I’ve had a lot of positive reaction to my developerWorks article on this topic, and many have requested a video version. So here it is, at last:
Like the article, the video follows the fictional Havannah team while they develop a Product Backlog and then a Sprint Backlog and execute their first Sprint. The case study comes from Mike Cohn’s Agile Estimating and Planning book. Since Scrum doesn’t specify how to maintain your backlog, I chose User Stories, and Mike’s example is complete enough to be interesting and simple enough to not get in the way of the tutorial.
The topics covered include:
- Overview of Project and Team Areas for the Havannah 1.0 project.
- Developing a Product Backlog with User Stories.
- Creating a Sprint Backlog from the Product Backlog by moving stories to the Sprint Iteration Plan and then developing tasks and estimates for them.
- Discussion of Team Load bars and their use during planning sessions.
- Description of work planning using the My Work view and why this is important – because it makes the Planned Time view work as intended.
- Sprint “execution”: updating tasks with time spent, changing states, adding discussion elements as well as use of Impediment and Retrospective Work Items.
- Use of standard reports, like the Sprint Burndown.
- An overview of the RTC Web UI.
Special thanks to Mike Cohn for permission to use some graphics from his web site to punch up the presentation.
—
Millard Ellingsworth
(6 votes, average: 4.50 out of 5)
Loading...
Very informative with regards to Jazz/RTC Scrum integration. Nice work.
Quite the informative article regarding the integration. I’ve bookmarked it in case I need to use the two together. Thanks!
– James, Resveratrol Consultant
The link to the video seems to be broken
I’ve fixed the link to the video from this blog post. We swizzled some locations around during our redesign. You can also find the video in the library now! http://jazz.net/library/video/46
Hi, I’ve done almost the same thing in my sprints, like you, I’m using the M. Cohn book to drive the project. My new chanllenge, after convince my managers, is extend the process to an electronic design area of the company. I’m writing a log of this implementation, along with some other scrum-related stuff. You can see the log here. Thanks for sharing!
Hi,
needless to say “great work”!! We need more of this!!
:-)
Questions:
* Release Iteration in SCRUM? I thought there are only sprints?
* Sprint duration only 2 weeks? Not ~30 days?
* What about Release Plans? There is no Plan Type of this in RTC SCRUM.
@stefan Thanks for your kind words. While it is true that Scrum is theoretically only sprints, I’ve yet to work on a project that didn’t have a release schedule. Some pragmatism may have leaked into the presentation.
Sprint duration is an oft-debated topic. I think the shortest sprint your project is capable of (not necessarily comfortable with) is the duration you want. I’ve seen teams do 1 week and I’ve seen teams to 6 weeks and I work with teams that do 3 week iterations.
RTC v2.0 and later provides much better support for Agile Estimating and Planning and does include Release plans as part of that (along with more flexible plan types and other improvements).
I saw this video and can quickly understand how to create stories and the big picture. Thanks for putting this together.