Content
Mapping of sprints to releases
Added by Noor Hussain almost 9 years ago
We are trying to organize our projects and follow SCRUM as a methodology for development, we are using open project and backlog plugin. We have Wishlist, Product Backlog, Bug backlog, Sprints(for internal team) and Releases(for external world so that they are aware of our product Roadmap). Each of these above are versions created from project setting tabs > versions.
As a process, product owner works on product backlog and creates release versions. So product owner adds WPs like features, epics and user stories during release planning which is then visible under Roadmap for other stake holders. During next step i.e. Sprint planning, product owner and team plans sprints (WP and task) by creating single or multiple sprint versions for a specific Release. During this process, all WP in Release version that are going to be delivered in a sprint are updated to belong to that particular sprint version. Now the problem is
1) These WP gets removed from Release versions and gets added to sprint version, though we want these WP to remain visible under release version as well as sprint version. Because of this our Roadmap view also gets disturbed(WP are visible only under sprint version and not in release version)
2) Sprints version are also visible under Roadmap which we don’t want to happen. Is there a way to hide sprint versions from Roadmap.
Replies (2)
Hello Noor,
thanks for your message.
1) In order to keep work packages in the release version and add them to the sprint version as well you can copy work packages. When you open a work package and select “More” you can select “Copy” which will create a new work package form with the values of the original work package pre-set. You can then make adjustments to the work package which should be newly created (e.g. change the version to the sprint version) and create the new work package.
2) The separation between sprint and release versions is only defined in the backlog. Therefore all (open) versions are displayed in the Roadmap. If you want to limit which versions are visible in the Roadmap you could have your release versions in a (e.g. public) main project and your sprint versions in a (private) subproject. When users go to the main project and take a look at the roadmap they only see the release versions by default. This approach would however require that you move work packages across projects when you assign them from the release version to the sprint version.
Best,
Robin
hi, i just tried the suggestion from Robin but it does not work. In both my parent and sub project, the roadmaps shows all the open versions (releases, sprints & product backlog). I am logged in as admin to my OpenProject. It will be great if someone can advise what else I need to do in order to show only the versions created under parent project in parent project's roadmap.