SlideShare une entreprise Scribd logo
1  sur  41
Télécharger pour lire hors ligne
An Introduction
   to Scrum

    Wm. Barrett Simms
         @wbsimms
   barrett@wbsimms.com
We‘re losing the relay race

    ―The… ‗relay race‘ approach to product
    development…may conflict with the goals
    of maximum speed and flexibility. Instead
    a holistic or ‗rugby‘ approach—where a
    team tries to go the distance as a unit,
    passing the ball back and forth—may
    better serve today‘s competitive
    requirements.‖      Hirotaka Takeuchi and Ikujiro Nonaka, ―The
                               New New Product Development Game‖,
                               Harvard Business Review, January 1986.
Scrum in 100 words

• Scrum is an agile process that allows us to focus on
  delivering the highest business value in the shortest
  time.
• It allows us to rapidly and repeatedly inspect actual
  working product (every two weeks to one month).
• The business sets the priorities. Teams self-organize to
  determine the best way to deliver the highest priority
  features.
• Every two weeks to a month anyone can see real
  product.
Scrum has been used by:
 •Microsoft           •Intuit
 •Yahoo               •Nielsen Media
 •Google              •First American Real Estate
 •Electronic Arts     •BMC Software
 •High Moon Studios   •Ipswitch
 •Lockheed Martin     •John Deere
 •Philips             •Lexis Nexis
 •Siemens             •Sabre
 •Nokia               •Salesforce.com
 •Capital One         •Time Warner
 •BBC                 •Turner Broadcasting
 •Intuit              •Oce
Scrum has been used for:
•   Commercial software         • Video game development
•   In-house development        • FDA-approved, life-critical
                                  systems
•   Contract development
•   Fixed-price projects
                                • Satellite-control software

•   Financial applications
                                • Websites
•   ISO 9001-certified
                                • Handheld software
    applications                • Mobile phones
•   Embedded systems            • Network switching applications
•   24x7 systems with 99.999%   • ISV applications
    uptime requirements         • Some of the largest
•   the Joint Strike Fighter      applications in use
Characteristics
•   Self-organizing teams
•   Product progresses in a series of ―sprints‖
•   Requirements are captured as items in a list of
    ―product backlog‖
•   No specific product development practices
    prescribed
•   Uses generative rules to create an agile
    environment for delivering projects
•   One of the ―agile processes‖
The Agile Manifesto–a statement
of values

  Individuals and
                          over        Process and tools
    interactions
                                       Comprehensive
  Quality Workd           over
                                       documentation
    Customer
                          over       Contract negotiation
   collaboration
  Responding to
                          over        Following a plan
     change
    Source: www.agilemanifesto.org
Project noise level


      Far from
    Agreement
                                                Anarchy
           Requirements


                                      Complex


                                                       Source: Strategic Management and
                                                       Organizational Dynamics by Ralph
                                                       Stacey in Agile Software Development
                                                       with Scrum by Ken Schwaber and Mike
      Close to            Simple                       Beedle.

    Agreement
                          Certainty
                          Close to




                                                     Certainty
                                                     Far from
                                       Technology
Scrum
                            24 hours




                               Sprint
                             2-4 weeks
  Sprint goal
     Return
                   Sprint                Potentially shippable
  Cancel
  Return          backlog                 product increment
   Coupons
   Gift wrap
 Gift wrap
  Cancel        Coupons
   Product
   backlog
Putting it all together




              Image available at
      www.mountaingoatsoftware.com/scrum
Sprints
• Scrum projects make progress in a series
    of ―sprints‖
    •   Analogous to Extreme Programming iterations
• Typical duration is 2–4 weeks or a
    calendar month at most
•   A constant duration leads to a better
    rhythm
•   Product is designed, coded, and tested
    during the sprint
Sequential vs. overlapping
development

 Requirement
                              Design                    Code    Test
      s


        Rather than doing all
        of one thing at a
        time...               ...Scrum teams do a
                              little of everything all
                              the time


  Source: ―The New New Product Development Game‖ by
  Takeuchi and Nonaka. Harvard Business Review, January 1986.
No changes during a sprint

    Change




• Plan sprint durations around how long you
  can commit to keeping change out of the
  sprint
Scrum framework
 Roles
 •Product owner
 •ScrumMaster
 •Team          Ceremonies
              •Sprint planning
              •Sprint review
              •Sprint retrospective
              •Daily scrum meeting
                          Artifacts
                          •Product backlog
                          •Sprint backlog
                          •Burndown charts
Scrum framework
 Roles
 •Product owner
 •ScrumMaster
 •Team          Ceremonies
              •Sprint planning
              •Sprint review
              •Sprint retrospective
              •Daily scrum meeting
                          Artifacts
                          •Product backlog
                          •Sprint backlog
                          •Burndown charts
Product owner
• Define the features of the product
• Decide on release date and content
• Be responsible for the profitability of the
    product (ROI)
•   Prioritize features according to market
    value
•   Adjust features and priority every iteration,
    as needed
•   Accept or reject work results
The ScrumMaster
•   Represents management to the project
•   Responsible for enacting Scrum values and
    practices
•   Removes impediments
•   Ensure that the team is fully functional and
    productive
•   Enable close cooperation across all roles and
    functions
•   Shield the team from external interferences
The team
•   Typically 5-9 people
•   Cross-functional:
    •   Programmers, testers, user experience
        designers, etc.
•   Members should be full-time
    •   May be exceptions (e.g., database administrator)
Scrum framework
 Roles
 •Product owner
 •ScrumMaster
 •Team
                  Ceremonies
                  •Sprint planning
                  •Sprint review
                  •Sprint retrospective
                  •Daily scrum meeting
                             Artifacts
                             •Product backlog
                             •Sprint backlog
                             •Burndown charts
Team
             Sprint planning meeting
 capacity
              Sprint prioritization

 Product      •   Analyze and evaluate product       Sprint
 backlog          backlog                             goal
              •   Select sprint goal

Business
conditions    Sprint planning
              •   Decide how to achieve sprint
 Current          goal (design)                       Sprint
 product      •   Create sprint backlog (tasks)
                  from product backlog items         backlog
                  (user stories / features)
Technology    •   Estimate sprint backlog in hours
Sprint planning
 • Team selects items from the product backlog
     they can commit to completing
 •   Sprint backlog is created
     •   Tasks are identified and each is estimated (1-16
         hours)
     •   Collaboratively, not done alone by the ScrumMaster
 •   High-level design is considered
     As a vacation                Code the middle tier (8 hours)
     planner, I want to           Code the user interface (4)
     see photos of the            Write test fixtures (4)

     hotels.
                                  Code the foo class (6)
                                  Update performance tests (4)
The daily scrum
• Parameters
  •   Daily
  •   15-minutes
  •   Stand-up
• Not for problem solving
  •   Whole world is invited
  •   Only team members, ScrumMaster, product
      owner, can talk
• Helps avoid other unnecessary meetings
Everyone answers 3 questions
                                       1
      What did you do yesterday?

                                       2
      What will you do today?

                                       3
      Is anything in your way?
• These are not status for the ScrumMaster
 •   They are commitments in front of peers
The sprint review
• Team presents what it accomplished
    during the sprint
•   Typically takes the form of a demo of new
    features or underlying architecture
•   Informal
    •   2-hour prep time rule
    •   No slides
• Whole team participates
• Invite the world
Sprint retrospective
• Periodically take a look at what is and is
    not working
•   Typically 15–30 minutes
•   Done after every sprint
•   Whole team participates
    •   ScrumMaster
    •   Product owner
    •   Team
    •   Possibly customers and others
Start / Stop / Continue
• Whole team gathers and discusses what
  they‘d like to:
        Start doing

                      Stop doing
   This is just one
   of many ways to        Continue doing
      do a sprint
    retrospective.
Scrum framework
 Roles
 •Product owner
 •ScrumMaster
 •Team          Ceremonies
              •Sprint planning
              •Sprint review
              •Sprint retrospective
              •Daily scrum meeting
                          Artifacts
                          •Product backlog
                          •Sprint backlog
                          •Burndown charts
Product backlog
                      • The requirements
                      • A list of all desired work on
                        the project
                      • Ideally expressed such that
                        each item has value to the
                        users or customers of the
                        product
                      • Prioritized by the product
                        owner
                      • Reprioritized at the start of
       This is the      each sprint
    product backlog
A sample product backlog
            Backlog item                     Estimate
 Allow a guest to make a reservation            3
 As a guest, I want to cancel a
                                                5
 reservation.
 As a guest, I want to change the dates of
                                                3
 a reservation.
 As a hotel employee, I can run RevPAR
                                                8
 reports (revenue-per-available-room)
 Improve exception handling                     8
 ...                                            30
 ...                                            50
The sprint goal
• A short statement of what the work will be
   focused on during the sprint
                                  Life Sciences
                              Support features necessary for
Database Application          population genetics studies.

Make the application run on SQL
Server in addition to Oracle.
                                  Financial services
                                  Support more technical indicators
                                  than company ABC with real-
                                  time, streaming data.
Managing the sprint backlog
•   Individuals sign up for work of their own
    choosing
    •   Work is never assigned
•   Estimated work remaining is updated daily
Managing the sprint backlog
•   Any team member can add, delete or change
    the sprint backlog
•   Work for the sprint emerges
•   If work is unclear, define a sprint backlog item
    with a larger amount of time and break it down
    later
•   Update work remaining as more becomes
    known
A sprint backlog

          Tasks            Mon Tues Wed Thur Fri
 Code the user interface     8    4    8
 Code the middle tier       16   12   10   4
 Test the middle tier        8   16   16   11   8
 Write online help          12
 Write the foo class         8    8    8   8    8
 Add error logging                     8   4
A sprint burndown chart
Hours
Tasks                Mon Tues Wed Thur Fri
Code the user interface          8      4      8
Code the middle tier            16     12     10      7
Test the middle tier             8     16     16     11   8
Write online help               12


              50
              40
              30
      Hours




              20
              10
               0
                   Mon   Tue     Wed        Thu    Fri
Scalability
 •   Typical individual team is 7 ± 2 people
     •   Scalability comes from teams of teams
 •   Factors in scaling
     •   Type of application
     •   Team size
     •   Team dispersion
     •   Project duration
 •   Scrum has been used on multiple 500+
     person projects
Scaling through the Scrum of
scrums
Scrum of scrums of scrums
Where to go next
•   www.mountaingoatsoftware.com/scrum
•   www.scrumalliance.org
•   www.controlchaos.com
•   scrumdevelopment@yahoogroups.com
A Scrum reading list
•   Agile and Iterative Development: A Manager’s Guide by
    Craig Larman
•   Agile Estimating and Planning by Mike Cohn
•   Agile Project Management with Scrum by Ken Schwaber
•   Agile Retrospectives by Esther Derby and Diana Larsen
A Scrum reading list
•   Agile Software Development Ecosystems by Jim Highsmith
•   Agile Software Development with Scrum by Ken Schwaber
    and
    Mike Beedle
•   Scrum and The Enterprise by Ken Schwaber
•   Succeeding with Agile by Mike Cohn
•   User Stories Applied for Agile Software Development by
    Mike Cohn

Contenu connexe

Tendances

Hanno Jarvet BeWise loeng "An Introduction to Scrum" (20.11.2013 EBS)
Hanno Jarvet BeWise loeng "An Introduction to Scrum" (20.11.2013 EBS)Hanno Jarvet BeWise loeng "An Introduction to Scrum" (20.11.2013 EBS)
Hanno Jarvet BeWise loeng "An Introduction to Scrum" (20.11.2013 EBS)JCI Tallinn BeWise
 
Avantica presentacion scrum
Avantica presentacion scrumAvantica presentacion scrum
Avantica presentacion scrumJl Ballon V
 
Agile Software Development With Scrum
Agile Software Development With ScrumAgile Software Development With Scrum
Agile Software Development With ScrumSameera Gayan
 
Standardization and strategy in agile
Standardization and strategy in agileStandardization and strategy in agile
Standardization and strategy in agileNaveen Gupta
 
Intro to Scrum - Balance Internet
Intro to Scrum - Balance InternetIntro to Scrum - Balance Internet
Intro to Scrum - Balance InternetHoang Nguyen
 
Managing Scope Time Cost And Team In Agile
Managing Scope Time Cost And Team In AgileManaging Scope Time Cost And Team In Agile
Managing Scope Time Cost And Team In Agilemlaulin
 
Let's Talk About Scrum
Let's Talk About ScrumLet's Talk About Scrum
Let's Talk About ScrumScott Vandehey
 
Agile Session @ Universidade Portucalense
Agile Session @ Universidade PortucalenseAgile Session @ Universidade Portucalense
Agile Session @ Universidade PortucalenseRui M. Barreira
 
SCRUM and Poker Game In Agile Project
SCRUM and Poker Game In Agile ProjectSCRUM and Poker Game In Agile Project
SCRUM and Poker Game In Agile ProjectNhan Nguyen
 
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mix
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mixVladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mix
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mixVladimirs Ivanovs
 
Scrum in Practice
Scrum in PracticeScrum in Practice
Scrum in PracticeNaresh Jain
 

Tendances (20)

Hanno Jarvet BeWise loeng "An Introduction to Scrum" (20.11.2013 EBS)
Hanno Jarvet BeWise loeng "An Introduction to Scrum" (20.11.2013 EBS)Hanno Jarvet BeWise loeng "An Introduction to Scrum" (20.11.2013 EBS)
Hanno Jarvet BeWise loeng "An Introduction to Scrum" (20.11.2013 EBS)
 
Avantica presentacion scrum
Avantica presentacion scrumAvantica presentacion scrum
Avantica presentacion scrum
 
Scrum introduction
Scrum introductionScrum introduction
Scrum introduction
 
Scrum wall images by tobias mayer
Scrum wall images by tobias mayerScrum wall images by tobias mayer
Scrum wall images by tobias mayer
 
Introduction to scrum & agile
Introduction to scrum & agileIntroduction to scrum & agile
Introduction to scrum & agile
 
Agile Software Development With Scrum
Agile Software Development With ScrumAgile Software Development With Scrum
Agile Software Development With Scrum
 
Standardization and strategy in agile
Standardization and strategy in agileStandardization and strategy in agile
Standardization and strategy in agile
 
Intro to Scrum - Balance Internet
Intro to Scrum - Balance InternetIntro to Scrum - Balance Internet
Intro to Scrum - Balance Internet
 
Managing Scope Time Cost And Team In Agile
Managing Scope Time Cost And Team In AgileManaging Scope Time Cost And Team In Agile
Managing Scope Time Cost And Team In Agile
 
Let's Talk About Scrum
Let's Talk About ScrumLet's Talk About Scrum
Let's Talk About Scrum
 
Agile intro module 1
Agile intro   module 1Agile intro   module 1
Agile intro module 1
 
Agile Session @ Universidade Portucalense
Agile Session @ Universidade PortucalenseAgile Session @ Universidade Portucalense
Agile Session @ Universidade Portucalense
 
SCRUM and Poker Game In Agile Project
SCRUM and Poker Game In Agile ProjectSCRUM and Poker Game In Agile Project
SCRUM and Poker Game In Agile Project
 
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mix
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mixVladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mix
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mix
 
Agile scrum
Agile scrumAgile scrum
Agile scrum
 
Introduction to Scrum - Agile Methods
Introduction to Scrum - Agile MethodsIntroduction to Scrum - Agile Methods
Introduction to Scrum - Agile Methods
 
Agile Project Management using Scrum
Agile Project Management using ScrumAgile Project Management using Scrum
Agile Project Management using Scrum
 
Agile by KD
Agile by KDAgile by KD
Agile by KD
 
Scrum in Practice
Scrum in PracticeScrum in Practice
Scrum in Practice
 
Scrum toufiq
Scrum toufiqScrum toufiq
Scrum toufiq
 

En vedette

shinwari saltish
shinwari saltishshinwari saltish
shinwari saltishJia Usaf
 
Software Development And Delivery Metrics That Matter
Software Development And Delivery Metrics That MatterSoftware Development And Delivery Metrics That Matter
Software Development And Delivery Metrics That MatterWilliam Simms
 
Unit Testing and Tools
Unit Testing and ToolsUnit Testing and Tools
Unit Testing and ToolsWilliam Simms
 
Negotiation skills ppt.odp
Negotiation skills ppt.odpNegotiation skills ppt.odp
Negotiation skills ppt.odpHari Kudchadkar
 
Big Data Overview Part 1
Big Data Overview Part 1Big Data Overview Part 1
Big Data Overview Part 1William Simms
 
Bir elektronikçinin mutluluk formülü.
Bir elektronikçinin mutluluk formülü.Bir elektronikçinin mutluluk formülü.
Bir elektronikçinin mutluluk formülü.murat-yaman.com
 
Oriental theatre Presentation - Dramatics
Oriental theatre Presentation - DramaticsOriental theatre Presentation - Dramatics
Oriental theatre Presentation - DramaticsHari Kudchadkar
 
E commerce business model strategy opportunities and challenges in
E commerce business model strategy opportunities and challenges inE commerce business model strategy opportunities and challenges in
E commerce business model strategy opportunities and challenges inHaroldo Monteiro da Silva Filho
 
French Theatre Presentation - Dramatics Class
French Theatre Presentation - Dramatics ClassFrench Theatre Presentation - Dramatics Class
French Theatre Presentation - Dramatics ClassHari Kudchadkar
 
The art of selling fashion franchises through storytelling
The art of selling fashion franchises through  storytellingThe art of selling fashion franchises through  storytelling
The art of selling fashion franchises through storytellingHaroldo Monteiro da Silva Filho
 
스타트업 홍보의 이론과 실제 20130323
스타트업 홍보의 이론과 실제 20130323스타트업 홍보의 이론과 실제 20130323
스타트업 홍보의 이론과 실제 20130323YoonTaeSup
 
Toyota's Team Culture Case Presentation
Toyota's Team Culture Case PresentationToyota's Team Culture Case Presentation
Toyota's Team Culture Case PresentationHari Kudchadkar
 
Intergroup conflict
Intergroup conflictIntergroup conflict
Intergroup conflictJia Usaf
 
News beats journalism ppt final
News beats   journalism ppt finalNews beats   journalism ppt final
News beats journalism ppt finalHari Kudchadkar
 
Medical Tourism Presentation
Medical Tourism PresentationMedical Tourism Presentation
Medical Tourism PresentationHari Kudchadkar
 

En vedette (17)

shinwari saltish
shinwari saltishshinwari saltish
shinwari saltish
 
Software Development And Delivery Metrics That Matter
Software Development And Delivery Metrics That MatterSoftware Development And Delivery Metrics That Matter
Software Development And Delivery Metrics That Matter
 
Insights of Brazilian Luxury Market Palestra UBIFRANCE
Insights of Brazilian Luxury Market Palestra UBIFRANCEInsights of Brazilian Luxury Market Palestra UBIFRANCE
Insights of Brazilian Luxury Market Palestra UBIFRANCE
 
Unit Testing and Tools
Unit Testing and ToolsUnit Testing and Tools
Unit Testing and Tools
 
Negotiation skills ppt.odp
Negotiation skills ppt.odpNegotiation skills ppt.odp
Negotiation skills ppt.odp
 
Big Data Overview Part 1
Big Data Overview Part 1Big Data Overview Part 1
Big Data Overview Part 1
 
Bir elektronikçinin mutluluk formülü.
Bir elektronikçinin mutluluk formülü.Bir elektronikçinin mutluluk formülü.
Bir elektronikçinin mutluluk formülü.
 
Oriental theatre Presentation - Dramatics
Oriental theatre Presentation - DramaticsOriental theatre Presentation - Dramatics
Oriental theatre Presentation - Dramatics
 
E commerce business model strategy opportunities and challenges in
E commerce business model strategy opportunities and challenges inE commerce business model strategy opportunities and challenges in
E commerce business model strategy opportunities and challenges in
 
French Theatre Presentation - Dramatics Class
French Theatre Presentation - Dramatics ClassFrench Theatre Presentation - Dramatics Class
French Theatre Presentation - Dramatics Class
 
The art of selling fashion franchises through storytelling
The art of selling fashion franchises through  storytellingThe art of selling fashion franchises through  storytelling
The art of selling fashion franchises through storytelling
 
스타트업 홍보의 이론과 실제 20130323
스타트업 홍보의 이론과 실제 20130323스타트업 홍보의 이론과 실제 20130323
스타트업 홍보의 이론과 실제 20130323
 
The fashion franchising market in brazil
The fashion franchising market in brazilThe fashion franchising market in brazil
The fashion franchising market in brazil
 
Toyota's Team Culture Case Presentation
Toyota's Team Culture Case PresentationToyota's Team Culture Case Presentation
Toyota's Team Culture Case Presentation
 
Intergroup conflict
Intergroup conflictIntergroup conflict
Intergroup conflict
 
News beats journalism ppt final
News beats   journalism ppt finalNews beats   journalism ppt final
News beats journalism ppt final
 
Medical Tourism Presentation
Medical Tourism PresentationMedical Tourism Presentation
Medical Tourism Presentation
 

Similaire à Introduction to scrum

Agile Scrum Training Process
Agile Scrum Training ProcessAgile Scrum Training Process
Agile Scrum Training ProcessClarion Marketing
 
English-Redistributable-Intro-Scrum (1) (1).ppt
English-Redistributable-Intro-Scrum (1) (1).pptEnglish-Redistributable-Intro-Scrum (1) (1).ppt
English-Redistributable-Intro-Scrum (1) (1).pptShwetaPuneyani1
 
Introduction to scrum
Introduction to scrumIntroduction to scrum
Introduction to scrumSemen Arslan
 
Practicing Agile through Scrum
Practicing Agile through ScrumPracticing Agile through Scrum
Practicing Agile through ScrumNaveen Kumar Singh
 
Introduction to Agile software testing
Introduction to Agile software testingIntroduction to Agile software testing
Introduction to Agile software testingKMS Technology
 
English-RedistributableIntroToScrumPPT.pptx
English-RedistributableIntroToScrumPPT.pptxEnglish-RedistributableIntroToScrumPPT.pptx
English-RedistributableIntroToScrumPPT.pptxGayanHewage2
 
Agile – scrum +
Agile – scrum +Agile – scrum +
Agile – scrum +Alon Lahav
 
22-AnOverviewOfScrum.pptx
22-AnOverviewOfScrum.pptx22-AnOverviewOfScrum.pptx
22-AnOverviewOfScrum.pptxHelenCandy2
 
English redistributable-intro-scrum
English redistributable-intro-scrumEnglish redistributable-intro-scrum
English redistributable-intro-scrumSean Mike
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to ScrumHussam Ahmad
 
Introducing Scrum a Collaboration Game
Introducing Scrum a Collaboration GameIntroducing Scrum a Collaboration Game
Introducing Scrum a Collaboration GameAgile ME
 
Redistributable introtoscrum
Redistributable introtoscrumRedistributable introtoscrum
Redistributable introtoscrumNguyen Quang
 

Similaire à Introduction to scrum (20)

Scrum Training
Scrum TrainingScrum Training
Scrum Training
 
scrum
scrumscrum
scrum
 
Agile Scrum Training Process
Agile Scrum Training ProcessAgile Scrum Training Process
Agile Scrum Training Process
 
Scrum.ppt
Scrum.pptScrum.ppt
Scrum.ppt
 
English-Redistributable-Intro-Scrum (1) (1).ppt
English-Redistributable-Intro-Scrum (1) (1).pptEnglish-Redistributable-Intro-Scrum (1) (1).ppt
English-Redistributable-Intro-Scrum (1) (1).ppt
 
Agile and Scrum 101 –PMI Central Indiana Chapter - Michael Nir - Slide deck
Agile and Scrum 101 –PMI Central Indiana Chapter -  Michael Nir - Slide deckAgile and Scrum 101 –PMI Central Indiana Chapter -  Michael Nir - Slide deck
Agile and Scrum 101 –PMI Central Indiana Chapter - Michael Nir - Slide deck
 
Introduction to scrum
Introduction to scrumIntroduction to scrum
Introduction to scrum
 
Practicing Agile through Scrum
Practicing Agile through ScrumPracticing Agile through Scrum
Practicing Agile through Scrum
 
Scrum 101
Scrum 101 Scrum 101
Scrum 101
 
Introduction to Agile software testing
Introduction to Agile software testingIntroduction to Agile software testing
Introduction to Agile software testing
 
English-RedistributableIntroToScrumPPT.pptx
English-RedistributableIntroToScrumPPT.pptxEnglish-RedistributableIntroToScrumPPT.pptx
English-RedistributableIntroToScrumPPT.pptx
 
Agile – scrum +
Agile – scrum +Agile – scrum +
Agile – scrum +
 
22-AnOverviewOfScrum.pptx
22-AnOverviewOfScrum.pptx22-AnOverviewOfScrum.pptx
22-AnOverviewOfScrum.pptx
 
English redistributable-intro-scrum
English redistributable-intro-scrumEnglish redistributable-intro-scrum
English redistributable-intro-scrum
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 
Agile intro module 1
Agile intro   module 1Agile intro   module 1
Agile intro module 1
 
Introducing Scrum a Collaboration Game
Introducing Scrum a Collaboration GameIntroducing Scrum a Collaboration Game
Introducing Scrum a Collaboration Game
 
Introducing scrum
Introducing scrumIntroducing scrum
Introducing scrum
 
Scrum
ScrumScrum
Scrum
 
Redistributable introtoscrum
Redistributable introtoscrumRedistributable introtoscrum
Redistributable introtoscrum
 

Plus de William Simms

Unit Testing and Tools - ADNUG
Unit Testing and Tools - ADNUGUnit Testing and Tools - ADNUG
Unit Testing and Tools - ADNUGWilliam Simms
 
ElasticSearch for data mining
ElasticSearch for data mining ElasticSearch for data mining
ElasticSearch for data mining William Simms
 
Continuous Integration - Step by Step
Continuous Integration - Step by StepContinuous Integration - Step by Step
Continuous Integration - Step by StepWilliam Simms
 
Introduction to Agile
Introduction to AgileIntroduction to Agile
Introduction to AgileWilliam Simms
 

Plus de William Simms (6)

Unit Testing and Tools - ADNUG
Unit Testing and Tools - ADNUGUnit Testing and Tools - ADNUG
Unit Testing and Tools - ADNUG
 
ElasticSearch for data mining
ElasticSearch for data mining ElasticSearch for data mining
ElasticSearch for data mining
 
Bootstrap Bootcamp
Bootstrap BootcampBootstrap Bootcamp
Bootstrap Bootcamp
 
Continuous Integration - Step by Step
Continuous Integration - Step by StepContinuous Integration - Step by Step
Continuous Integration - Step by Step
 
AWS vs Azure
AWS vs AzureAWS vs Azure
AWS vs Azure
 
Introduction to Agile
Introduction to AgileIntroduction to Agile
Introduction to Agile
 

Dernier

NIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopNIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopBachir Benyammi
 
Linked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond OntologiesLinked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond OntologiesDavid Newbury
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsSafe Software
 
Comparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and IstioComparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and IstioChristian Posta
 
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UbiTrack UK
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesMd Hossain Ali
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Websitedgelyza
 
Designing A Time bound resource download URL
Designing A Time bound resource download URLDesigning A Time bound resource download URL
Designing A Time bound resource download URLRuncy Oommen
 
How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?IES VE
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Will Schroeder
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Adtran
 
Videogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfVideogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfinfogdgmi
 
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfDianaGray10
 
Bird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemBird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemAsko Soukka
 
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAAnypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAshyamraj55
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxMatsuo Lab
 
UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6DianaGray10
 
AI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarAI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarPrecisely
 
Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1DianaGray10
 

Dernier (20)

NIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopNIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 Workshop
 
Linked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond OntologiesLinked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond Ontologies
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
 
Comparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and IstioComparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and Istio
 
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Website
 
Designing A Time bound resource download URL
Designing A Time bound resource download URLDesigning A Time bound resource download URL
Designing A Time bound resource download URL
 
How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™
 
Videogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfVideogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdf
 
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
 
Bird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemBird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystem
 
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAAnypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptx
 
20150722 - AGV
20150722 - AGV20150722 - AGV
20150722 - AGV
 
UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6
 
AI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarAI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity Webinar
 
Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1
 

Introduction to scrum

  • 1. An Introduction to Scrum Wm. Barrett Simms @wbsimms barrett@wbsimms.com
  • 2. We‘re losing the relay race ―The… ‗relay race‘ approach to product development…may conflict with the goals of maximum speed and flexibility. Instead a holistic or ‗rugby‘ approach—where a team tries to go the distance as a unit, passing the ball back and forth—may better serve today‘s competitive requirements.‖ Hirotaka Takeuchi and Ikujiro Nonaka, ―The New New Product Development Game‖, Harvard Business Review, January 1986.
  • 3. Scrum in 100 words • Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time. • It allows us to rapidly and repeatedly inspect actual working product (every two weeks to one month). • The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features. • Every two weeks to a month anyone can see real product.
  • 4. Scrum has been used by: •Microsoft •Intuit •Yahoo •Nielsen Media •Google •First American Real Estate •Electronic Arts •BMC Software •High Moon Studios •Ipswitch •Lockheed Martin •John Deere •Philips •Lexis Nexis •Siemens •Sabre •Nokia •Salesforce.com •Capital One •Time Warner •BBC •Turner Broadcasting •Intuit •Oce
  • 5. Scrum has been used for: • Commercial software • Video game development • In-house development • FDA-approved, life-critical systems • Contract development • Fixed-price projects • Satellite-control software • Financial applications • Websites • ISO 9001-certified • Handheld software applications • Mobile phones • Embedded systems • Network switching applications • 24x7 systems with 99.999% • ISV applications uptime requirements • Some of the largest • the Joint Strike Fighter applications in use
  • 6. Characteristics • Self-organizing teams • Product progresses in a series of ―sprints‖ • Requirements are captured as items in a list of ―product backlog‖ • No specific product development practices prescribed • Uses generative rules to create an agile environment for delivering projects • One of the ―agile processes‖
  • 7. The Agile Manifesto–a statement of values Individuals and over Process and tools interactions Comprehensive Quality Workd over documentation Customer over Contract negotiation collaboration Responding to over Following a plan change Source: www.agilemanifesto.org
  • 8. Project noise level Far from Agreement Anarchy Requirements Complex Source: Strategic Management and Organizational Dynamics by Ralph Stacey in Agile Software Development with Scrum by Ken Schwaber and Mike Close to Simple Beedle. Agreement Certainty Close to Certainty Far from Technology
  • 9. Scrum 24 hours Sprint 2-4 weeks Sprint goal Return Sprint Potentially shippable Cancel Return backlog product increment Coupons Gift wrap Gift wrap Cancel Coupons Product backlog
  • 10. Putting it all together Image available at www.mountaingoatsoftware.com/scrum
  • 11. Sprints • Scrum projects make progress in a series of ―sprints‖ • Analogous to Extreme Programming iterations • Typical duration is 2–4 weeks or a calendar month at most • A constant duration leads to a better rhythm • Product is designed, coded, and tested during the sprint
  • 12. Sequential vs. overlapping development Requirement Design Code Test s Rather than doing all of one thing at a time... ...Scrum teams do a little of everything all the time Source: ―The New New Product Development Game‖ by Takeuchi and Nonaka. Harvard Business Review, January 1986.
  • 13. No changes during a sprint Change • Plan sprint durations around how long you can commit to keeping change out of the sprint
  • 14. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts
  • 15. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts
  • 16. Product owner • Define the features of the product • Decide on release date and content • Be responsible for the profitability of the product (ROI) • Prioritize features according to market value • Adjust features and priority every iteration, as needed • Accept or reject work results
  • 17. The ScrumMaster • Represents management to the project • Responsible for enacting Scrum values and practices • Removes impediments • Ensure that the team is fully functional and productive • Enable close cooperation across all roles and functions • Shield the team from external interferences
  • 18. The team • Typically 5-9 people • Cross-functional: • Programmers, testers, user experience designers, etc. • Members should be full-time • May be exceptions (e.g., database administrator)
  • 19. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts
  • 20. Team Sprint planning meeting capacity Sprint prioritization Product • Analyze and evaluate product Sprint backlog backlog goal • Select sprint goal Business conditions Sprint planning • Decide how to achieve sprint Current goal (design) Sprint product • Create sprint backlog (tasks) from product backlog items backlog (user stories / features) Technology • Estimate sprint backlog in hours
  • 21. Sprint planning • Team selects items from the product backlog they can commit to completing • Sprint backlog is created • Tasks are identified and each is estimated (1-16 hours) • Collaboratively, not done alone by the ScrumMaster • High-level design is considered As a vacation Code the middle tier (8 hours) planner, I want to Code the user interface (4) see photos of the Write test fixtures (4) hotels. Code the foo class (6) Update performance tests (4)
  • 22. The daily scrum • Parameters • Daily • 15-minutes • Stand-up • Not for problem solving • Whole world is invited • Only team members, ScrumMaster, product owner, can talk • Helps avoid other unnecessary meetings
  • 23. Everyone answers 3 questions 1 What did you do yesterday? 2 What will you do today? 3 Is anything in your way? • These are not status for the ScrumMaster • They are commitments in front of peers
  • 24. The sprint review • Team presents what it accomplished during the sprint • Typically takes the form of a demo of new features or underlying architecture • Informal • 2-hour prep time rule • No slides • Whole team participates • Invite the world
  • 25. Sprint retrospective • Periodically take a look at what is and is not working • Typically 15–30 minutes • Done after every sprint • Whole team participates • ScrumMaster • Product owner • Team • Possibly customers and others
  • 26. Start / Stop / Continue • Whole team gathers and discusses what they‘d like to: Start doing Stop doing This is just one of many ways to Continue doing do a sprint retrospective.
  • 27. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts
  • 28. Product backlog • The requirements • A list of all desired work on the project • Ideally expressed such that each item has value to the users or customers of the product • Prioritized by the product owner • Reprioritized at the start of This is the each sprint product backlog
  • 29. A sample product backlog Backlog item Estimate Allow a guest to make a reservation 3 As a guest, I want to cancel a 5 reservation. As a guest, I want to change the dates of 3 a reservation. As a hotel employee, I can run RevPAR 8 reports (revenue-per-available-room) Improve exception handling 8 ... 30 ... 50
  • 30. The sprint goal • A short statement of what the work will be focused on during the sprint Life Sciences Support features necessary for Database Application population genetics studies. Make the application run on SQL Server in addition to Oracle. Financial services Support more technical indicators than company ABC with real- time, streaming data.
  • 31. Managing the sprint backlog • Individuals sign up for work of their own choosing • Work is never assigned • Estimated work remaining is updated daily
  • 32. Managing the sprint backlog • Any team member can add, delete or change the sprint backlog • Work for the sprint emerges • If work is unclear, define a sprint backlog item with a larger amount of time and break it down later • Update work remaining as more becomes known
  • 33. A sprint backlog Tasks Mon Tues Wed Thur Fri Code the user interface 8 4 8 Code the middle tier 16 12 10 4 Test the middle tier 8 16 16 11 8 Write online help 12 Write the foo class 8 8 8 8 8 Add error logging 8 4
  • 34. A sprint burndown chart Hours
  • 35. Tasks Mon Tues Wed Thur Fri Code the user interface 8 4 8 Code the middle tier 16 12 10 7 Test the middle tier 8 16 16 11 8 Write online help 12 50 40 30 Hours 20 10 0 Mon Tue Wed Thu Fri
  • 36. Scalability • Typical individual team is 7 ± 2 people • Scalability comes from teams of teams • Factors in scaling • Type of application • Team size • Team dispersion • Project duration • Scrum has been used on multiple 500+ person projects
  • 37. Scaling through the Scrum of scrums
  • 38. Scrum of scrums of scrums
  • 39. Where to go next • www.mountaingoatsoftware.com/scrum • www.scrumalliance.org • www.controlchaos.com • scrumdevelopment@yahoogroups.com
  • 40. A Scrum reading list • Agile and Iterative Development: A Manager’s Guide by Craig Larman • Agile Estimating and Planning by Mike Cohn • Agile Project Management with Scrum by Ken Schwaber • Agile Retrospectives by Esther Derby and Diana Larsen
  • 41. A Scrum reading list • Agile Software Development Ecosystems by Jim Highsmith • Agile Software Development with Scrum by Ken Schwaber and Mike Beedle • Scrum and The Enterprise by Ken Schwaber • Succeeding with Agile by Mike Cohn • User Stories Applied for Agile Software Development by Mike Cohn