Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Gerard beckerleg scrum and tfs 2012

6,598 views

Published on

Slide of talk I did at Microsoft in Canberra and the Sydney .NET user group. See the video at http://www.youtube.com/watch?v=9MRbY8RqQdU

Published in: Technology
  • Be the first to comment

Gerard beckerleg scrum and tfs 2012

  1. 1. Scrum with TFS 2012Gerard BeckerlegSenior Software ArchitectLive Backchannel: #NETUG Delivering Awesome Web Applications
  2. 2. About me Gerard Beckerleg from England Senior Software Architect at SSW Teacher at UTS (.NET and SharePoint) Professional Scrum Developer Experience in traditional waterfall development Experience in Agile/Scrum development  Sydney Airport (Macquarie Airports)  National Australia Day Council  Toll
  3. 3. History of Scrum at SSW 1990 “rough” agile practices + waterfall projects 2000 Kent Beck book - Extreme Programming SSW generally following the 12 principles of XP 2005 TFS released with agile template 2009 Scrum 2010 Microsoft release Scrum template 2011 Scrum updated 2011 Chief Architect Adam Cogan, ALM MVP of the year
  4. 4. Agenda Our Backlog Part 1 Agile and Scrum theory Part 2 Manual - Walkthrough project using Scrum Part 3 Tools - Walkthrough using TFS 2012 and Scrum Template v2.1 Delivering Awesome Web Applications
  5. 5. Part 1 - Agile and Scrum theory
  6. 6. Agile Manifesto (agilemanifesto.org) Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
  7. 7. Visibility Ability to Change Business Value Agile Plan driven development (Traditional) @elegantcoder
  8. 8. @microsoft
  9. 9. @microsoft
  10. 10. Scrumdamentals 3 Roles 3 Artefacts 5 Events
  11. 11. 3 Roles (Scrum Team) Product Owner Scrum Master Development Team
  12. 12. 3 Artefacts Increment Product Backlog Sprint Backlog
  13. 13. 5 Events Sprint Sprint  Sprint Planning  Daily Scrum Retrospective  Sprint Review Daily Scrum Planning Review  Retrospective
  14. 14. Delivering Awesome Web Applications
  15. 15. Part 2 - Manual - walkthrough projectusing Scrum
  16. 16. Step 1 - Initial Meeting Needs App ? Monitor her wealth ? Role The Product Owner (PO) Delivering Awesome Web Applications
  17. 17. Step 2 - Backlog Construction Create Product Backlog Items (PBI)  Features  Technical Work  Bugs  Knowledge acquisition Each PBI requires:  Description  Priority  Estimate Delivering Awesome Web Applications
  18. 18. The Sprint (Steps 3 to 8) Sprint Planning Daily Scrum Sprint Review  Product Increment  Product Feedback Retrospective
  19. 19. Step 3 - Sprint Planning What How
  20. 20. 5 Balance summary3 3 Set up staging server 3 Set up production server
  21. 21. To Do In Progress Done 5 Balance summary 3 Set upstaging server 3 Set up production server
  22. 22. To Do In Progress Done 8 5 Partial view Balance summary 8 Master page 1 3 DNS Set upstaging server Provision 4 server 3 1 Set up DNS production server Provision 4 server
  23. 23. Backlog Accuracy and Item Detail Vague Understood Estimated PBIs Tasks Other Next Next Next This Backlog Next Release Sprint Sprint Items Sprint richard@accentient.com
  24. 24. Step 4 - Day to day activities duringthe Sprint Daily Scrum Development Product Backlog Grooming
  25. 25. To Do In Progress Done 4 5 Partial view Balance summary 0 Master page 1 3 DNS Set upstaging server Provision 0 server 3 1 Set up DNS production server Provision 4 server
  26. 26. Burndown35302520151050 Mon Tues Wed Thur Fri Work Remaining
  27. 27. Steps 5,6,7 - The Sprint Review Gather feedback from Product Increment But wait….is your Product Increment really done?
  28. 28. Step 8 - The Sprint Retrospective Inspect and adapt 3 Questions  What went well (reinforce good behaviour)  What didn’t go well  What can we improve for the next sprint Output is actionable item(s) for Product Backlog
  29. 29. Part 3 Tools - Walkthrough using TFS2012 and Scrum Template v2.1 Delivering Awesome Web Applications
  30. 30. Summary Part 1 Agile and Scrum theory Part 2 Manual - Walkthrough project using Scrum Part 3 Tools - Walkthrough using TFS 2012 and Scrum Template v2.1 Delivering Awesome Web Applications
  31. 31. Links http://agilemanifesto.org/ http://scrum.org/ http://rules.ssw.com.au/Management/RulesToBetterScrum UsingTFS/PublishingImages/8StepstoScrum.pdf http://rules.ssw.com.au/management/rulestobetterscrumusi ngtfs/Pages/default.aspx http://rules.ssw.com.au/management/rulestomanagingsoftw areconsultants/pages/default.aspx
  32. 32. 3 things• @gerardbeckerleg• gerardbeckerleg@ssw.com.au• http://gerardbeckerleg.wordpress.com Delivering Awesome Web Applications
  33. 33. Thank You!Sydneyinfo@ssw.com.auwww.ssw.com.au Delivering Awesome Web Applications

×