Scrum With TFS 2010
- 1. 19th August 2011Microsoft Singapore ALM EventScrum withMicrosoftVisual Studio Team Foundation Server 2010Adrian Dunne | Microsoft Singapore
- 2. Team Foundation Server 2010
- 4. Source: Forrester Reasearch, Inc.
- 5. Why is Agile Catching On?5
- 6. Business Needs Demand It “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.”Diego Lo Giudice and Dave West, ForresterFebruary 2011Transforming Application Delivery
- 7. Value Delivered Early and OftenWorking software continually delivered
- 8. Regular discussions with stakeholders
- 9. Maximize ROIAgendaScrum with TFS 2010
- 12. Running a SprintProduct Backlog DailySprintSprint Backlog Potentially Shippable Increment
- 13. How do you Plan the Project?Product Backlog
- 14. Evolving backlog of Product Backlog Items
- 15. Describes what users need and value
- 16. Owned by the Product Owner
- 17. Prioritized by business value
- 18. Each PBI is written from the user’s perspectivePlanning the ProjectProduct Backlog“As a new customer I want to register online so I can use the services offered”Product Backlog Item58PBIs are listed on the backlog in priority orderThe team estimates the ‘effort’ for each PBI5Priority3New PBIs are added to the product backlog81
- 19. Product Backlog in TFS 2010 Product Backlog query
- 21. Prioritizing
- 22. Estimating effortDemoManaging the Product Backlog in TFS 2010
- 23. AgendaScrum with TFS 2010
- 26. Running a SprintProduct Backlog DailySprintSprint Backlog Potentially Shippable Increment
- 27. What is Sprint Planning?The product owner and the team add Product Backlog Itemsto the sprint
- 28. Each PBI is decomposed into tasks
- 29. The team makes a commitment to each PBIProduct BacklogIteration BacklogPBIsPlanning a SprintPBIsTasks (Points)Commit!Based on estimates the team commits to each PBI3The team thinks this PBI is more work than they can commit to…3During the sprint planning meeting, the product owner and the team add PBIs to the sprint3The team breaks down each story into tasksCommit!Can’t Commit!
- 30. Product BacklogIteration BacklogPBIsTasks (Points)Planning a SprintPBIsCommit!333The larger story is removed from the sprint and the team considers a smaller story on the backlogCommit!?3The sprint is now planned and the team is ready to get started!The team can commit to this smaller storyCommit!
- 31. Sprint PlanningBreak down PBIs into tasks
- 32. Team members Sign up for tasks
- 33. Commit
- 34. Track progressDemoPlanning a Sprint in TFS 2010
- 35. AgendaScrum with TFS 2010
- 38. Running a SprintProduct Backlog DailySprintSprint Backlog Potentially Shippable Increment
- 39. How do you Run a Sprint?Daily Scrum
- 40. What was done
- 41. What will be done
- 42. Impediments
- 43. Sprint Burn-down
- 44. Deliver a “potentially shippable” increment
- 45. Demo the value delivered
- 46. Retrospective Product BacklogIteration BacklogPBIsPBIsTasks (Points)Running a SprintThe team starts work on the tasks…
- 47. Running a SprintProduct BacklogIteration BacklogPBIsPBIsTasks (hours)Completed work is reported daily
- 48. Running a SprintProduct BacklogIteration BacklogPBIsPBIsTasks (hours)
- 49. Running a SprintProduct BacklogIteration BacklogPBIsPBIsTasks (hours)Each User PBI has been implementedAll work for the sprint is “done-done”
- 50. Product BacklogIteration BacklogPBIsPBIsTasks (hours)Running a SprintAnd the team has developed a “potentially shippable” incrementThe team holds a demo to show the value they have delivered
- 51. Running a SprintProduct BacklogIteration BacklogUser StoriesUser StoriesTasks (hours)The latest increment is shipped to customers
- 52. Running a SprintProduct BacklogIteration BacklogPBIsPBIsTasks (Points)PBIs and tasks are cleared from the backlog – the team delivered on its commitmentPBIs delivered in the last sprint are closedWhat worked? What didn’t work? What can the team do to improve?The team holds a retrospective…
- 53. Running a SprintProduct BacklogIteration BacklogPBIsPBIsTasks (Points)New PBIs are added to the Product Backlog
- 54. Running a SprintProduct BacklogIteration BacklogPBIsPBIsTasks (Points)The backlog is prioritized and ready for the team to plan the next sprint
- 55. Running a SprintRecord completed work daily
- 56. Track and Resolve Impediments
- 57. Track progress with reports and dashboards
- 58. RetrospectivesDemoRunning a Sprint in TFS 2010
- 59. Tracking Progress - DevelopmentBurndown chart tracks remaining and completed work
- 60. Tracking Progress - Development
- 61. Tracking Progress - Development
- 62. Tracking Progress - DevelopmentDetailed sprint progress is tracked on the project portalThe burndown shows the team on track…And almost half of the tasks remain openBut the team hasn’t closed any of the three PBIs…
- 63. Tracking Progress - DevelopmentThe Scrum Master opens an issue to track the problem the portal has identified
- 64. Tracking Progress - DevelopmentThe issue is opened and tracked in TFS
- 65. Tracking Progress – QAThe portal brings data together so it can be analyzed to ensure success on a sprintTest are passing…But bugs are climbing steadily
- 66. Tracking Progress - QARich set of reports track progress
- 67. Product Backlog DailySprintSprint Backlog Potentially Shippable Increment
- 68. vNextA few agile driven features coming to TFS
- 69. Sprint Planning ToolCapacity & Sprint BurndownBurndown progressThe enhanced work item management tools in Team Web Access
- 70. Tool pre-populates required data
- 71. Streamlines the association and update process.
- 72. Effectively allocate work balancing load with available capacity
- 73. Real-time feedback on the updates to the planTeam capacity at a glance
- 74. Task Board in Team Web Accessupdate the status of work items visuallyBurndown progressEasily move tasks around
- 75. Team NavigatorMy WorkAllows the developer to easily context switch
- 76. Packages all the open work
- 77. Save entire environment settings
- 78. Fix urgent bugs
- 79. Recall task, work is instantly restored in context and error-free.
- 80. Resume where the developer left off© 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.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.
Editor's Notes
- #3: Poster TFS ArchitectureUserreferencesVSS to TFS migration scenariosTest migration (actuallywrittenin Excel)
- #4: Poster TFS ArchitectureUserreferencesVSS to TFS migration scenariosTest migration (actuallywrittenin Excel)
- #19: Add animation and a “can’t commit”… Move a smaller up…
- #29: Add a not-finished… Red -
- #30: Add animation and a “can’t commit”… Move a smaller up…