Background: Our company has been using Jira / Greenhopper and one project for over 20 customers who all utilize one form or another of our base software package. With the new upgrade to Greenhopper we have decided to restructure our implementation of Jira / GH. This series of questions will be presented in a way that would be similar to a product backlog.
In true Agile / Scrum Fashion
Product (Question) Backlog
Thank You in advance to all of you who have read this far (yes I tend to be long-winded) and for any help you may be able to provide.
For number one, there is nothing that prevents you from working on tickets in your backlog without adding them to a sprint.
For number 3, if you have totally separate teams with a separate backlog, multiple rapid boards is probably the preferred way to do it.
If you truly have multiple sprints overlapping on the same backlog, then parellel sprints would be the way to go, and that issue is now in Greenhopper.
There is my 2 cents.
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG