SlideServe
Menu
Préférences
© SlideServe · v2026

FR AGILE

lynde avatar
23 diapositives · 565 Views · Sep 05, 2014

Breaking Agile. http://www.npowersoftware.com/gallery/4GlassShaterLarge.jpg. FR AGILE. Handle with care. Dan Clausing CBAP, CSM Nationwide. There are no shortcuts. Co-location Communication Immediate Response. Agile Values. Breaking Agile. Easier to break than create/maintain

FR AGILE - slide 1
01 / 23FR AGILE
1 / 17

Télécharger la présentation

FR AGILE
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation
  1. Breaking Agile http://www.npowersoftware.com/gallery/4GlassShaterLarge.jpg FRAGILE Handle with care Dan Clausing CBAP, CSM Nationwide

  2. There are no shortcuts • Co-location • Communication • Immediate Response

  3. Agile Values

  4. Breaking Agile • Easier to break than create/maintain • Not just in the team, whole organization • Time independent • Agile is not formulaic; it is necessarily organic, ever changing within the environment in which it occurs Dan Clausing 2010

  5. Breaking Points • Senior Management • Stakeholders • Project Management • Development Team

  6. Senior Management • ROI • Values • Certification • Metrics

  7. Senior Management - ROI Agile Methods require non-traditional measures. Traditional Methods were optimized for productivity and quality, which rewards them using total lifecycle cost analysis; but Agile methods should focus on project success and customer satisfaction where they shine best. http://davidfrico.com/rico08b.pdf

  8. Senior Management - ROI Jeff Sutherland Says… (Co-founder of SCRUM) http://agile.scumniotales.com/agile-roi/

  9. Senior Management – Values/Certification

  10. Senior Management – Metrics The Hawthorne Effect • Change of behaviors as a result of being measured • Impact of other things on what is being measured SystemsThinking

  11. Stakeholders – Beliefs Perception versus Reality • Everything is Quicker • Expectations in conflict with needs • Changing Views • Availability (Conduit) Eugene Oberst 1901 - 1991

  12. Project Management - Metrics Limit Control

  13. Project Management - Behaviors Support the Team • Be in the team room • Know the process • Communicate Risks and Issues • Don’t push scope • Agile is not an excuse • ASK WHY!

  14. Development Team Build the Team • The Best of the Best • Environment • Team Mindset • Motivation • Communication • Documentation • Testing

  15. Development Team – The Players Best of the Best • All roles must be filled • The best doesn’t mean the best • People skills are essential • Mindset • Audition

  16. Development Team – Environment Environment Matters • One centralized room • One roof • No cube walls • Headphones • Perimeter walls • Pairing

  17. Development Team – Mindset The Right Mind • In it together • The story… • Motivation

  18. Development Team – Communication How Do We Interact • Non-Emotional • Emotional • Using the wrong collaboration media to communicate messages “In fact, the effort to fastidiously eliminate all emotion from the workplace is a very strong sign that the team is a machine. Machine parts don't have to have emotions and machine parts don't have to deal with emotions.” Daryl Kulak. "Agile in the Bloodstream”. Yet to be published

  19. Development Team – Communication Type of Communication

  20. Development Team Team Dynamics

  21. Development Team Documentation • Longevity • Will it be used? • What is needed? • How can it be conveyed?

  22. Development Team Testing …Defects can be Good!

  23. Final Thoughts… You Might Break Agile if You… • think Agile is an excuse • don’t have management commitment • need reams of documentation • can’t play well in the sandbox • don’t have time • have an irrational fear of thumbtacks • can’t see your teammates daily • rely on metrics for all decisions