Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Scrum and Agile Values

This is a deck I use to conduct workshops on the Scrum and Agile Values that help make Scrum implementations successful

Livres associés

Gratuit avec un essai de 30 jours de Scribd

Tout voir
  • Identifiez-vous pour voir les commentaires

Scrum and Agile Values

  1. 1. Agile and Scrum Values Presented by Kamal Tejnani, Agile Coach, Agile CoE 08/24/2015
  2. 2. 2 Scrum Values
  3. 3. 3 Focus
  4. 4. 4 Openness
  5. 5. 5 Respect Scrum Master as Servant Leader
  6. 6. 6 Courage
  7. 7. 7 Commitment
  8. 8. 8 Agile Manifesto
  9. 9. 9 Principles on which the Agile Manifesto is based
  10. 10. • What does this mean ? • Processes and Tools – Bureaucracy (red tapism ?) – Approvals, hand-offs, sign-offs – Formal notes – Email trails – Not in my jurisdiction (Indian Police always does that) and refer to policies • As software developers, we are actually passionate about tools. And we love our processes as well. Both processes and tools help us get things done • How many processes can you put in place, given the kind of projects that are implemented in Agile • But will this work in a Distributed Model between Onsite and Offshore • Will it work for us ? 10 Individuals and Interactions over Processes and Tools Stacey Matrix
  11. 11. 11 Working software over comprehensive Documentation
  12. 12. • Agile processes harness change for the customer's competitive advantage • What does this mean ? • Arbitrary changes within the Sprint ? • Changes during  Grooming  Before Estimation  After Estimation  Before Planning  After Planning  Before Sprint has started  After Sprint has started 12 Welcome changing Requirements even late in Development
  13. 13. 13 Business people and developers must work together daily throughout the project • Why ? • During Release Planning • During Grooming • Even during Estimation to get clarifications if needed • During the Sprint • Demos • Risks highlighted during Standups
  14. 14. Give them the environment and support they need and trust them to get the job done • Stacey Matrix again – the kind of projects that are implemented in Agile • Empowered teams deliver better • Self-organized teams support one another • Teams trust one another 14 Build projects around motivated individuals
  15. 15. • Less Technical Debt • Easier to make changes • Your code changes will not have negative impacts • You will be able to deliver faster, with good quality thus making you Agile 15 Continuous attention to technical excellence and good design enhances agility
  16. 16. Anything I missed out ?