whole agile
DESCRIPTION
Choosing a methodology or a set of software development practices is just the beginning. In order to truly find success using agile methods you need to embrace Whole Agile.TRANSCRIPT
![Page 1: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/1.jpg)
Whole Agile
Version 1.0
Copyright © 2012 Peter Scheyen
![Page 2: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/2.jpg)
PERSONAL BACKGROUND
Peter Scheyen ([email protected], @pscheyen)CTO, Richard Ivey School of BusinessFormerly with Comcast, TVWorks, Liberate, CableshareExperience includes Software Developer, Management, VP EngTraditional software development methodologiesIntroduced Agile methods in different contexts
Small team of 10 membersLarge organization of 10 teams of 5-10 members each
![Page 3: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/3.jpg)
Whole Agile
Version 1.0
![Page 4: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/4.jpg)
COMMON PERCEPTIONS OFAGILE METHODS
![Page 5: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/5.jpg)
Quick Fix
Quick Fix?
![Page 6: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/6.jpg)
Repackaged Waterfall
Repackaged Method X?
![Page 7: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/7.jpg)
No More Project Managers
No PMs? No QA?
![Page 8: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/8.jpg)
Change Orders for Free
Free Changes?
![Page 9: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/9.jpg)
Cowboy CodingCowboy Coding?
![Page 10: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/10.jpg)
For Elite Programmers Only
Requires Elite Programmers?
![Page 11: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/11.jpg)
For Web Development Only
Web Programming Only?
![Page 12: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/12.jpg)
For Small Teams Only
Small Teams Only?
![Page 13: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/13.jpg)
It’s Hard!
It’s Hard
![Page 14: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/14.jpg)
WHY BOTHER?
![Page 15: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/15.jpg)
Deliver working software faster
and more frequently
![Page 16: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/16.jpg)
Fewer quality issues
![Page 17: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/17.jpg)
Self-managing, adaptive, learning teams
![Page 18: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/18.jpg)
Less reliance on individual heroes
Greater reliance on high performing teams
![Page 19: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/19.jpg)
More effective use of resources
![Page 20: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/20.jpg)
Can create space for organic innovation
![Page 21: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/21.jpg)
Higher visibility into the true state of projects
![Page 22: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/22.jpg)
No place to hide
![Page 23: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/23.jpg)
WHAT IS AGILE ANYWAY?
![Page 24: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/24.jpg)
A BRIEF HISTORY
Iterative methods date back to the 1950sObject oriented programming from the 1960sAdaptive methodologies from the early 1970sLightweight methods developed in the 1990sAgile Manifesto signed in early 2001Scrum, XP, Crystal, Adaptive Software Development, FDD
![Page 25: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/25.jpg)
AGILE MANIFESTO
We value:Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
http://agilemanifesto.org
![Page 26: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/26.jpg)
IN A NUTSHELL
Working software product as the primary deliverableIterative and incremental product developmentClose collaboration between customer/business and technical roles
Dave Rooney, “An Organizational Structure for Agile Projects”
![Page 27: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/27.jpg)
Sounds simple enough
![Page 28: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/28.jpg)
WHAT IS “WHOLE AGILE”?
Successful agile is more than...working software delivered iteratively in collaboration with customersa set of processesa set of software development practices
Whole Agile looks at the organization as a system taking into account not only Process but also People, Culture, Communication, Physical Environment, Requirements, Organizational Roles
![Page 29: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/29.jpg)
ESSENTIAL ASPECTS OF
WHOLE AGILE
![Page 30: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/30.jpg)
ESSENTIAL ASPECTS OF WHOLE AGILE
Basic Agile PracticesSoftware Development PracticesCulturePeopleOrganization and RolesCommunicationFeedback and Adaptation
![Page 31: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/31.jpg)
ASPECT: BASIC AGILE PRACTICES
Backlog of remaining workIteration planningShort, frequent meetings (daily standups)Available customer or customer representative (Product Owner)Burn down charts or similar progress trackingDeliverable software at the end of each iterationRetrospective
![Page 32: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/32.jpg)
ASPECT: SOFTWARE DEVELOPMENT PRACTICES
Out of scope for this discussionImportant to trust the technical team to decide
![Page 33: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/33.jpg)
Requirements sidebar
![Page 34: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/34.jpg)
ASPECT: CULTUREAgile Cultural Norms
Whole TeamCustomer Value-OrientedHonestyTransparencyTrustCommitmentExcellenceSustainable PaceHunger for feedbackContinuous LearningAdaptableAccountable
![Page 35: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/35.jpg)
ASPECT: PEOPLE
Alistair Cockburn: “non-linear, first-order components of software development”People are:
sensitive to communication timing and modalityinconsistent over timevariable day to day and place to placegood citizens that want to do a good job
![Page 36: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/36.jpg)
ASPECT: PEOPLE
Leadership - it takes courageFrequency and impact of decisions increasedEmpowerment and trustHolding people accountable
![Page 37: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/37.jpg)
No place to hide
![Page 38: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/38.jpg)
ASPECT: ORGANIZATION
Key Roles (Dave Rooney, “An Org. Structure for Agile Projects”)Customer or Customer ProxyCoachSubject Matter ExpertGeneralizing SpecialistQAComptroller
Organizational Structure pseudo-matrixedDual Career Paths
![Page 39: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/39.jpg)
ASPECT: COMMUNICATION
High bandwidthOpen and honestDirectly with customerTransparent at all levelsReal-time as possibleMeetings
![Page 40: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/40.jpg)
ASPECT: FEEDBACK AND ADAPTATION
Culture demands constant feedback and adaptationRelentless identification and elimination of wasteSelf-assessment through retrospectivesGuided by metrics (generated automatically)Peer feedbackExperimentation and feedback (failure is an option)Feedback isn’t enough alone -- adaptation
![Page 41: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/41.jpg)
OTHER WHOLE AGILE ASPECTS
Physical EnvironmentToolsPortfolio managementSimplicityJust enough, just in time, just do it
![Page 42: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/42.jpg)
LEAN THINKINGLean Software Development -- Mary and Tom PoppendieckBorrows heavily from Toyota Production System7 Principles
Optimize the wholeEliminate wasteBuild in qualityLearn constantlyDeliver as fast as possibleEngage everyoneKeep getting better
![Page 43: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/43.jpg)
IN SUMMARY (10 min)
Software companies want to deliver more, fasterNon-software companies want to better leverage IT resourcesWhole Agile means:
Iteratively deliver working software in collaboration with the customerPLUSWhole TeamDeep commitment to delivering customer valueHealthy cultureOpen and honest communication and transparencyFeedback and adaptationRelentless elimination of waste
![Page 44: Whole Agile](https://reader034.vdocuments.site/reader034/viewer/2022051513/5454e14daf7959795d8b45a2/html5/thumbnails/44.jpg)
READING LIST
http://scheyeniam.blogspot.com/2012/01/agile-reading-list.html