19th August 2011<br />Microsoft Singapore ALM Event<br />Scrum withMicrosoftVisual Studio Team Foundation Server 2010<br /...
Team Foundation Server 2010<br />
An Open Platform<br />
Source:  Forrester Reasearch, Inc.<br />
Why is Agile Catching On?<br />5<br />
Business Needs Demand It	<br />“Firms today experience a much higher velocity of business change. Market opportunities app...
Value Delivered Early and Often<br /><ul><li>Working software continually delivered
Regular discussions with stakeholders
Maximize ROI</li></li></ul><li>Agenda<br /><ul><li>Scrum with TFS 2010
Planning the Project
Planning a Sprint
Running a Sprint</li></li></ul><li>Product Backlog<br />    Daily<br />Sprint<br />Sprint <br />Backlog<br />    Potential...
How do you Plan the Project?<br /><ul><li>Product Backlog
Evolving backlog of Product Backlog Items
Describes what users need and value
Owned by the Product Owner
Prioritized by business value
Each PBI is written from the user’s perspective</li></li></ul><li>Planning the Project<br />Product Backlog<br />“As a new...
Product Backlog in TFS 2010 <br /><ul><li>Product Backlog query
Creating new PBIs
Prioritizing
Estimating effort</li></li></ul><li>DemoManaging the Product Backlog in TFS 2010<br />
Agenda<br /><ul><li>Scrum with TFS 2010
Planning the Project
Planning a Sprint
Running a Sprint</li></li></ul><li>Product Backlog<br />    Daily<br />Sprint<br />Sprint <br />Backlog<br />    Potential...
What is Sprint Planning?<br /><ul><li>The product owner and the team add Product Backlog Itemsto the sprint
Each PBI is decomposed into tasks
The team makes a commitment to each PBI</li></li></ul><li>Product Backlog<br />Iteration Backlog<br />PBIs<br />Planning a...
Product Backlog<br />Iteration Backlog<br />PBIs<br />Tasks (Points)<br />Planning a Sprint<br />PBIs<br />Commit!<br />3<...
Sprint Planning<br /><ul><li>Break down PBIs into tasks
Team members Sign up for tasks
Commit
Track progress</li></li></ul><li>DemoPlanning a Sprint in TFS 2010<br />
Agenda<br /><ul><li>Scrum with TFS 2010
Planning the Project
Planning a Sprint
Running a Sprint</li></li></ul><li>Product Backlog<br />    Daily<br />Sprint<br />Sprint <br />Backlog<br />    Potential...
How do you Run a Sprint?<br /><ul><li>Daily Scrum
What was done
What will be done
Impediments
Sprint Burn-down
Deliver a “potentially shippable” increment
Demo the value delivered
Retrospective </li></li></ul><li>Product Backlog<br />Iteration Backlog<br />PBIs<br />PBIs<br />Tasks (Points)<br />Runni...
Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />PBIs<br />PBIs<br />Tasks (hours)<br />Completed work is...
Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />PBIs<br />PBIs<br />Tasks (hours)<br />
Upcoming SlideShare
Loading in...5
×

Scrum With TFS 2010

2,297

Published on

Microsoft Singapore Developer Days Event - August 2011

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,297
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
108
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Poster TFS ArchitectureUserreferencesVSS to TFS migration scenariosTest migration (actuallywrittenin Excel)
  • Poster TFS ArchitectureUserreferencesVSS to TFS migration scenariosTest migration (actuallywrittenin Excel)
  • 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 TFS 2010

    1. 1. 19th August 2011<br />Microsoft Singapore ALM Event<br />Scrum withMicrosoftVisual Studio Team Foundation Server 2010<br />Adrian Dunne | Microsoft Singapore<br />
    2. 2. Team Foundation Server 2010<br />
    3. 3. An Open Platform<br />
    4. 4. Source: Forrester Reasearch, Inc.<br />
    5. 5. Why is Agile Catching On?<br />5<br />
    6. 6. Business Needs Demand It <br />“Firms today experience a much higher velocity of business change. Market opportunities appear or dissolve in months or weeks instead of years. This increased business velocity demands much greater agility from business systems.”<br />Diego Lo Giudice and Dave West, Forrester<br />February 2011<br />Transforming Application Delivery<br />
    7. 7. Value Delivered Early and Often<br /><ul><li>Working software continually delivered
    8. 8. Regular discussions with stakeholders
    9. 9. Maximize ROI</li></li></ul><li>Agenda<br /><ul><li>Scrum with TFS 2010
    10. 10. Planning the Project
    11. 11. Planning a Sprint
    12. 12. Running a Sprint</li></li></ul><li>Product Backlog<br /> Daily<br />Sprint<br />Sprint <br />Backlog<br /> Potentially Shippable Increment<br />
    13. 13. How do you Plan the Project?<br /><ul><li>Product Backlog
    14. 14. Evolving backlog of Product Backlog Items
    15. 15. Describes what users need and value
    16. 16. Owned by the Product Owner
    17. 17. Prioritized by business value
    18. 18. Each PBI is written from the user’s perspective</li></li></ul><li>Planning the Project<br />Product Backlog<br />“As a new customer I want to register online so I can use the services offered”<br />Product Backlog Item<br />5<br />8<br />PBIs are listed on the backlog in priority order<br />The team estimates the ‘effort’ for each PBI<br />5<br />Priority<br />3<br />New PBIs are added to the product backlog<br />8<br />1<br />
    19. 19. Product Backlog in TFS 2010 <br /><ul><li>Product Backlog query
    20. 20. Creating new PBIs
    21. 21. Prioritizing
    22. 22. Estimating effort</li></li></ul><li>DemoManaging the Product Backlog in TFS 2010<br />
    23. 23. Agenda<br /><ul><li>Scrum with TFS 2010
    24. 24. Planning the Project
    25. 25. Planning a Sprint
    26. 26. Running a Sprint</li></li></ul><li>Product Backlog<br /> Daily<br />Sprint<br />Sprint <br />Backlog<br /> Potentially Shippable Increment<br />
    27. 27. What is Sprint Planning?<br /><ul><li>The product owner and the team add Product Backlog Itemsto the sprint
    28. 28. Each PBI is decomposed into tasks
    29. 29. The team makes a commitment to each PBI</li></li></ul><li>Product Backlog<br />Iteration Backlog<br />PBIs<br />Planning a Sprint<br />PBIs<br />Tasks (Points)<br />Commit!<br />Based on estimates the team commits to each PBI<br />3<br />The team thinks this PBI is more work than they can commit to…<br />3<br />During the sprint planning meeting, the product owner and the team add PBIs to the sprint<br />3<br />The team breaks down each story into tasks<br />Commit!<br />Can’t Commit!<br />
    30. 30. Product Backlog<br />Iteration Backlog<br />PBIs<br />Tasks (Points)<br />Planning a Sprint<br />PBIs<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 />
    31. 31. Sprint Planning<br /><ul><li>Break down PBIs into tasks
    32. 32. Team members Sign up for tasks
    33. 33. Commit
    34. 34. Track progress</li></li></ul><li>DemoPlanning a Sprint in TFS 2010<br />
    35. 35. Agenda<br /><ul><li>Scrum with TFS 2010
    36. 36. Planning the Project
    37. 37. Planning a Sprint
    38. 38. Running a Sprint</li></li></ul><li>Product Backlog<br /> Daily<br />Sprint<br />Sprint <br />Backlog<br /> Potentially Shippable Increment<br />
    39. 39. How do you Run a Sprint?<br /><ul><li>Daily Scrum
    40. 40. What was done
    41. 41. What will be done
    42. 42. Impediments
    43. 43. Sprint Burn-down
    44. 44. Deliver a “potentially shippable” increment
    45. 45. Demo the value delivered
    46. 46. Retrospective </li></li></ul><li>Product Backlog<br />Iteration Backlog<br />PBIs<br />PBIs<br />Tasks (Points)<br />Running a Sprint<br />The team starts work on the tasks…<br />
    47. 47. Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />PBIs<br />PBIs<br />Tasks (hours)<br />Completed work is reported daily<br />
    48. 48. Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />PBIs<br />PBIs<br />Tasks (hours)<br />
    49. 49. Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />PBIs<br />PBIs<br />Tasks (hours)<br />Each User PBI has been implemented<br />All work for the sprint is “done-done”<br />
    50. 50. Product Backlog<br />Iteration Backlog<br />PBIs<br />PBIs<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 />
    51. 51. 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 />
    52. 52. Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />PBIs<br />PBIs<br />Tasks (Points)<br />PBIs and tasks are cleared from the backlog – the team delivered on its commitment<br />PBIs 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 />
    53. 53. Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />PBIs<br />PBIs<br />Tasks (Points)<br />New PBIs are added to the Product Backlog<br />
    54. 54. Running a Sprint<br />Product Backlog<br />Iteration Backlog<br />PBIs<br />PBIs<br />Tasks (Points)<br />The backlog is prioritized and ready for the team to plan the next sprint<br />
    55. 55. Running a Sprint<br /><ul><li>Record completed work daily
    56. 56. Track and Resolve Impediments
    57. 57. Track progress with reports and dashboards
    58. 58. Retrospectives</li></li></ul><li>DemoRunning a Sprint in TFS 2010<br />
    59. 59. Tracking Progress - Development<br />Burndown chart tracks remaining and completed work<br />
    60. 60. Tracking Progress - Development<br />
    61. 61. Tracking Progress - Development<br />
    62. 62. Tracking Progress - Development<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 PBIs…<br />
    63. 63. Tracking Progress - Development<br />The Scrum Master opens an issue to track the problem the portal has identified<br />
    64. 64. Tracking Progress - Development<br />The issue is opened and tracked in TFS<br />
    65. 65. Tracking Progress – QA<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 />
    66. 66. Tracking Progress - QA<br />Rich set of reports track progress<br />
    67. 67. Product Backlog<br /> Daily<br />Sprint<br />Sprint <br />Backlog<br /> Potentially Shippable Increment<br />
    68. 68. vNextA few agile driven features coming to TFS<br />
    69. 69. Sprint Planning ToolCapacity & Sprint Burndown<br />Burndown progress<br /><ul><li>The enhanced work item management tools in Team Web Access
    70. 70. Tool pre-populates required data
    71. 71. Streamlines the association and update process.
    72. 72. Effectively allocate work balancing load with available capacity
    73. 73. Real-time feedback on the updates to the plan</li></ul>Team capacity at a glance<br />
    74. 74. Task Board in Team Web Accessupdate the status of work items visually<br />Burndown progress<br />Easily move tasks around<br />
    75. 75. Team NavigatorMy Work<br /><ul><li>Allows the developer to easily context switch
    76. 76. Packages all the open work
    77. 77. Save entire environment settings
    78. 78. Fix urgent bugs
    79. 79. Recall task, work is instantly restored in context and error-free.
    80. 80. Resume where the developer left off</li></li></ul><li>© 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.

    ×