I'm working in a product company developing about 20 products and having about 40 developers in staff. Developers are united in teams (5-10 persons), and each team works on a set of products. Each team has more or less freedom (as some products depend on other ones) in choosing duration of sprint. For each sprint team implements a set of features in the products they are working on, but products are released separately, usually on demand.
By now we have a strong need to migrate from self-made issue tracking tool to something more convenient and functional. I looked at JIRA(+Greenhopper) and appreciated it's simplicity and customization opportunities. But I have no idea how we can implement our process with a plain structure of projects and sprints based on releases used in JIRA.
It sounds like JIRA & Greenhopper plus the new Rapid Views in JIRA 4.4 will help.
Its the only way to do cross-project views in JIRA so far that I know about.
Thank you, Bernard. I'm going to look at Rapid Views, sounds promising.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm a bit unsure if what your question actually is.
My current customer has sevelra products in their portfolio. What we have done is registering every product as a project. This again makes it possible to have different pages, workflow, notofications, permissions, etc. The projects can have different sprints, different durations and different version-setups.
Just a quick answer. I have no idea if I actually answered your question :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, Ivar! In our case we want to have one sprint and one backlog for several projects, and thats the problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.