I recently started using portfolios (features and initiatives) for some of our team's larger strategic initiatives. I did not, however, create a new project (which may have been a mistake; don't know). I am not too concerned with tracking and metrics right now as much as grouping my stories together.
For example, we have an initiative to deliver a product enhancement that will touch many different areas in the product. I created the feature and I created the stories before the work is put into a sprint, placing them in the order in which I want the work to be done. These stories need to be worked on in a specified order, relative to the overall portfolio, but independent of the priority for the stories & defects in any given sprint (which will have work not associated with the portfolio).
When I'm looking at the work in the Portfolio view, I see the stories and they are in the order I want them to be. However, once I move a story into a sprint, it gets placed at the top of the sprint. This would be fine if I didn't have other work going on that is of higher priority. So I move the story to the proper priority order for the spring and, ugh!, the story is now in a different order when looking at the portfolio. If I reorder the portfolio, my sprint is messed up.
Can someone please tell me if I can "have my cake and eat it too" or if the problem is because I didn't create the portfolio in a different project.
thanks!
------------------------------
Karen Gwynn
still learning ...
IData, Inc.
------------------------------