Presentation
Transcription
Presentation
4/20/15 Core Agility Workout AgileIndy 2015 Ma1 Block Ma1 Block – CSP, CSM, CSPO • Agile Coach/Consultant @ Fusion Alliance • Founder of AgileIndy and the AgileIndy Conference • Leading agile teams since 2008 • Passionate about creaEng great places to work • Happy, moEvated employees create delighted customers which results in profits. “Profit is the applause you get for taking care of your customers and crea8ng a mo8va8ng environment for your people.” – The One Minute Entrepreneur 2 1 4/20/15 WARM U P The Agile Manifesto Individuals and InteracEons over Processes and Tools Working SoOware over Comprehensive DocumentaEon Customer CollaboraEon over Contract NegoEaEon Responding to Change over Following a Plan 4 2 4/20/15 Scrum 5 12 Agile Principles • SaEsfy the customer through early and conEnuous delivery • Working soOware is the primary measure of progress • Welcome changing requirements, even late in development • Sustainable pace • ConEnuous a1enEon to technical excellence • Deliver Frequently • Maximize the amount of work • Business people and developers NOT done work together daily • Emergent design from self-‐ • Build projects around moEvated organizing teams individuals • Regularly inspect and adapt • Face-‐to-‐Face communicaEon 6 3 4/20/15 Scrum Details Scrum Roles • Product Owner • ScrumMaster • Team Member • • • • Scrum Events Sprint Planning Daily Stand-‐up Sprint Review Sprint RetrospecEve • • • • Scrum Events Sprint Planning Daily Stand-‐up Sprint Review Sprint RetrospecEve 7 Lean Principles • Eliminate Waste • Amplify Learning • Just-‐in-‐Eme Decisions • Rapid, Small Deliveries • Empowered Teams • Build with Integrity • Focus on Big Picture 8 4 4/20/15 EXERCISE # 1 MULTI TASKING Rules • Worker o Group A – MulE-‐task o Group B – Complete projects one at a Eme • Manager o Time your worker o How long does it take to deliver the first project o How long does it take to deliver all three projects • Projects o Project 1 – Numbers 0-‐9 o Project 2 – Le1ers A – J o Project 3 – Roman Numerals I -‐ X 10 5 4/20/15 Results Group A First Project Group B First Project Group A All Projects Group B All Projects 1 2 3 4 5 11 What did we learn? • Humans are poor mulE-‐taskers • Focusing on one project at a Eme allows it to get done quickly and with higher quality • Since you don’t have the cost of context switching, you actually finish all the projects faster doing them one at a Eme 12 6 4/20/15 How does this apply to agile? • Agile encourages dedicated teams, not individuals allocated across mulEple projects. o Build projects around moEvated individuals. • Task switching is one of the 7 wastes called out by Lean • This supports small, quick, deliverables o Focus on this one problem and get it done, then move on to the next. 13 EXERCISE # 2 THE P ENNY G AME 7 4/20/15 Rules • Magic Penny Company o A penny gets its magic by being flipped one Eme by 4 different people • Workers (4 Workers for each company) o Only use one hand, only flip one penny at a Eme • Managers (4 Managers, one for each worker) o Time how long your worker is “acEve” (start when touches first penny, stop when passes off the last penny) • CEO (1 CEO) o How long does it take unEl you get your first penny? o How long does it take unEl you have all of the pennies? 15 Results Team 1 20 Team 1 5 Team 1 1 Team 2 20 Team 2 5 Team 2 1 Team 3 20 Team 3 5 Team 3 1 A B C D 1st Total 16 8 4/20/15 What did we learn? • Cycle Eme decreases as batch size decreases o Smaller pieces of work can get through the system faster o Overall cycle Eme of all the pieces also decreases • As total Eme decreases, worker Eme increases! o I could get this done a lot quicker if I could work on all these stories at the same Eme. • Idle Eme is higher with higher batch size • Cost of change higher with higher batch size 17 How does this apply to agile? • Heavily related to the lean principle Eliminate Waste o ParEally done work o Extra features • Small User Stories, Quick deliverables o “If I could work on all of those stories at the same Eme I’d get them done quicker” • Speaks to the pinalls of local opEmzaEon 18 9 4/20/15 EXERCISE # 3 THE H UMAN K NOT Rules • The Team – 7 team members • Group A – Manager led o o Team Ees the knot, Manager unEes it Team members are not allowed to talk or help the manager in any way, just do as the manager asks you • Group B – Self-‐Organizing o Team Ees the know, team unEes the knot 20 10 4/20/15 Results Team Time 21 What did we learn? • Self-‐organizing groups out-‐perform manager led groups • Those closest to the work should decide how to do the work • How did the groups self-‐organize o Did any leaders emerge? o What would you do different next Eme? 22 11 4/20/15 How does this relate to agile? • Scrum – self organizing teams • Agile Principles o Build projects around moEvated individuals. Give them the environment and support they need, and trust them to get the job done. 23 COOL D OWN 12 4/20/15 Lots of Games Available • The Marshmallow Challenge • Paper folding exercise • Ball point game • h1p://tastycupcakes.org/ • h1p://www.innovaEongames.com/resources/the-‐games/ 25 Why use games • Help us visualize and internalize otherwise theoreEcal concepts • Play is an essenEal part of human life o Builds team cohesiveness o Builds trust • Gives us a different perspecEve from which to consider problems 26 13 4/20/15 Ma1 Block – CSP, CSM, CSPO • Email: [email protected] • Twi1er: @devblock • LinkedIn: h1ps://www.linkedin.com/in/devblock • Fusion Blog: h1ps://www.fusionalliance.com/blog/ • Personal Block: h1p://www.developmentblock.com/ 27 APPENDIX 14 4/20/15 Words can be tricky • I didn’t say she stole my money. • I didn’t say she stole my money. • I didn’t say she stole my money. • I didn’t say she stole my money. • I didn’t say she stole my money. • I didn’t say she stole my money. • I didn’t say she stole my money. • I didn’t say she stole my money. 29 15