Continued from Part 1...
In the first part of this series we looked at the Product Owner activities that take place in VersionOne (Product Planning and Release Planning). The second part of this series will outline the Team activities that are covered during our bi-weekly live product demonstrations.
Picking up from where we left off, once the work has been scheduled into a Release we’ll be jumping into…
- Sprint Planning
- This is where we’ll cover the resources available to the ScrumMaster and Team to plan their Sprint.
- Areas covered:
- Velocity Reporting that provides a good gauge on how much work should be scheduled into a Sprint
- Scheduling Work into a Sprint
- Customizing the grid to ensure dependencies are being satisfied
- Visualization
- Breaking of work into Task and Test level details
- Sprint Summary showing how the current Sprint compares to the last
- Team Member Capacity and visibility to ensure the team is not overburdened
- Areas covered:
- This is where we’ll cover the resources available to the ScrumMaster and Team to plan their Sprint.
Once the Backlog has been broken down, the team is ready to start focusing on day to day activities for that Sprint via the…
- TeamRoom
- Here the Team will track their day to day progress for the Sprint.
- Areas covered:
- Developers tracking and updating their progress via the Taskboard
- Sharing blocking issues with the team
- How the board views provide direct collaboration between the Developers and Testers
- Conducting the daily standup meeting
- QA Team tracking and updating their progress via the Testboard
- Visibility provided to executives via the Storyboard
- VersionOne’s support for different processes on a per project basis
- Areas covered:
- Here the Team will track their day to day progress for the Sprint.
Finally when the Team is near the end of the sprint, we’re ready to…
- Review the Sprint
- This is where the Team can close or move any remaining work before reviewing their efforts.
- Areas covered:
- Quick Closing a Backlog Item
- Moving an item to a future Sprint
- Performing a Split on Backlog Items where partial work was completed
- Closing out the Sprint
- Conducting a Retrospective
- Areas covered:
- This is where the Team can close or move any remaining work before reviewing their efforts.
Other areas covered during the demonstration (time permitting) include reporting, support, and integration’s covered in the final part of this series.
Continued…
