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

Like this? Share it with your network

Share

Rangers Visual studio project process guidance using with msf scrum

on

  • 1,297 views

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

Statistics

Views

Total Views
1,297
Views on SlideShare
1,288
Embed Views
9

Actions

Likes
3
Downloads
48
Comments
0

2 Embeds 9

http://www.linkedin.com 6
https://www.linkedin.com 3

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Rangers Visual studio project process guidance using with msf scrum Presentation Transcript

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