際際滷

際際滷Share a Scribd company logo
Scrum:
What s In It for Me?
 Prepared by Lisa Monta単o
Agenda
 Overview   of Agile and Scrum

 Scrum:   Product Vision & Product Owner Role

 Scrum:   Practices and ScrumMaster Role

 What   s in it for me?


                                              2
Overview of Agile and Scrum
Overview of Agile and Scrum

                      Agile Manifesto

 Agile    is a set of values:
   Individuals   and interactions over processes and
    tools
   Workingsoftware (Products) over
    comprehensive documentation
   Customer    collaboration over contract negotiation
   Responding    to change over following a plan


                                                       4
Overview of Agile and Scrum

      12 Agile Principles
1 Highest priority is to satisfy the
customer through early and continuous
delivery of valuable software/products
2 Welcome changing requirements
3 Deliver working software (product)
frequently
4 Business people and developers must
work together daily throughout the
project

                                         5
Overview of Agile and Scrum

   12 Agile Principles
5 Build projects around motivated
individuals
6 Most efficient and effective method of
conveying information is face-to-face
conversation
7 Working software (product) is the
primary measure of progress
8 Agile processes promote sustainable
development (maintain a constant pace
indefinitely)
                                        6
Overview of Agile and Scrum

          12 Agile Principles

9 Continuous attention to technical
excellence and good design enhances agility
10 Simplicity (art of maximizing amount
of work not done) is essential
11 Best architectures, requirements, and
designs emerge from self-organizing teams
12 At regular intervals, team reflects on how
to become more effective, then fine-tunes
and adjusts
http://agilemanifesto.org/principles.html

                                               7
Overview of Agile and Scrum

                               What is Scrum?

   Scrum is an Agile framework
     that supports lightweight
     processes that emphasize:
        Incremental deliveries
        Quality of Product
        Continuous improvement
        Discovery of people s potential
 Scrum is simple to understand,
   requires discipline in order to
   be successful
 Scrum is not a methodology
                                                                 8
Overview of Agile and Scrum


                        Foundations of Scrum
   Empiricism
        Detailed up-front planning and defined processes are replaced
          by just-in-time Inspect and Adapt cycles
   Self-Organization
        Small teams manage their own workload and organize
          themselves around clear goals and constraints
   Prioritization
        Do the next right thing
   Rhythm
        Allows teams to avoid daily noise and focus on delivery
   Collaboration
        Leaders and customers work with the Team, rather than
          directing them

                                                                          9
Overview of Agile and Scrum

                                   CoreValues
   Transparency
        Everything about a project is visible to everyone
   Commitment
        Making realistic commitments
   Courage
        Have the courage to commit, to act, to be open and to
          expect respect
   Focus
        Focus all of your efforts and skills on doing the work that you
          have committed to doing
   Respect
        Respect and trust the different people who comprise a team10
Scrum: Product Vision and
   Product Owner Role
Scrum: Vision and Product


                      ProductVision
 A   goal to aspire to
 Can be
  summarized in a
  short statement of
  intent
 Communicate     it to
  the team


                                                       12
Scrum: Vision and Product

                      Role: ProductOwner

 ThoughtLeader     and Visionary
 Drives   the Product Vision (e.g. story Mapping)
 Prioritizes   the Goals - User Stories
 Maintains   the Product Backlog with the team
 Acceptsthe Working Product (on behalf of the
  customer)



                                                        13
Scrum: Practices and
 ScrumMaster Role
Scrum: Sprint

                      Role: ScrumMaster

 Servant   Leader
 Facilitates   the Process
 Supports    the Team
 Removes     Organizational Impediments
 Socializes    Scrum to Management
 Enables    close collaboration across all roles and
  functions


                                                         15
Scrum: Sprint

                        Role: Team
 CrossFunctional

 5-9   Members
 SelfOrganizing

 Focused   on meeting Commitments




                                           16
Role: Relationships
        Product
        Owner



Team              Stakeholders




         Scrum
         Master


                     Diagram by Look Forward Consulting
Scrum Process Overview
Stakehol                         Daily Standup
ders                                 24 hrs


                                         Team
  Product             Retrospective
  Owner                                           Potentially
                                                  Shippable
                                                  Product
                         Sprint length
                          1-4 weeks       Stakeholders
    Sprint Planning
       Meeting        Sprint Backlog
                  Team
Scrum: Sprint

                Flow & Artifacts: Planning

 SprintPlanning    meeting held prior to beginning of
  each Sprint
 Duration   and time-effort are fixed in any given
  Sprint
      is to have prioritized Sprint Backlog, broken
 Goal
  down into tasks, that the Team can commit to
 During planning, Team commits to scope that can
  be completed in the Sprint, taking into account the
  Definition of Done
                                                       19
Scrum: Sprint

               Flow & Artifacts: DailyStandup

 Meetings     held in same location, same time, every
   day
 Timeboxed at 15minutes
 Encourages self-organization, rhythm, and
   collaboration
 Not a status meeting
 Each team member speaks to:
     What did I accomplish in the last 24 hours?
     What do I plan to accomplish in the next 24 hours?
     Any impediments getting in the way of my work?
                                                            20
Scrum: Sprint

              Flow & Artifacts: Taskboard

 Active
        visual indicator of
  flow of work

 Should
        be visible to
  team members at all
  times

 Should   be kept current

 Encouragesself-
  organization, and
  collaboration                               21
Scrum: Sprint

              Flow & Artifacts: SprintReview
 Occurs    at the end of each Sprint
 Inspect   and Adapt the product (Empiricism)
 Theteam meets with the Product Owner (and
  Stakeholders) to demonstrate the working
  software from the Sprint
 Thisis a hands-on software demo (not a
  PowerPoint) that usually requires some prep
  beforehand

                                                  22
Scrum: Sprint

                       Flow & Artifacts:
                        Retrospective
 Occurs    at the end of each Sprint
 Inspect   and Adapt the process (Empiricism)
 Teamand ScrumMaster meet to reflect on what
  went well and what can be improved
 Toneof the meeting is that everyone did their best
  and now look to how can we improve
 Retrospectives
             must conclude with team
  commitments to action

                                                    23
What is in it for me?
          {Customer}
 As a Customer, I want to be able to
    Have opportunity to provide feedback early
    Go to market faster with quality
    Faster return on investment




                                                   24
What is in it for me?
          {Leadership}
 As a Leader, I want
    To understand progress in terms of real progress
      made on the product
    Better engaged & accountable team




                                                    25
What is in it for me? {Team
           Member}

 Who    is a typical team member?
 As a team member, I want
     A sustainable pace
     Satisfaction of quality product delivered
     Clear Priority and less interruption during
       development




                                                     26
How do you learn Scrum? By
            Doing!

 Apply   a few practices at a time

 Understand    the values and foundations

 Inspect   and Adapt

 Experience   the Joy of Doing Scrum


                                              27
How do you learn Scrum?
Experiential Training.




                          28
User groups /Communities


 ALN   Agile Leadership Network
 Scrum Alliance  Scrum User Groups
 Online User Groups
    Scrum Alliance




                                        29
Scrum Certifications




                       30
Q&A




      31
 Scrum is a lightweight framework with a
 simple set of rules, built on foundations and
                     values

 Scrumenables teams to discover their true
  potential and deliver quality software that
             adds business value



                                                 32
Certified ScrumMaster Trainings in US



≒   Boston, MA- Jan 24-25, 2013  Certified ScrumMaster Training
≒   http://agile.conscires.com/certified-scrummaster-training-boston-10/

≒   Los Angeles, CA- Jan 26-27, 2013  Weekend Certified ScrumMaster Training
≒   http://agile.conscires.com/certified-scrummaster-training-losangeles-01/

≒   Dallas, TX- Jan 31-Feb 1, 2013  Certified ScrumMaster Training
≒   http://agile.conscires.com/certified-scrummaster-training-dallas-01/

≒   Denver, CO- Feb 4-5, 2013  Certified ScrumMaster Training
≒   http://agile.conscires.com/certified-scrummaster-training-denver-10/

≒   Irvine, CA- Feb 6-7, 2013  Certified ScrumMaster Training
≒   http://agile.conscires.com/certified-scrummaster-training-irvine-18/



                                                                                 33
Pay It Forward/Donation Only Trainings



≒   Irvine, CA- Jan 25, 2013  Agile & Scrum Training
≒   http://agile.conscires.com/agile-scrum-training-irvine-21/

≒   San Diego, CA- Jan 28, 2013  Agile & Scrum Training
≒   http://agile.conscires.com/agile-scrum-training-sandiego-08/

≒   Phoenix, AZ- Feb 1, 2013  Agile & Scrum Training
≒   http://agile.conscires.com/agile-scrum-training-phoenix-04/

≒   San Francisco, CA- Feb 4, 2013  Agile & Scrum Training
≒   http://agile.conscires.com/agile-training-scrum-training-san-francisco-07/

≒   Seattle, WA- Feb 8, 2013  Agile & Scrum Training
≒   http://agile.conscires.com/1-day-agile-scrum-training-in-seattle-10/

≒   Austin, TX- Feb 8, 2013  Agile & Scrum Training
≒   http://agile.conscires.com/1-day-agile-scrum-training-in-austin-03/

                                                                                  34
Thank you !
 More   Resources at
   http://agile.conscires.com/suggested-reading-list-
    and-resources/

  Contact Info
     agile@conscires.com
     +1-949-981-0998
     +1-949-232-8900


                                                    35

More Related Content

Introduction to Agile & Scrum

  • 1. Scrum: What s In It for Me? Prepared by Lisa Monta単o
  • 2. Agenda Overview of Agile and Scrum Scrum: Product Vision & Product Owner Role Scrum: Practices and ScrumMaster Role What s in it for me? 2
  • 3. Overview of Agile and Scrum
  • 4. Overview of Agile and Scrum Agile Manifesto Agile is a set of values: Individuals and interactions over processes and tools Workingsoftware (Products) over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan 4
  • 5. Overview of Agile and Scrum 12 Agile Principles 1 Highest priority is to satisfy the customer through early and continuous delivery of valuable software/products 2 Welcome changing requirements 3 Deliver working software (product) frequently 4 Business people and developers must work together daily throughout the project 5
  • 6. Overview of Agile and Scrum 12 Agile Principles 5 Build projects around motivated individuals 6 Most efficient and effective method of conveying information is face-to-face conversation 7 Working software (product) is the primary measure of progress 8 Agile processes promote sustainable development (maintain a constant pace indefinitely) 6
  • 7. Overview of Agile and Scrum 12 Agile Principles 9 Continuous attention to technical excellence and good design enhances agility 10 Simplicity (art of maximizing amount of work not done) is essential 11 Best architectures, requirements, and designs emerge from self-organizing teams 12 At regular intervals, team reflects on how to become more effective, then fine-tunes and adjusts http://agilemanifesto.org/principles.html 7
  • 8. Overview of Agile and Scrum What is Scrum? Scrum is an Agile framework that supports lightweight processes that emphasize: Incremental deliveries Quality of Product Continuous improvement Discovery of people s potential Scrum is simple to understand, requires discipline in order to be successful Scrum is not a methodology 8
  • 9. Overview of Agile and Scrum Foundations of Scrum Empiricism Detailed up-front planning and defined processes are replaced by just-in-time Inspect and Adapt cycles Self-Organization Small teams manage their own workload and organize themselves around clear goals and constraints Prioritization Do the next right thing Rhythm Allows teams to avoid daily noise and focus on delivery Collaboration Leaders and customers work with the Team, rather than directing them 9
  • 10. Overview of Agile and Scrum CoreValues Transparency Everything about a project is visible to everyone Commitment Making realistic commitments Courage Have the courage to commit, to act, to be open and to expect respect Focus Focus all of your efforts and skills on doing the work that you have committed to doing Respect Respect and trust the different people who comprise a team10
  • 11. Scrum: Product Vision and Product Owner Role
  • 12. Scrum: Vision and Product ProductVision A goal to aspire to Can be summarized in a short statement of intent Communicate it to the team 12
  • 13. Scrum: Vision and Product Role: ProductOwner ThoughtLeader and Visionary Drives the Product Vision (e.g. story Mapping) Prioritizes the Goals - User Stories Maintains the Product Backlog with the team Acceptsthe Working Product (on behalf of the customer) 13
  • 14. Scrum: Practices and ScrumMaster Role
  • 15. Scrum: Sprint Role: ScrumMaster Servant Leader Facilitates the Process Supports the Team Removes Organizational Impediments Socializes Scrum to Management Enables close collaboration across all roles and functions 15
  • 16. Scrum: Sprint Role: Team CrossFunctional 5-9 Members SelfOrganizing Focused on meeting Commitments 16
  • 17. Role: Relationships Product Owner Team Stakeholders Scrum Master Diagram by Look Forward Consulting
  • 18. Scrum Process Overview Stakehol Daily Standup ders 24 hrs Team Product Retrospective Owner Potentially Shippable Product Sprint length 1-4 weeks Stakeholders Sprint Planning Meeting Sprint Backlog Team
  • 19. Scrum: Sprint Flow & Artifacts: Planning SprintPlanning meeting held prior to beginning of each Sprint Duration and time-effort are fixed in any given Sprint is to have prioritized Sprint Backlog, broken Goal down into tasks, that the Team can commit to During planning, Team commits to scope that can be completed in the Sprint, taking into account the Definition of Done 19
  • 20. Scrum: Sprint Flow & Artifacts: DailyStandup Meetings held in same location, same time, every day Timeboxed at 15minutes Encourages self-organization, rhythm, and collaboration Not a status meeting Each team member speaks to: What did I accomplish in the last 24 hours? What do I plan to accomplish in the next 24 hours? Any impediments getting in the way of my work? 20
  • 21. Scrum: Sprint Flow & Artifacts: Taskboard Active visual indicator of flow of work Should be visible to team members at all times Should be kept current Encouragesself- organization, and collaboration 21
  • 22. Scrum: Sprint Flow & Artifacts: SprintReview Occurs at the end of each Sprint Inspect and Adapt the product (Empiricism) Theteam meets with the Product Owner (and Stakeholders) to demonstrate the working software from the Sprint Thisis a hands-on software demo (not a PowerPoint) that usually requires some prep beforehand 22
  • 23. Scrum: Sprint Flow & Artifacts: Retrospective Occurs at the end of each Sprint Inspect and Adapt the process (Empiricism) Teamand ScrumMaster meet to reflect on what went well and what can be improved Toneof the meeting is that everyone did their best and now look to how can we improve Retrospectives must conclude with team commitments to action 23
  • 24. What is in it for me? {Customer} As a Customer, I want to be able to Have opportunity to provide feedback early Go to market faster with quality Faster return on investment 24
  • 25. What is in it for me? {Leadership} As a Leader, I want To understand progress in terms of real progress made on the product Better engaged & accountable team 25
  • 26. What is in it for me? {Team Member} Who is a typical team member? As a team member, I want A sustainable pace Satisfaction of quality product delivered Clear Priority and less interruption during development 26
  • 27. How do you learn Scrum? By Doing! Apply a few practices at a time Understand the values and foundations Inspect and Adapt Experience the Joy of Doing Scrum 27
  • 28. How do you learn Scrum? Experiential Training. 28
  • 29. User groups /Communities ALN Agile Leadership Network Scrum Alliance Scrum User Groups Online User Groups Scrum Alliance 29
  • 31. Q&A 31
  • 32. Scrum is a lightweight framework with a simple set of rules, built on foundations and values Scrumenables teams to discover their true potential and deliver quality software that adds business value 32
  • 33. Certified ScrumMaster Trainings in US ≒ Boston, MA- Jan 24-25, 2013 Certified ScrumMaster Training ≒ http://agile.conscires.com/certified-scrummaster-training-boston-10/ ≒ Los Angeles, CA- Jan 26-27, 2013 Weekend Certified ScrumMaster Training ≒ http://agile.conscires.com/certified-scrummaster-training-losangeles-01/ ≒ Dallas, TX- Jan 31-Feb 1, 2013 Certified ScrumMaster Training ≒ http://agile.conscires.com/certified-scrummaster-training-dallas-01/ ≒ Denver, CO- Feb 4-5, 2013 Certified ScrumMaster Training ≒ http://agile.conscires.com/certified-scrummaster-training-denver-10/ ≒ Irvine, CA- Feb 6-7, 2013 Certified ScrumMaster Training ≒ http://agile.conscires.com/certified-scrummaster-training-irvine-18/ 33
  • 34. Pay It Forward/Donation Only Trainings ≒ Irvine, CA- Jan 25, 2013 Agile & Scrum Training ≒ http://agile.conscires.com/agile-scrum-training-irvine-21/ ≒ San Diego, CA- Jan 28, 2013 Agile & Scrum Training ≒ http://agile.conscires.com/agile-scrum-training-sandiego-08/ ≒ Phoenix, AZ- Feb 1, 2013 Agile & Scrum Training ≒ http://agile.conscires.com/agile-scrum-training-phoenix-04/ ≒ San Francisco, CA- Feb 4, 2013 Agile & Scrum Training ≒ http://agile.conscires.com/agile-training-scrum-training-san-francisco-07/ ≒ Seattle, WA- Feb 8, 2013 Agile & Scrum Training ≒ http://agile.conscires.com/1-day-agile-scrum-training-in-seattle-10/ ≒ Austin, TX- Feb 8, 2013 Agile & Scrum Training ≒ http://agile.conscires.com/1-day-agile-scrum-training-in-austin-03/ 34
  • 35. Thank you ! More Resources at http://agile.conscires.com/suggested-reading-list- and-resources/ Contact Info agile@conscires.com +1-949-981-0998 +1-949-232-8900 35