Defining Jira structure according to single scrum team multiple products.

[Oğuz Yılmaz]

Hi,

We have a single scrum team with 2 different product's task items are handled by the team in sprints. Sprints have changing characteristics to focus on each product in consequent sprints.

In jra and Greenhopper plugin, may I use 2 Jira Project's work items in a sprint?

What is your practices on the issue?

Best Regards,

[Nicholas Muldoon]

Hi Oguz,

Igor is spot on, the Rapid Board in GreenHopper 5.8 onwards is the way to get multiple JIRA projects in the one view. You may wish to find out more about our future plans for Scrum and the Rapid Board.

Thanks Oguz.

Regards,
Nicholas Muldoon

[Oğuz Yılmaz]

A special docuemnt for just implementing Scrum in Jira-Greenhopper duo is necessary.

For example, I can not decide what is the best practice to Create a Sprint. Should I create a target version? Should I create a Rapid view? What is the sprint in term of jira-greenhopper.

I would be grateful if you have some directions. I thougth I will see comething like that:

create a sprint

drag and drop scenarios or work items in to sprint.

lock sprint.

run sprint.

finish sprint

like buttons :)

I am trying to select a new poduct for using in next several years. We have real bottlenecks with current Mantis system.

[Igor Sereda [ALM Works]]

In the latest GreenHopper versions, you can use the Rapid Board to put issues from several projects on one board. You can define a Rapid Board by a filter like fixVersion = SprintFromProject1 OR fixVersion = SprintFromProject2, and call that configuration a sprint.

(I'm theorizing - it would be interesting to hear answers from the practitioners of the Rapid Board.)