Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.
Introduction to Scrum
Brief Overview of Scrum Framework
Avidan Hetzroni
Enterprise Agile Coach, Trainer &
Blogger
Certified Scrum Professional
Certified SAFe® Program Consultant
...
What is Scrum?
Scrum is a
framework (not a
process) for
developing and
sustaining complex
products
A scrum (short for scru...
Scrum Theory
Scrum is based on
empirical process control
theory, where:
knowledge comes from
experience, and
decisions a...
Scrum Values
Scrum Team members have courage to
do the right thing and work on tough
problems
COURAGE
Scrum Values
Everyone focuses on the work of the
Sprint and the goals of the Scrum Team
Focus
Scrum Values
People personally commit to achieving
the goals of the Scrum Team
COMMITMENT
Scrum Values
Scrum Team members respect each
other to be capable, independent
people
RESPECT
Scrum Values
The Scrum Team and its stakeholders
agree to be open about all the work
and the challenges with performing
th...
The Scrum Framework
Scrum bind together the events, roles, and artifacts, governing the
relationships and interaction betw...
Scrum Roles
The Scrum Master
Responsible for ensuring Scrum is
understood and enacted
Scrum Master
The Product Owner
Responsible for maximizing the value of
the product and the work of the
Development Team
Product Owner
The Development Team
Responsible for delivering a potentially
Product Increment at the end of each
Sprint
Dev Team (4 to 9...
The Scrum Team
Self-organizing, choose how
best to accomplish their
work
Cross-functional, have all
abilities needed to
ac...
Scrum Events
Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint
Retrospective
Scrum Events
 Occurred on regular cadence. (same time and place)
 Minimize the need for meetings not defined in Scrum.
...
The Sprint
 One month or less.
 Produce potentially product
Increment.
 A new Sprint starts immediately after
the concl...
During the Sprint…
 No changes are made that would
endanger the Sprint Goal.
 Quality goals do not decrease.
 Scope may...
Cancelling a Sprint
Product Owner has the
authority to cancel the Sprint
 if the Sprint Goal becomes obsolete
 if it no ...
Sprint Planning
The entire team collaborate to agree the work to be performed in the
Sprint
Time Box
8
hrs
Inputs
• Produc...
Daily Scrum
The Dev. Team synchronize activities and create a plan for the next day
Time Box
15
min.
Inputs
• Team members...
Sprint Review
The Scrum Team and stakeholders inspect the Increment and adapt the
Product Backlog if needed
Time Box
4
hrs...
Sprint Retrospective
The Scrum Team inspect itself and create a plan for improvements
Time Box
3
hrs
Inputs
• Potential Pr...
Scrum Artifacts
Product Backlog, Sprint Backlog, Product Increment
Scrum Artifacts
 Are evidences of work or value
 Provide transparency and opportunity for inspection and
adoption
Produc...
Product Backlog
 Product Backlog is an ordered list of
everything that might be needed in the
product
 The single source...
Product Backlog Readiness = INVEST
Sprint Backlog
 Sprint Backlog is the work (tasks)
needed to deliver the functionality of
Product Backlog into a “Done”
I...
Potential Product Increment
 Increment is the sum of all the Product
Backlog items completed during a
Sprint
 MUST be DO...
Definition of Done (DoD)
 Shared understanding of what done/complete means to
ensure transparency
 Used to assess when w...
Definition of Done (DoD)
Code completed and checked-in
All unit testing pass
All acceptance testing pass
New injected bugs...
THAT’S ALL
Próximo SlideShare
Cargando en…5
×

de

Introduction to Scrum Slide 1 Introduction to Scrum Slide 2 Introduction to Scrum Slide 3 Introduction to Scrum Slide 4 Introduction to Scrum Slide 5 Introduction to Scrum Slide 6 Introduction to Scrum Slide 7 Introduction to Scrum Slide 8 Introduction to Scrum Slide 9 Introduction to Scrum Slide 10 Introduction to Scrum Slide 11 Introduction to Scrum Slide 12 Introduction to Scrum Slide 13 Introduction to Scrum Slide 14 Introduction to Scrum Slide 15 Introduction to Scrum Slide 16 Introduction to Scrum Slide 17 Introduction to Scrum Slide 18 Introduction to Scrum Slide 19 Introduction to Scrum Slide 20 Introduction to Scrum Slide 21 Introduction to Scrum Slide 22 Introduction to Scrum Slide 23 Introduction to Scrum Slide 24 Introduction to Scrum Slide 25 Introduction to Scrum Slide 26 Introduction to Scrum Slide 27 Introduction to Scrum Slide 28 Introduction to Scrum Slide 29 Introduction to Scrum Slide 30 Introduction to Scrum Slide 31 Introduction to Scrum Slide 32 Introduction to Scrum Slide 33
Próximo SlideShare
What to Upload to SlideShare
Siguiente
Descargar para leer sin conexión y ver en pantalla completa.

2 recomendaciones

Compartir

Descargar para leer sin conexión

Introduction to Scrum

Descargar para leer sin conexión

In this slides deck, Avidan Hetzroni explains the basic concepts behind the Scrum Framework values and principles and how Scrum bind together the events, roles, and artifacts to govern the relationships and interaction between them.

Audiolibros relacionados

Gratis con una prueba de 30 días de Scribd

Ver todo

Introduction to Scrum

  1. 1. Introduction to Scrum Brief Overview of Scrum Framework
  2. 2. Avidan Hetzroni Enterprise Agile Coach, Trainer & Blogger Certified Scrum Professional Certified SAFe® Program Consultant Six Sigma Green-Belt B.Sc. System Engineering, BGU www.avidanhetzroni.com
  3. 3. What is Scrum? Scrum is a framework (not a process) for developing and sustaining complex products A scrum (short for scrummage) is a method of restarting play in rugby football.
  4. 4. Scrum Theory Scrum is based on empirical process control theory, where: knowledge comes from experience, and decisions are made based on what is known
  5. 5. Scrum Values Scrum Team members have courage to do the right thing and work on tough problems COURAGE
  6. 6. Scrum Values Everyone focuses on the work of the Sprint and the goals of the Scrum Team Focus
  7. 7. Scrum Values People personally commit to achieving the goals of the Scrum Team COMMITMENT
  8. 8. Scrum Values Scrum Team members respect each other to be capable, independent people RESPECT
  9. 9. Scrum Values The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work OPENNESS
  10. 10. The Scrum Framework Scrum bind together the events, roles, and artifacts, governing the relationships and interaction between them
  11. 11. Scrum Roles
  12. 12. The Scrum Master Responsible for ensuring Scrum is understood and enacted Scrum Master
  13. 13. The Product Owner Responsible for maximizing the value of the product and the work of the Development Team Product Owner
  14. 14. The Development Team Responsible for delivering a potentially Product Increment at the end of each Sprint Dev Team (4 to 9 people)
  15. 15. The Scrum Team Self-organizing, choose how best to accomplish their work Cross-functional, have all abilities needed to accomplish the work without depending on others Flexibility, Creativity, and Productivity
  16. 16. Scrum Events Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective
  17. 17. Scrum Events  Occurred on regular cadence. (same time and place)  Minimize the need for meetings not defined in Scrum.  Are time-boxed, has a maximum duration:  Sprint duration is fixed and cannot be shortened or lengthened.  Other events may end whenever the purpose of the event is achieved, but without allowing waste in the process
  18. 18. The Sprint  One month or less.  Produce potentially product Increment.  A new Sprint starts immediately after the conclusion of the previous Sprint.
  19. 19. During the Sprint…  No changes are made that would endanger the Sprint Goal.  Quality goals do not decrease.  Scope may be clarified and re- negotiated between the Product Owner and Development Team as more is learned.
  20. 20. Cancelling a Sprint Product Owner has the authority to cancel the Sprint  if the Sprint Goal becomes obsolete  if it no longer makes sense given the circumstances
  21. 21. Sprint Planning The entire team collaborate to agree the work to be performed in the Sprint Time Box 8 hrs Inputs • Product backlog items • Latest Product Increment • Team capacity & Past performance Steps • What can be done this Sprint? • How will the chosen work get done? Outputs • Sprint Goal (s) • Sprint Backlogs (tasks)
  22. 22. Daily Scrum The Dev. Team synchronize activities and create a plan for the next day Time Box 15 min. Inputs • Team members progress Steps • What did I do yesterday? • What will I do today? • Do I see any impediment? Outputs • After the Daily Scrum, adapt or re-plan, the rest of the Sprint’s work
  23. 23. Sprint Review The Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed Time Box 4 hrs Inputs • Potential Product Increment Steps • What was done? • What was changed? • Demonstrate Product Increment Outputs • A revised Product Backlog that defines the most likely items for the next Sprint.
  24. 24. Sprint Retrospective The Scrum Team inspect itself and create a plan for improvements Time Box 3 hrs Inputs • Potential Product Increment Steps • How things goes with regards to people, relationships, process, and tools? • What went well and potential improvements? Outputs • A plan for implementing improvements to the way the Scrum Team does its work, normally in the next sprint
  25. 25. Scrum Artifacts Product Backlog, Sprint Backlog, Product Increment
  26. 26. Scrum Artifacts  Are evidences of work or value  Provide transparency and opportunity for inspection and adoption Product Backlogs Sprint Backlogs Potential Product Increment
  27. 27. Product Backlog  Product Backlog is an ordered list of everything that might be needed in the product  The single source of requirements for any changes to be made to the product  Have to be READY before Sprint Planning  Used to monitor progress toward goal or project milestone
  28. 28. Product Backlog Readiness = INVEST
  29. 29. Sprint Backlog  Sprint Backlog is the work (tasks) needed to deliver the functionality of Product Backlog into a “Done” Increment  New sprint backlogs can emerges during the Sprint progress  Used to monitor Sprint progress
  30. 30. Potential Product Increment  Increment is the sum of all the Product Backlog items completed during a Sprint  MUST be DONE !
  31. 31. Definition of Done (DoD)  Shared understanding of what done/complete means to ensure transparency  Used to assess when work is complete on the product Increment  Help Development Team in knowing how many Product Backlog items it can select during a Sprint Planning  It is expected that DoD will expand to include more stringent criteria for higher quality
  32. 32. Definition of Done (DoD) Code completed and checked-in All unit testing pass All acceptance testing pass New injected bugs fixed Code Coverage +80% Regression testing pass Deployed Accepted by PO
  33. 33. THAT’S ALL
  • kishordeo

    Dec. 15, 2020
  • Roisantu

    Sep. 12, 2017

In this slides deck, Avidan Hetzroni explains the basic concepts behind the Scrum Framework values and principles and how Scrum bind together the events, roles, and artifacts to govern the relationships and interaction between them.

Vistas

Total de vistas

217

En Slideshare

0

De embebidos

0

Número de embebidos

0

Acciones

Descargas

10

Compartidos

0

Comentarios

0

Me gusta

2

×