Your SlideShare is downloading. ×
0
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
Scrum With TFS 2010
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

Scrum With TFS 2010

2,279

Published on

Microsoft Singapore Developer Days Event - August 2011

Microsoft Singapore Developer Days Event - August 2011

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

No Downloads
Views
Total Views
2,279
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
107
Comments
0
Likes
2
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
  • 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…
  • Transcript

    • 1. 19th August 2011
      Microsoft Singapore ALM Event
      Scrum withMicrosoftVisual Studio Team Foundation Server 2010
      Adrian Dunne | Microsoft Singapore
    • 2. Team Foundation Server 2010
    • 3. An Open Platform
    • 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, Forrester
      February 2011
      Transforming Application Delivery
    • 7. Value Delivered Early and Often
      • Working software continually delivered
      • 8. Regular discussions with stakeholders
      • 9. Maximize ROI
    • Agenda
      • Scrum with TFS 2010
      • 10. Planning the Project
      • 11. Planning a Sprint
      • 12. Running a Sprint
    • Product Backlog
      Daily
      Sprint
      Sprint
      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 perspective
    • Planning the Project
      Product Backlog
      “As a new customer I want to register online so I can use the services offered”
      Product Backlog Item
      5
      8
      PBIs are listed on the backlog in priority order
      The team estimates the ‘effort’ for each PBI
      5
      Priority
      3
      New PBIs are added to the product backlog
      8
      1
    • 19. Product Backlog in TFS 2010
      • Product Backlog query
      • 20. Creating new PBIs
      • 21. Prioritizing
      • 22. Estimating effort
    • DemoManaging the Product Backlog in TFS 2010
    • 23. Agenda
      • Scrum with TFS 2010
      • 24. Planning the Project
      • 25. Planning a Sprint
      • 26. Running a Sprint
    • Product Backlog
      Daily
      Sprint
      Sprint
      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 PBI
    • Product Backlog
      Iteration Backlog
      PBIs
      Planning a Sprint
      PBIs
      Tasks (Points)
      Commit!
      Based on estimates the team commits to each PBI
      3
      The team thinks this PBI is more work than they can commit to…
      3
      During the sprint planning meeting, the product owner and the team add PBIs to the sprint
      3
      The team breaks down each story into tasks
      Commit!
      Can’t Commit!
    • 30. Product Backlog
      Iteration Backlog
      PBIs
      Tasks (Points)
      Planning a Sprint
      PBIs
      Commit!
      3
      3
      3
      The larger story is removed from the sprint and the team considers a smaller story on the backlog
      Commit!
      ?
      3
      The sprint is now planned and the team is ready to get started!
      The team can commit to this smaller story
      Commit!
    • 31. Sprint Planning
      • Break down PBIs into tasks
      • 32. Team members Sign up for tasks
      • 33. Commit
      • 34. Track progress
    • DemoPlanning a Sprint in TFS 2010
    • 35. Agenda
      • Scrum with TFS 2010
      • 36. Planning the Project
      • 37. Planning a Sprint
      • 38. Running a Sprint
    • Product Backlog
      Daily
      Sprint
      Sprint
      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 Backlog
      Iteration Backlog
      PBIs
      PBIs
      Tasks (Points)
      Running a Sprint
      The team starts work on the tasks…
    • 47. Running a Sprint
      Product Backlog
      Iteration Backlog
      PBIs
      PBIs
      Tasks (hours)
      Completed work is reported daily
    • 48. Running a Sprint
      Product Backlog
      Iteration Backlog
      PBIs
      PBIs
      Tasks (hours)
    • 49. Running a Sprint
      Product Backlog
      Iteration Backlog
      PBIs
      PBIs
      Tasks (hours)
      Each User PBI has been implemented
      All work for the sprint is “done-done”
    • 50. Product Backlog
      Iteration Backlog
      PBIs
      PBIs
      Tasks (hours)
      Running a Sprint
      And the team has developed a “potentially shippable” increment
      The team holds a demo to show the value they have delivered
    • 51. Running a Sprint
      Product Backlog
      Iteration Backlog
      User Stories
      User Stories
      Tasks (hours)
      The latest increment is shipped to customers
    • 52. Running a Sprint
      Product Backlog
      Iteration Backlog
      PBIs
      PBIs
      Tasks (Points)
      PBIs and tasks are cleared from the backlog – the team delivered on its commitment
      PBIs delivered in the last sprint are closed
      What worked?
      What didn’t work? What can the team do to improve?
      The team holds a retrospective…
    • 53. Running a Sprint
      Product Backlog
      Iteration Backlog
      PBIs
      PBIs
      Tasks (Points)
      New PBIs are added to the Product Backlog
    • 54. Running a Sprint
      Product Backlog
      Iteration Backlog
      PBIs
      PBIs
      Tasks (Points)
      The backlog is prioritized and ready for the team to plan the next sprint
    • 55. Running a Sprint
      • Record completed work daily
      • 56. Track and Resolve Impediments
      • 57. Track progress with reports and dashboards
      • 58. Retrospectives
    • DemoRunning a Sprint in TFS 2010
    • 59. Tracking Progress - Development
      Burndown chart tracks remaining and completed work
    • 60. Tracking Progress - Development
    • 61. Tracking Progress - Development
    • 62. Tracking Progress - Development
      Detailed sprint progress is tracked on the project portal
      The burndown shows the team on track…
      And almost half of the tasks remain open
      But the team hasn’t closed any of the three PBIs…
    • 63. Tracking Progress - Development
      The Scrum Master opens an issue to track the problem the portal has identified
    • 64. Tracking Progress - Development
      The issue is opened and tracked in TFS
    • 65. Tracking Progress – QA
      The portal brings data together so it can be analyzed to ensure success on a sprint
      Test are passing…
      But bugs are climbing steadily
    • 66. Tracking Progress - QA
      Rich set of reports track progress
    • 67. Product Backlog
      Daily
      Sprint
      Sprint
      Backlog
      Potentially Shippable Increment
    • 68. vNextA few agile driven features coming to TFS
    • 69. Sprint Planning ToolCapacity & Sprint Burndown
      Burndown progress
      • The 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 plan
      Team capacity at a glance
    • 74. Task Board in Team Web Accessupdate the status of work items visually
      Burndown progress
      Easily move tasks around
    • 75. Team NavigatorMy Work
      • Allows 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.

    ×