MyTFS2010 - Project Guidance<br />Ivan Sanders <br />Define scrum planning, sprint, review and retrospective schedule<br /...
Team capacity
Upcoming SlideShare
Loading in...5

Rangers Visual studio project process guidance using with msf scrum


Published on

Your team can apply agile practices more easily by using the process template for MSF for Agile Software Development v5.0 with Visual Studio Application Lifecycle Management (ALM). The template and this guidance will help you practice Scrum and apply agile engineering practices. These processes and practices come from Scrum, eXtreme Programming, and other agile methodologies

Published in: Technology
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Transcript of "Rangers Visual studio project process guidance using with msf scrum"

  1. 1. MyTFS2010 - Project Guidance<br />Ivan Sanders <br />Define scrum planning, sprint, review and retrospective schedule<br />4<br />Dev Lead<br />Madhan<br />Scrum Master Name<br />C<br />SP<br />Scrum<br />boundaries<br />6<br />R/R<br /><ul><li>Product backlog
  2. 2. Team capacity
  3. 3. “Done” Definition</li></ul>M<br />T<br />W<br />T<br />F<br />Area Leads<br />1..8<br />Define Sprint Goal<br />A<br />SP<br />Sprint Planning Meeting<br />Define Sprint Backlog<br />B<br />Area Members<br />1..8<br />8<br />Define project name and optional codename<br />R/R<br />User Story template:<br />AS <user>I WANT <action>SO THAT <value><br />Define sprint duration 2,4,8, …weeks<br />3<br />Product Owner<br />owns product backlog and prioritization thereof.<br />Sprint Teams <br />Team A<br />1<br />Sprints<br />Feeds…<br />Team B<br />2<br />Define start date<br />Sprint<br />2<br />Sprint<br />1<br />9<br />Product Backlog<br />Sprint Task Item (STI)<br /><ul><li>Business Case
  4. 4. Vision
  5. 5. Team
  6. 6. User Stories
  7. 7. Product Backlog
  8. 8. Release Plan
  9. 9. Logistics
  10. 10. Sprint duration
  11. 11. “Done” Definition</li></ul>Burndown Chart<br />A<br />1<br />Product Backlog Item (PBI)<br />Sprint Task Item (STI)<br />Update Product Backlog<br />Product Planning<br />1<br />2<br />Sprint Status Update<br />B<br />Product Backlog Item (PBI)<br />Sprint Task Item (STI)<br />2<br />3<br />Product Backlog Item (PBI)<br />Sprint<br />3<br />SCRUM<br /><ul><li>2min status message</li></ul> - or -<br /><ul><li>15 min standup
  12. 12. What have you done?
  13. 13. What will you do?
  14. 14. Impediments?</li></ul>1<br />7<br />2<br />Product Backlog Item (PBI)<br />Sprint Task Item (STI)<br />4<br />4<br />Product Backlog Item (PBI)<br />Sprint Task Item (STI)<br />5<br />Heartbeat !<br />5<br />Product Backlog Item (PBI)<br /><ul><li>0
  15. 15. 0.5
  16. 16. 1
  17. 17. 2
  18. 18. 3
  19. 19. 5
  20. 20. 8
  21. 21. 13
  22. 22. 20
  23. 23. 40
  24. 24. 100
  25. 25. ?</li></ul>n<br />Sprint<br />3<br />Sprint Task Item (STI)<br />Groom backlog<br />Define definition of “done”<br />6<br />5<br />CODE<br /><ul><li>Designed
  26. 26. Design reviewed
  27. 27. Coded
  28. 28. Code reviewed
  29. 29. Unit tested
  30. 30. Functional tested
  31. 31. Code commented
  32. 32. Secure source control</li></ul>Story Points<br />Impediment Backlog<br />Scrum Master “backlog”<br />Impediment Backlog Item (IBI)<br />1<br />Impediment Backlog Item (IBI)<br />2<br />Sprint Retrospective<br />Sprint Review<br />10<br />11<br />Typically the vision is defined by the product owner<br />Steve<br />Product Owner Name<br />TEAM MEETING<br /><ul><li>What is working?
  33. 33. What is not working?
  34. 34. What else?</li></ul>INFORMAL DEMO<br /><ul><li>Team presents features
  35. 35. Questions & Answers</li></ul>DOCUMENTATION<br /><ul><li>Documented
  36. 36. Acronyms
  37. 37. References
  38. 38. Reviewed</li></ul>Vision template (source Geoffrey Moore):<br />FOR <customer>WHO <need>THE <product> IS <product category>UNLIKE <competitive alternative>OUR PRODUCT <differentiation statement><br />VisionMy Development Team<br />01/14/2011 <br />To provide an easy to follow roadmap using MSF Agile/Scrum for the development team as they grow into the process of using Visual Studio Team system<br />
  39. 39. 3<br />2<br />1<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.