Scrum with TFS 2012
Gerard Beckerleg
Senior Software Architect

Live Backchannel: #NETUG



                   Delivering Awesome Web Applications
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
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
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
Part 1 - Agile and Scrum theory
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
Visibility                           Ability to Change




             Business Value




                Agile
                Plan driven development (Traditional)

              @elegantcoder
@microsoft
@microsoft
Scrumdamentals
   3 Roles

   3 Artefacts

   5 Events
3 Roles (Scrum Team)
   Product Owner



   Scrum Master



   Development Team
3 Artefacts
   Increment



   Product Backlog



   Sprint Backlog
5 Events
   Sprint                                         Sprint
       Sprint Planning
       Daily Scrum




                                                                     Retrospective
       Sprint Review




                                     Daily Scrum
                          Planning




                                                            Review
       Retrospective
Delivering Awesome Web Applications
Part 2 - Manual - walkthrough project
using Scrum
Step 1 - Initial Meeting
   Needs App ?

   Monitor her wealth

   ? Role

   The Product Owner (PO)




                             Delivering Awesome Web Applications
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
The Sprint (Steps 3 to 8)
   Sprint Planning

   Daily Scrum

   Sprint Review
       Product Increment
       Product Feedback
   Retrospective
Step 3 - Sprint Planning
   What




   How
5
      Balance
      summary

3
                  3
        Set up
    staging server


                  3
       Set up
     production
       server
To Do   In Progress   Done



              5
  Balance
  summary


              3
    Set up
staging server


              3
   Set up
 production
   server
To Do            In Progress   Done



                                 8
              5   Partial view
  Balance
  summary                        8

                  Master page

                                 1
              3      DNS
    Set up
staging server     Provision     4


                    server

              3                  1

   Set up            DNS
 production
   server          Provision     4


                    server
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
Step 4 - Day to day activities during
the Sprint
   Daily Scrum

   Development

   Product Backlog Grooming
To Do          In Progress           Done


                                                 4
              5                   Partial view
  Balance
  summary                                                          0

                                                     Master page

                                                 1
              3                      DNS
    Set up
staging server                                        Provision    0


                                                       server

              3               1

   Set up           DNS
 production
   server         Provision   4


                   server
Burndown
35


30


25


20


15


10


5


0
     Mon   Tues       Wed          Thur   Fri

                  Work Remaining
Steps 5,6,7 - The Sprint Review
   Gather feedback from Product Increment




   But wait….is your Product Increment really done?
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
Part 3 Tools - Walkthrough using TFS
2012 and Scrum Template v2.1




                       Delivering Awesome Web Applications
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
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
3 things
•   @gerardbeckerleg
•   gerardbeckerleg@ssw.com.au
•   http://gerardbeckerleg.wordpress.com




                                       Delivering Awesome Web Applications
Thank You!
Sydney

info@ssw.com.au

www.ssw.com.au




                  Delivering Awesome Web Applications

Gerard beckerleg scrum and tfs 2012

  • 1.
    Scrum with TFS2012 Gerard Beckerleg Senior Software Architect Live Backchannel: #NETUG Delivering Awesome Web Applications
  • 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.
    History of Scrumat 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.
    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.
    Part 1 -Agile and Scrum theory
  • 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.
    Visibility Ability to Change Business Value Agile Plan driven development (Traditional) @elegantcoder
  • 8.
  • 9.
  • 11.
    Scrumdamentals  3 Roles  3 Artefacts  5 Events
  • 12.
    3 Roles (ScrumTeam)  Product Owner  Scrum Master  Development Team
  • 13.
    3 Artefacts  Increment  Product Backlog  Sprint Backlog
  • 14.
    5 Events  Sprint Sprint  Sprint Planning  Daily Scrum Retrospective  Sprint Review Daily Scrum Planning Review  Retrospective
  • 15.
  • 16.
    Part 2 -Manual - walkthrough project using Scrum
  • 18.
    Step 1 -Initial Meeting  Needs App ?  Monitor her wealth  ? Role  The Product Owner (PO) Delivering Awesome Web Applications
  • 20.
    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
  • 27.
    The Sprint (Steps3 to 8)  Sprint Planning  Daily Scrum  Sprint Review  Product Increment  Product Feedback  Retrospective
  • 29.
    Step 3 -Sprint Planning  What  How
  • 30.
    5 Balance summary 3 3 Set up staging server 3 Set up production server
  • 31.
    To Do In Progress Done 5 Balance summary 3 Set up staging server 3 Set up production server
  • 32.
    To Do In Progress Done 8 5 Partial view Balance summary 8 Master page 1 3 DNS Set up staging server Provision 4 server 3 1 Set up DNS production server Provision 4 server
  • 33.
    Backlog Accuracy andItem Detail Vague Understood Estimated PBIs Tasks Other Next Next Next This Backlog Next Release Sprint Sprint Items Sprint richard@accentient.com
  • 35.
    Step 4 -Day to day activities during the Sprint  Daily Scrum  Development  Product Backlog Grooming
  • 36.
    To Do In Progress Done 4 5 Partial view Balance summary 0 Master page 1 3 DNS Set up staging server Provision 0 server 3 1 Set up DNS production server Provision 4 server
  • 37.
    Burndown 35 30 25 20 15 10 5 0 Mon Tues Wed Thur Fri Work Remaining
  • 39.
    Steps 5,6,7 -The Sprint Review  Gather feedback from Product Increment  But wait….is your Product Increment really done?
  • 41.
    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
  • 42.
    Part 3 Tools- Walkthrough using TFS 2012 and Scrum Template v2.1 Delivering Awesome Web Applications
  • 59.
    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
  • 60.
    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
  • 61.
    3 things • @gerardbeckerleg • gerardbeckerleg@ssw.com.au • http://gerardbeckerleg.wordpress.com Delivering Awesome Web Applications
  • 62.
    Thank You! Sydney info@ssw.com.au www.ssw.com.au Delivering Awesome Web Applications

Editor's Notes

  • #6 I’m passionate about Scrum and want to share how we are currently doing things at SSW
  • #7 In February 2001, 17 software developers[6] met at the Snowbird, Utah resort, to discuss lightweight development methods. They published the Manifesto for Agile Software Development[1] to define the approach now known as agile software developmentKent BeckWard CunninghamMartin FowlerRobert C. MartinKen SchwaberJeff Sutherland
  • #9 Delivering a product increment
  • #11 Easy to learn difficult to masterRichard Hundhausen - P90X - cross-training (weight training, martial arts, yoga and calisthenics) and periodization, combined with a nutrition and dietary supplement plan
  • #13 PO – Decides the whatScrum Master – Guides the processDevelopment Team – Builds what the PO decides
  • #14 Product Backlog – Can be excel, is owned by the PO but groomed by the team
  • #15 Sprint – period of time between 1 and 3 weeks
  • #21 PBI are not tasks, talk in business language
  • #22 FeaturesBugsTechnical workKnowledge acquisitionAcceptance Criteria – Yeah but questions
  • #23 FeaturesBugsTechnical workKnowledge acquisitionAcceptance Criteria – Yeah but questions
  • #24 FeaturesBugsTechnical workKnowledge acquisitionAcceptance Criteria – Yeah but questions
  • #25 ComparativeRelative size
  • #26 FeaturesBugsTechnical workKnowledge acquisitionAcceptance Criteria – Yeah but questions
  • #30 What – PBI’sHow - Tasks
  • #43 High level to more detail
  • #61 High level to more detail