It's all about the answers!

Ask a question

RTC and Team Planning


Ratheesh Madathil (1371325) | asked Mar 10 '15, 8:33 a.m.

We are in the face of introducing RTC in our environment. In the situation where we are offering SCRUM template to a particular development team, like any other large organisation we always have to face the long term planning/commitment aspect as well.

Can anyone of you share us any hints, that would enable to us have a velocity based planning (projection) for a scrum team in RTC?

We would like to know whether such a possibility is existing in RTC or not? If yes, how to use it.

Scenario:

Scrum team with backlog of stories

All stories in the backlog has a story point assigned (estimation)

All stories are also Ranked

Output expected:

A projection for a story in the backlog, which tells approximately when this story can be delivered by the team

Can be in a dashboard or any other report

Assumption:

Team velocity is available from the past iterations (or using team capacity and  allocation)

 Thank you very much.

2 answers



permanent link
Stephanie Bagot (2.1k512) | answered Mar 10 '15, 9:49 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
Yes this is possible. We have an article on the information center with typical reports you would use to determine Team velocity:
http://www-01.ibm.com/support/knowledgecenter/SSYMRC_5.0.1/com.ibm.team.reports.doc/topics/c_ccm_check_velocity.html?lang=en

Just keep in mind you may have to customize the RTC instance based on your needs. This is documented throughout jazz.net and the information center as well.

Comments
Ratheesh Madathil commented Mar 10 '15, 9:57 a.m.

Thanks for that answer, but does not really address the forecasting part.
Just giving an input iteration and get a chart for how many story points are closed is pretty straight forward.
The request is, if I have a TEAM backlog as input, can I know when a particular story will be delivered in future. Any algorithm behind is fine to start with.


permanent link
Juan Pablo Bruno (26510) | answered Mar 10 '15, 11:27 a.m.
 You may want build your own release burndown that just asks for the estimated velocity (or projected burndown line), and given the size of your backlog, that will give you the plan for that release. We did that at our team, and it really helps to have a picture of it. I don't know of any built-in report for that, but you may want to use the JRS (or RRDI) to do it.

Your answer


Register or to post your answer.