Tracking Impediments and creating an Impediment Plan in RTC
What I would like to do is create a Plan so that I can better manage the impediments, increase the visibility, and create a more concise view for the team and for management. Since Impediments are not necessarily tied to a particular release or iteration, I would like to make that restriction optional.
Is this even possible in RTC? We are on 4.0.1
One answer
Comments
I can understand tying an impediment to a particular iteration, but what about those impediments that are not part of an iteration? Here I am using the expanded definition of Iteration - those items and issues that are blocking progress or that would increase the productivity of the team.
So some of the "impediments" that I want to track is the construction of a new Team Room to reduce the distractions from other departments in our area, and the purchase of webcams for the team so that when they are remote we can still see each other. These are things that I want to keep visible to the team and to management so that they can be addressed.
Any suggestions on how to better manage Impediments without having them imbedded in a Release or Sprint backlog? I am open to any and all suggestions.
You can create a shared query that matches the set of impediments of interest, and optionally, put that query in a viewlet in a team dashboard.
I heard some teams are using another iteration (RTC iteration) for the project management purpose. This iteration's period never ends.
_-_Rational_Team_Conc.png)
Alternatively, you may create another timeline.
_-_Rational_Team_Conc.png)
2 votes
I was about to suggest something similar. Some teams also use this strategy to put defects into a "Triage iteration" to hold them outside of the normal development plans. This strategy is described in my Pragmatic Scrum with RTC webinar, replay here: http://youtu.be/LgSmmEox9GY
Perfect! Some out of the box thinking is what it took to find a good solution.