Your SlideShare is downloading. ×
0
Rangers Visual studio project process guidance using with msf scrum
Rangers Visual studio project process guidance using with msf scrum
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Rangers Visual studio project process guidance using with msf scrum

943

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 …

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
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
943
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
50
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 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. Team capacity
  • 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. Vision
  • 5. Team
  • 6. User Stories
  • 7. Product Backlog
  • 8. Release Plan
  • 9. Logistics
  • 10. Sprint duration
  • 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. What have you done?
  • 13. What will you do?
  • 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. 0.5
  • 16. 1
  • 17. 2
  • 18. 3
  • 19. 5
  • 20. 8
  • 21. 13
  • 22. 20
  • 23. 40
  • 24. 100
  • 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. Design reviewed
  • 27. Coded
  • 28. Code reviewed
  • 29. Unit tested
  • 30. Functional tested
  • 31. Code commented
  • 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. What is not working?
  • 34. What else?</li></ul>INFORMAL DEMO<br /><ul><li>Team presents features
  • 35. Questions & Answers</li></ul>DOCUMENTATION<br /><ul><li>Documented
  • 36. Acronyms
  • 37. References
  • 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. 3<br />2<br />1<br />

×