Scrum with Team Foundation Server 2010<br />Aaron Bjork<br />Senior Program Manager<br />Microsoft Corporation<br />
Agenda<br />Scrum with TFS 2010 using MSF for Agile 5.0<br />Planning the Project<br />How do you plan the project?<br />P...
How do you Plan the Project?<br />Product Backlog<br />Evolving backlog of user stories (requirements)<br />Describes what...
Planning the Project<br />Product Backlog<br />“As a new customer I want to register online so I can use the services offe...
Product Backlog<br />User Stories<br />Planning the Project<br />Stories are planned for completion in  upcoming sprints<b...
… let’s look at the Product Backlog in TFS 2010<br />
Product Backlog in TFS 2010 <br />Product Backlog query<br />Creating new user stories<br />Prioritizing<br />Estimating s...
Product Backlog<br />Product backlog query in Team Explorer<br />
Product Backlog<br />New stories created by the Product Owner<br />
Product Backlog<br />The new story provides a guide to ensure the story is written from the customer’s perspective<br />
Product Backlog<br />Each story is ranked by priority and assigned a story point value<br />
Product Backlog<br />Product Backlog workbook for planning future sprints<br />
Product Backlog Workbook<br />Stories that are too large are left on the backlog<br />Each story is placed in an upcoming ...
Product Backlog Workbook<br />The product owner can use the velocity of the team to help plan for upcoming sprints<br />… ...
Agenda<br />Scrum with TFS 2010 using MSF for Agile 5.0<br />Planning the Project<br />How do you plan the project?<br />P...
What is Sprint Planning?<br />The product owner and the team add user stories to the sprint<br />Each story is decomposed ...
Product Backlog<br />User Stories<br />Planning a Sprint<br />Iteration Backlog<br />User Stories<br />Tasks (hours)<br />...
Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />Planning a Sprint<br />...
… let’s look at Sprint Planning in TFS 2010<br />
Sprint Planning<br />Break down user stories into tasks<br />Load balance<br />Commit<br />Track interruptions<br />Track ...
Iteration Backlog Workbook<br />Each sprint has an Excel workbook to assist the team in making a commitment<br />
Iteration Backlog Workbook<br />Dates for the sprint are added…<br />
Iteration Backlog Workbook<br />... and any planned interruptions<br />
Iteration Backlog Workbook<br />The team breaks down the first user story into tasks<br />
Iteration Backlog Workbook<br />Each task is estimated in hours<br />
Iteration Backlog Workbook<br />The team checks their capacity for the sprint<br />
Iteration Backlog Workbook<br />The next story is broken down…<br />
Iteration Backlog Workbook<br />
Iteration Backlog Workbook<br />The team has capacity…<br />… but one team member has too much work<br />
Iteration Backlog Workbook<br />
Iteration Backlog Workbook<br />The final story is broken down<br />
Iteration Backlog Workbook<br />Based on capacity and estimates, the team is overcommitted<br />
Iteration Backlog Workbook<br />The final story is removed…<br />
Iteration Backlog Workbook<br />And replaced with a smaller story from the product backlog<br />
Iteration Backlog Workbook<br />… but one team member still has too much work<br />The team is comfortable committing to t...
Iteration Backlog Workbook<br />Tasks are reassigned<br />
Iteration Backlog Workbook<br />Tasks are reassigned<br />
Iteration Backlog Workbook<br />Work is now load balanced across the team<br />
Iteration Backlog Workbook<br />The final step is to publish the data back to TFS<br />Sprint planning is complete!<br />
Agenda<br />Scrum with TFS 2010 using MSF for Agile 5.0<br />Planning the Project<br />How do you plan the project?<br />P...
How do you Run a Sprint?<br />Track Progress<br />Daily Sprint Meeting<br />What work has been completed<br />What work re...
Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />Running a Sprint<br />T...
Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />C...
Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />
Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />E...
Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />Running a Sprint<br />A...
Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />T...
Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />S...
Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />N...
Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />T...
… let’s look at Running a Sprint in TFS 2010<br />
Running a Sprint<br />Record completed work daily <br />Track progress with reports and dashboards<br />Retrospectives<br />
Updating Tasks<br />Multiple interfaces for updating work items<br />
Updating Tasks<br />Team Explorer<br />
Updating Tasks<br />Iteration Backlog workbook<br />
Updating Tasks<br />Team Project portal<br />
Updating Tasks<br />
Updating Tasks<br />
Updating Tasks<br />Team Web Access<br />
Tracking Progress<br />Burndown chart tracks remaining and completed work<br />
Tracking Progress<br />
Tracking Progress<br />
Tracking Progress<br />Detailed sprint progress is tracked on the project portal<br />The burndown shows the team on track...
Tracking Progress<br />The Scrummaster opens an issue to track the problem the portal has identified<br />
Tracking Progress<br />The issue is opened and tracked in TFS<br />
Tracking Progress<br />The portal brings data together so it can be analyzed to ensure success on a sprint<br />Test are p...
Tracking Progress<br />Rich set of reports track progress<br />
Retrospective<br />Capture retrospectives using the Team wiki on the Project Portal<br />Sample documents are provided as ...
Agenda<br />Scrum with TFS 2010 using MSF for Agile 5.0<br />Planning the Project<br />How do you plan the project?<br />P...
Questions/Follow-Up<br />Contact<br />Aaron  Bjork <br />abjork@microsoft.com<br />http://blogs.msdn.com/aaronbjork<br />T...
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be...
Upcoming SlideShare
Loading in …5
×

Scrum With Team Foundation Server 2010

91,935
-1

Published on

Learn how Team Foundation Server 2010 supports Scrum.

Published in: Technology, Sports
11 Comments
55 Likes
Statistics
Notes
No Downloads
Views
Total Views
91,935
On Slideshare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
4,967
Comments
11
Likes
55
Embeds 0
No embeds

No notes for slide
  • Add animation and a “can’t commit”… Move a smaller up…
  • Add a not-finished… Red -
  • Add animation and a “can’t commit”… Move a smaller up…
  • Scrum With Team Foundation Server 2010

    1. 1. Scrum with Team Foundation Server 2010<br />Aaron Bjork<br />Senior Program Manager<br />Microsoft Corporation<br />
    2. 2. Agenda<br />Scrum with TFS 2010 using MSF for Agile 5.0<br />Planning the Project<br />How do you plan the project?<br />Project planning in TFS 2010<br />Planning a Sprint<br />What is sprint planning?<br />Sprint planning in TFS 2010<br />Running a Sprint<br />How do you run a sprint?<br />Running a sprint in TFS 2010<br />
    3. 3. How do you Plan the Project?<br />Product Backlog<br />Evolving backlog of user stories (requirements)<br />Describes what users need and value<br />Owned by the Product Owner<br />Prioritized by business value<br />Each story is written from the user’s perspective<br />
    4. 4. Planning the Project<br />Product Backlog<br />“As a new customer I want to register online so I can use the services offered”<br />User Stories<br />5<br />8<br />Stories are listed on the backlog in priority order<br />The team estimates each story using story points<br />5<br />Priority<br />3<br />New stories are added to the product backlog<br />8<br />1<br />
    5. 5. Product Backlog<br />User Stories<br />Planning the Project<br />Stories are planned for completion in upcoming sprints<br />Sprint 3<br />3<br />3<br />3<br />Sprint 4<br />The product owner re-prioritizes the backlog<br />Priority<br />4<br />4<br />4<br />
    6. 6. … let’s look at the Product Backlog in TFS 2010<br />
    7. 7. Product Backlog in TFS 2010 <br />Product Backlog query<br />Creating new user stories<br />Prioritizing<br />Estimating story points<br />Add user stories to upcoming sprints<br />
    8. 8. Product Backlog<br />Product backlog query in Team Explorer<br />
    9. 9. Product Backlog<br />New stories created by the Product Owner<br />
    10. 10. Product Backlog<br />The new story provides a guide to ensure the story is written from the customer’s perspective<br />
    11. 11. Product Backlog<br />Each story is ranked by priority and assigned a story point value<br />
    12. 12. Product Backlog<br />Product Backlog workbook for planning future sprints<br />
    13. 13. Product Backlog Workbook<br />Stories that are too large are left on the backlog<br />Each story is placed in an upcoming sprint<br />
    14. 14. Product Backlog Workbook<br />The product owner can use the velocity of the team to help plan for upcoming sprints<br />… with start/end dates and the size of the team<br />Each sprint is added to Iteration Planning worksheet…<br />
    15. 15. Agenda<br />Scrum with TFS 2010 using MSF for Agile 5.0<br />Planning the Project<br />How do you plan the project?<br />Project planning in TFS 2010<br />Planning a Sprint<br />What is sprint planning?<br />Sprint planning in TFS 2010<br />Running a Sprint<br />How do you run a sprint?<br />Running a sprint in TFS 2010<br />
    16. 16. What is Sprint Planning?<br />The product owner and the team add user stories to the sprint<br />Each story is decomposed into tasks<br />The team makes a commitment to each user story<br />
    17. 17. Product Backlog<br />User Stories<br />Planning a Sprint<br />Iteration Backlog<br />User Stories<br />Tasks (hours)<br />Commit!<br />Based on estimates the team commits to each story<br />3<br />3<br />The team thinks this story is more work than they can commit to…<br />During the sprint planning meeting, the product owner and the team add User Stories to the sprint<br />3<br />The team breaks down each story into tasks<br />Commit!<br />Can’t Commit!<br />
    18. 18. Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />Planning a Sprint<br />User Stories<br />Tasks (hours)<br />Commit!<br />3<br />3<br />3<br />The larger story is removed from the sprint and the team considers a smaller story on the backlog<br />Commit!<br />?<br />3<br />The sprint is now planned and the team is ready to get started!<br />The team can commit to this smaller story<br />Commit!<br />
    19. 19. … let’s look at Sprint Planning in TFS 2010<br />
    20. 20. Sprint Planning<br />Break down user stories into tasks<br />Load balance<br />Commit<br />Track interruptions<br />Track progress<br />
    21. 21. Iteration Backlog Workbook<br />Each sprint has an Excel workbook to assist the team in making a commitment<br />
    22. 22. Iteration Backlog Workbook<br />Dates for the sprint are added…<br />
    23. 23. Iteration Backlog Workbook<br />... and any planned interruptions<br />
    24. 24. Iteration Backlog Workbook<br />The team breaks down the first user story into tasks<br />
    25. 25. Iteration Backlog Workbook<br />Each task is estimated in hours<br />
    26. 26. Iteration Backlog Workbook<br />The team checks their capacity for the sprint<br />
    27. 27. Iteration Backlog Workbook<br />The next story is broken down…<br />
    28. 28. Iteration Backlog Workbook<br />
    29. 29. Iteration Backlog Workbook<br />The team has capacity…<br />… but one team member has too much work<br />
    30. 30. Iteration Backlog Workbook<br />
    31. 31. Iteration Backlog Workbook<br />The final story is broken down<br />
    32. 32. Iteration Backlog Workbook<br />Based on capacity and estimates, the team is overcommitted<br />
    33. 33. Iteration Backlog Workbook<br />The final story is removed…<br />
    34. 34. Iteration Backlog Workbook<br />And replaced with a smaller story from the product backlog<br />
    35. 35. Iteration Backlog Workbook<br />… but one team member still has too much work<br />The team is comfortable committing to this story…<br />
    36. 36. Iteration Backlog Workbook<br />Tasks are reassigned<br />
    37. 37. Iteration Backlog Workbook<br />Tasks are reassigned<br />
    38. 38. Iteration Backlog Workbook<br />Work is now load balanced across the team<br />
    39. 39. Iteration Backlog Workbook<br />The final step is to publish the data back to TFS<br />Sprint planning is complete!<br />
    40. 40. Agenda<br />Scrum with TFS 2010 using MSF for Agile 5.0<br />Planning the Project<br />How do you plan the project?<br />Project planning in TFS 2010<br />Planning a Sprint<br />What is sprint planning?<br />Sprint planning in TFS 2010<br />Running a Sprint<br />How do you run a sprint?<br />Running a sprint in TFS 2010<br />
    41. 41. How do you Run a Sprint?<br />Track Progress<br />Daily Sprint Meeting<br />What work has been completed<br />What work remains<br />Deliver a “potentially shippable” increment<br />Demo the value delivered<br />Retrospective <br />
    42. 42. Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />Running a Sprint<br />The team starts work on the tasks…<br />
    43. 43. Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />Completed work is reported daily<br />
    44. 44. Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />
    45. 45. Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />Each User Story has been implemented<br />All work for the sprint is “done-done”<br />
    46. 46. Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />Running a Sprint<br />And the team has developed a “potentially shippable” increment<br />The team holds a demo to show the value they have delivered<br />
    47. 47. Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />The latest increment is shipped to customers<br />
    48. 48. Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />Stories and tasks are cleared from the backlog – the team delivered on its commitment<br />Stories delivered in the last sprint are closed<br />What worked? <br />What didn’t work? What can the team do to improve?<br />The team holds a retrospective…<br />
    49. 49. Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />New Stories are added to the Product Backlog<br />
    50. 50. Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />User Stories<br />User Stories<br />Tasks (hours)<br />The backlog is prioritized and ready for the team to plan the next sprint<br />
    51. 51. … let’s look at Running a Sprint in TFS 2010<br />
    52. 52. Running a Sprint<br />Record completed work daily <br />Track progress with reports and dashboards<br />Retrospectives<br />
    53. 53. Updating Tasks<br />Multiple interfaces for updating work items<br />
    54. 54. Updating Tasks<br />Team Explorer<br />
    55. 55. Updating Tasks<br />Iteration Backlog workbook<br />
    56. 56. Updating Tasks<br />Team Project portal<br />
    57. 57. Updating Tasks<br />
    58. 58. Updating Tasks<br />
    59. 59. Updating Tasks<br />Team Web Access<br />
    60. 60. Tracking Progress<br />Burndown chart tracks remaining and completed work<br />
    61. 61. Tracking Progress<br />
    62. 62. Tracking Progress<br />
    63. 63. Tracking Progress<br />Detailed sprint progress is tracked on the project portal<br />The burndown shows the team on track…<br />And almost half of the tasks remain open<br />But the team hasn’t closed any of the three stories…<br />
    64. 64. Tracking Progress<br />The Scrummaster opens an issue to track the problem the portal has identified<br />
    65. 65. Tracking Progress<br />The issue is opened and tracked in TFS<br />
    66. 66. Tracking Progress<br />The portal brings data together so it can be analyzed to ensure success on a sprint<br />Test are passing…<br />But bugs are climbing steadily<br />
    67. 67. Tracking Progress<br />Rich set of reports track progress<br />
    68. 68. Retrospective<br />Capture retrospectives using the Team wiki on the Project Portal<br />Sample documents are provided as a guide<br />
    69. 69. Agenda<br />Scrum with TFS 2010 using MSF for Agile 5.0<br />Planning the Project<br />How do you plan the project?<br />Project planning in TFS 2010<br />Planning a Sprint<br />What is sprint planning?<br />Sprint planning in TFS 2010<br />Running a Sprint<br />How do you run a sprint?<br />Running a sprint in TFS 2010<br />
    70. 70. Questions/Follow-Up<br />Contact<br />Aaron Bjork <br />abjork@microsoft.com<br />http://blogs.msdn.com/aaronbjork<br />TFS Resources<br />http://blogs.msdn.com/bharry<br />http://social.msdn.microsoft.com/Forums/en-US/category/vsts<br />http://msdn.microsoft.com/en-us/teamsystem/default.aspx<br />
    71. 71. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.<br />The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.<br />
    1. A particular slide catching your eye?

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

    ×