A presentation at Devoxx Belgium in in Antwerp, Belgium by KLAUK FANNY
PREFACE Written in 2019, still relevant in 2023… Teams autonomy & self-organisation Cry of alarm / warning Only 6 sketches today…but 2048 possibles
CHARACTERS Lily, hero React developer 2 years’ experience You & I, readers Manager Project manager Agile coach Developer Client Ops … 1
THE STORY Lily has just started a new job at Sogreat. Her objective: to join a team which produce an ecommerce site for VerySweet, a company specialising in the sale of masks. We are the Manager, we choose to: Start Lily immediately: time is money! Go to page 3 Take the time to introduce Lily to your team, your environment… Go to page 5 2
THE START OF WORK Lily goes to work: 3
THE START OF WORK Lily goes to work: 3
THE START OF WORK Lily goes to work: 3
THE START OF WORK Lily goes to work: 3
THE START OF WORK Lily goes to work: 3
THE START OF WORK Take the time to welcome and make Lily feel part of the team Go to page 5 4
THE INTRODUCTIONS Jack Tester Dave Product Owner Chris Back-end TechLead 5
THE INTRODUCTIONS Jack Tester Dave Product Owner Chris Back-end TechLead 5
THE INTRODUCTIONS Jack Tester Dave Product Owner Chris Back-end TechLead 5
THE INTRODUCTIONS Well done, Manager! You have given your agile team its first key! 6
FEATURES MONITORING Documentation Tools GO to 1st iteration! Roles Objectives 7
FEATURES MONITORING Documentation Tools GO to 1st iteration! Roles Objectives 7
FEATURES MONITORING Documentation Tools GO to 1st iteration! Roles Objectives We are the PMO, we choose to: Continue to use Giraffe, licences are expensive and need to be amortised! Go to page 8 OK use Grello, as long as I still get my crossfunctional indicators! Go to page 10 7
FEATURES MONITORING 8
FEATURES MONITORING 8
FEATURES MONITORING 8
FEATURES MONITORING Take the time to test new ways of doing things, tools and processes. Go to page 10 9
TEAM’S AUTONOMY 10
TEAM’S AUTONOMY 10
TEAM’S AUTONOMY 10
TEAM’S AUTONOMY Well done, PMO! You have given your agile team its second key! 11
AGILE COACHING 12
AGILE COACHING We are Agile Coach, we choose to: Suggest to Lily’s team a WIP limit. Go to page 14 Suggest to Lily’s team to take some time to find their own solutions. Go to page 16 12
AGILE COACHING WIP limit = 2 14
AGILE COACHING WIP limit = 2 14
AGILE COACHING WIP limit = 2 14
AGILE COACHING WIP limit = 2 14
AGILE COACHING Take the time to listen to the team, their calls for help and their needs. Go to page 16 15
SELF-EVALUATION 16
SELF-EVALUATION 16
SELF-EVALUATION 16
SELF-EVALUATION Well done, Agile Coach! You have given your agile team its third key! 17
ONGOING ITERATION 18
ONGOING ITERATION 18
ONGOING ITERATION We are Lily, developer, we choose to: Concentrate on our task: we will achieve our individual KPI of 100%! Go to page 19 Help Jack & Chris, as far as we can! Go to page 21 18
ONGOING ITERATION 19
ONGOING ITERATION 19
ONGOING ITERATION Take the time to listen to the team, their calls for help and their needs. Go to page 21 20
ONGOING ITERATION 21
ONGOING ITERATION 21
ONGOING ITERATION 21
ONGOING ITERATION 21
ONGOING ITERATION 21
ONGOING ITERATION Well done Developer! You have given your agile team its fourth key! 22
PRODUCT EVOLUTION We are the Customer, we choose to: Trust Lily’s team and validate all the functionalities later. Go to page 24 Make ourself available to be sure that the product meets our expectations. Go to page 27 23
PRODUCT EVOLUTION 24
PRODUCT EVOLUTION 24
PRODUCT EVOLUTION 25
PRODUCT EVOLUTION Take the time to give constructive feedback on what has been achieved. Go to page 27 26
INCREMENTAL PRODUCT Sprint review no. 1 27
INCREMENTAL PRODUCT Sprint review no. 2 27
INCREMENTAL PRODUCT Sprint review no. 3 27
INCREMENTAL PRODUCT Sprint review no. 3 27
INCREMENTAL PRODUCT Well done Customer! You have given your agile team its fifth key! 30
DEPLOYMENT PROCESS We are Ops, we choose to: Add the package to the next cross-company delivery shot in the IT department Go to page 32 Support the team in the ongoing deployment of its deliveries Go to page 35 31
DEPLOYMENT PROCESS Week 1 32
DEPLOYMENT PROCESS Week 2 32
DEPLOYMENT PROCESS 33
DEPLOYMENT PROCESS 33
DEPLOYMENT PROCESS Wall of confusion 33
DEPLOYMENT PROCESS Take the time to optimise the value chain from the initial idea to postproduction. Go to page 35 34
CROSS-FUNCTIONNAL TEAM CI/CD Integration tests Code quality DOD … 35
CROSS-FUNCTIONNAL TEAM CI/CD Integration tests Code quality DOD … 35
CROSS-FUNCTIONNAL TEAM Well done Ops! You have given your agile team its final key! 36
Congratulations! You have brought agility back to the developers! 1 Take the time to welcome and make the members feel part of the agile team 2 Take the time to test new ways of doing things, tools and processes 3 Take the time to sit back and think about how best to create, implement and test… 4 Take the time to listen to the team, their calls for help and their needs 5 Take the time to give constructive feedback on what has been achieved 6 Take the time to optimise the value chain from the initial idea to post-production 37
Congratulations! You have brought agility back to the developers! 1 Take the time to welcome and make the members feel part of the agile team 2 Take the time to test new ways of doing things, tools and processes 3 Take the time to sit back and think about how best to create, implement and test… 4 Take the time to listen to the team, their calls for help and their needs 5 Take the time to give constructive feedback on what has been achieved 6 Take the time to optimise the value chain from the initial idea to post-production 37
We all have a role to play in a team’s transition to agile! Manager PMO Ops Agile Coach Customer Developer 38
We all have a role to play in a team’s transition to agile! Manager TechLead PMO HR Trainer Ops Sales representative Agile Coach Tester Customer Developer … 38
Fanny KLAUK @klf37 Agile Coach, TechRel & trainer at Apside Brussel Apside TOP Tours
Fanny KLAUK @klf37 Agile Coach, TechRel & trainer at Co-creator of avec Stéphane PHILIPPART #iamlily Thanks Bitmoji
We talk about performance instead of talking about efficiency.We talk about ROI instead of continuous improvement. We emphasize monitoring over support and reporting over team protection. But give us back our agility! Let us remember that agility was thought by and for developers, eager to create useful services that are used, in a rewarding way, in varying and variable contexts.
Let’s reclaim our power as Super Agile teams!
Through scenes from our “choose-your-own-adventure book” 📖, we will see how each actor, whether Manager, Cross-functional Pilot, Agile Coach or Client, can help give us back the real keys 🔑 of your agility.
