Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

TechEvent Turbo SCRUM

52 visualizaciones

Publicado el

Turbo SCRUM - Produce 1 product during 3 sprints in 5 hours

Publicado en: Tecnología
  • Sé el primero en comentar

  • Sé el primero en recomendar esto

TechEvent Turbo SCRUM

  1. 1. BASLE BERN BRUGG DÜSSELDORF FRANKFURT A.M. FREIBURG I.BR. GENEVA HAMBURG COPENHAGEN LAUSANNE MUNICH STUTTGART VIENNA ZURICH Turbo SCRUM Produce 1 product during 3 sprints in 5 hours Remco Bonse TVD Basel Bertil Alexandersson TVD Basel
  2. 2. Turbo SCRUM2 10/2/2018 ‘’This was the most exciting experience since many years.’’ Bertil Alexandersson ‘’As a consultant, this was the most exciting experience since many years.’’ Bertil Alexandersson
  3. 3. 3 10/2/2018 Once upon a time... Turbo SCRUM
  4. 4. Going back to early 2018... 4 10/2/2018 Trivadis wants to win the World Cup! – Or next best thing; to win a large contract for a Swiss Canton computer service department Part of tender – Need of several Managed Teams to execute Software Projects – Selection of preferred suppliers with internal ranking – Contract duration: 4,5 years, possible extension to 8.5 years – Managed Teams volume can mean up to 16 consultants per year (FTE) Trivadis Basel is determined to catch this fish! Turbo SCRUM
  5. 5. Assessment Description – Goals 5 10/2/2018 Selection criteria – Price of offered services – Assessment of managed teams Factors to assess – Know-how level of methodology – Know-how level of technologies (HTML5, Angular and Java EE as well as CI/CD) – Social competence – Team work – Agility Turbo SCRUM
  6. 6. Assessment Description – Content 6 10/2/2018 Content – Methodology: SCRUM – Duration: 5 hours – Start Scenario: Customer presents Business Case – Required content: Team must perform 3 sprints „Live Programming is expected“ Tools Jira and Confluence must be used Conclusion: Focus of assessment is not on technology but on methodology and team work! Turbo SCRUM
  7. 7. 7 10/2/2018 Assessment Preparation Turbo SCRUM
  8. 8. Assessment Team – Required roles 8 10/2/2018 Michael Könings Product Owner (Team Captain) Remco Bonse Frontend Developer SCRUM Master Mattia Baldinger Frontend Developer Erhan Ünlü DevOps Bertil Alexandersson Backend Developer Sven Lau Backend Developer SCRUM Master (!= Product Owner) TVD Basel All Star Team Colin Hoffmann DevOps Specialist Backup & Support A Team with a lot of experience apart from working as a team. Turbo SCRUM
  9. 9. Preparation Team 9 10/2/2018 Alexander Papezik Tender Manager Head Coach Additional staff Caspar von Stülpnagel Co-Leader TVD Basel Fabiano Marraffino Co-Trainer Benno Leuenberger Co-Leader TVD Basel Gianleandro Sarro Business Developer Roland Siposs Solution Unit Manager Turbo SCRUM
  10. 10. Assessment Preparation Timeline 10 10/2/2018 March April 1712 19 9 Assessment School Holiday Mission Impossible: Get 10 people together to prepare Turbo SCRUM
  11. 11. March 12th – Assessment Team Kickoff 11 10/2/2018 Tender specifics were presented Dear Team, I want you to win this World cup, euh Tender What do you need to succeed? Time for 2 Trial runs and preparation Turbo SCRUM
  12. 12. Trial Run definition 13 10/2/2018 Goal – Simulate the real assesment: The Team needs to – Create a working application – Under time pressure – With an audience Improvement cycle: – Feedback by audience and team after each run – weekly calls to share team knowledge. Turbo SCRUM
  13. 13. Preparation tasks 14 10/2/2018 Tasks before 1st Trial Assessment – Create a test bussiness case – invite an good audience ( Trainers) – Define Scrum meetings (Scrum master and Product owner) – Setup Project tool(Jira) and source code repository (PO ) – Setup VMs with complete technology stack ( DevOps) – Develop template code (Back and front end) – Setup Development and Test servers with CI/CD (DevOps) Turbo SCRUM
  14. 14. March 19th – 1st trial run: 5 hours 15 10/2/2018 Content – Trainers present Business Case – Time is given to discuss SCRUM and process improvements – Result: Team completes only two sprints and no functional web app Conclusion Storming: Communication and team integration must improve! – Various levels of SCRUM know-how – Coding takes too long – Almost all phases took too long => brush up on and discuss SCRUM => reduce code complexity further => improve time keeping Turbo SCRUM
  15. 15. Improvements until next trial run 16 10/2/2018 All must brush up on their SCRUM skills – SCRUM Master and PO decide on rules for Turbo SCRUM Reduce code complexity – Better code templates for frontend and backend – Implement login via Facebook and authorization via OAuth – Use only generic JSON entities in one database table Prepare visualizations of concepts Setup communication channel for easy info and file distribution Turbo SCRUM
  16. 16. April 9th – 2nd trial run: 5 hours 17 10/2/2018 Content – Trainers present a new Business Case – Team uses all parts of SCRUM and develops a web app – Note: No discussion regarding SCRUM methodology – Result: Team completes three sprints and a some-what functional web app Conclusion – Goals of SCRUM meetings not clear => consolidate SCRUM Meetings – Communication and team integration => rehearse team interaction – Time keeping suffers under SM and front end => develop detailed time schedule – Norming: We have improved a lot but we want to do better! Average Self- Assessment Grade* 6 points *) Scale 1 - 10 Turbo SCRUM
  17. 17. Assessment Preparation Timeline 18 10/2/2018 12 March April 19 9 12 17 Assessment School Holiday Turbo SCRUM
  18. 18. April 12th – 3rd trial run: 3 hours 19 10/2/2018 Content – Trainers present Business Case – Team uses all parts of SCRUM and develop a web app – Result: Team completes two sprints, no functional web app (not enough time) Conclusion – Minor improvement since last run – Communication and team integration still needs improvement – Still uncertainties regarding SCRUM => define our SCRUM process in more detail – We want to do even better! Average Self- Assessment Grade 6.5 points Turbo SCRUM
  19. 19. Assessment Preparation Timeline 20 10/2/2018 12 March April 19 9 12 17 Assessment School Holiday 16 Turbo SCRUM
  20. 20. April 16th – 4th trial run and final preparations: 1 day 21 10/2/2018 Content – Team review and individual trainings – PO and SM define Turbo SCRUM process in detail – Perform trial sprints and test time schedule – Result: Performing Team completes three sprints and a functional web app Average Self- Assessment Grade >8 points Turbo SCRUM
  21. 21. Turbo SCRUM 23 10/2/2018 Turbo SCRUM – Implementation of SCRUM process build for speed and demonstration SCRUM Meetings have – goals for Team members – fixed times with dedicated Time Keeper Recommendations – Sprint Planning with Magic Estimates – Retrospective with observe, summarize, act – Visual Time Keeping 0 1 2 3 5 8 13 20 Turbo SCRUM
  22. 22. Assesment Preparation Summary Name Presentation24 10/2/2018 Conclusion – We have reached a stage of high team spirit, high quality and high efficiency! – Bring it on!  Well actually I could use some sleep Were is the emergency exit!?
  23. 23. 25 10/2/2018 Assessment day Turbo SCRUM
  24. 24. At 6:30 am... April 17th – Assessment day 26 10/2/2018 Turbo SCRUM
  25. 25. April 17th – Assessment day meet up 27 10/2/2018 Place to make history! Assessment Team Support Team 6:30 Turbo SCRUM
  26. 26. April 17th – Assessment day 28 10/2/2018 Start time: 5 persons from customer side 20 minutes introduction round and setting ground rules 5 hours of assessement Sandwiches are for free... 7:00 Playing role of client in business case The rest watching, making notes, taking pictures in silence... Turbo SCRUM
  27. 27. Let the game begin! What about a game plan?
  28. 28. Name Presentation30 10/2/2018 Phase Sprint 1 Sprint 2 Sprint 3 Customer explains Business Case 10 * Fill Backlog with User Stories 15 Backlog Estimation 15 Sprint Planning 1 – Commit 10 10 10 Sprint Planning 2 – Taskification 10 10 10 Sprint – Part 1 20 20 20 Daily Standup 5 5 5 Sprint – Part 2 20 20 20 Sprint Review 10 10 10 Sprint Retrospective 10 10 10 Sprint = 85 minutes*) Phase times in minutes Timekeepers job 1st call: «We now start Sprint Part 1, it will last for 20 minutes, I will let you know when 3 minutes are left.» 2nd call: «3 minutes left, start to wrap up what you are doing.» 3rd call: «Sprint Part 1 is over, we must move on to the next phase.» Max 2 hours of programming Total = 295 minutes = 4:55 hours
  29. 29. April 17th – After 5 hours of intense team work... 31 10/2/2018 But how did it go? Turbo SCRUM
  30. 30. April 17th – Assessment day retrospective 32 10/2/2018 Preparation had been excellent! – Correct focus – Team work and pragmatic SCRUM – Technical simplicity essential – We developed a working web app! – Dedicated Time Manager – Reduced stress to close to zero – Everyone knew what to do! – Everyone was integrated into a team! Turbo SCRUM
  31. 31. April 17th – Assessment day retrospective 33 10/2/2018 Assumptions made were mostly correct – Business case – pretty much as expected – Customer behavior – nicer than our trainers during trial runs  Handling changed customer request (drop login via Facebook) – Change was significant => Stop 3rd sprint – Restart short 4th sprint (45 min) with a different user story Total focus on task – No time to eat sandwiches Turbo SCRUM
  32. 32. April 17th – Co-Leader called for a lunch celebration... 34 10/2/2018 Turbo SCRUM
  33. 33. 35 10/2/2018 Lessons learned Turbo SCRUM
  34. 34. Lessons learned – Part I 36 10/2/2018 Trial runs and preparations are essential! – Forming a team from great individuals takes time: Forming, Storming, Norming, Performing – Prepare every artefact and template possible – Budget was exceeded with 50% (but it was worth it!) Minimize technical complexity – No innovation possible during strict time constraints – Prepare generic and reusable code templates – Pragmatic technical solution rather than realistic solution Turbo SCRUM
  35. 35. Lessons learned – Part II 37 10/2/2018 Focus on the essential SCRUM / Agile elements Plan, do, inspect, adapt instead of cargo cult Define backups and involve them in preparation process – Early involvement reduces overall risk for assessment team – Backups can become support during preparation Delegate Scrum Master Tasks (time keeping, boards etc) – Difficult for SCRUM Master to moderate and keep track of time in parallel – Other team members can focus on keeping phases time boxed Turbo SCRUM
  36. 36. 38 10/2/2018 And the end of the story? Turbo SCRUM
  37. 37. Tender result for Managed Teams 39 10/2/2018 Official winners of tender were announced end of June – Trivadis is one of three becoming Preferred Supplier Official ranking among suppliers announced beginning of July – Trivadis is ranked 1st among Preferred Suppliers First Pilot Project will be executed in autumn or winter of 2018 Turbo SCRUM
  38. 38. 40 10/2/2018 And just one more thing... Turbo SCRUM
  39. 39. 41 10/2/2018 Coming soon... A Trivadis Basel production... Where mice become heroes... ... and new Agile masters are form Turbo SCRUM
  40. 40. 42 10/2/2018 Turbo SCRUM
  41. 41. New internal offering (?) – Agile Bootcamp 43 10/2/2018 Providing Managed Teams calls for reproducing the preparation effort Two day Workshop in Agile Projects and SCRUM – Team excercises to practice all SCRUM phases using KANBAN board From creating User Stories to Sprint Retrospective – Coached by an experienced Drill Sergeant – Two different SCRUM projects with two sprints each to be performed Turbo SCRUM
  42. 42. Target audience – Inexperienced SCRUM Teams which want to get up to speed fast – Team size 5 – 8 people filling all essential SCRUM roles Pre-requisite – Participants have knowledge of SCRUM methodology Reading SCRUM manifest is enough, no certification is required – Note: Agile Bootcamp is focussed on practical exercises and small theory blocks and does not lead to a SCRUM certification New internal offering (?) – Agile Bootcamp 44 10/2/2018 Turbo SCRUM
  43. 43. Remco Bonse remco.bonse@trivadis.com Bertil Alexandersson bertil.alexandersson@trivadis.com 10/2/201845 Questions & Answers Turbo SCRUM
  44. 44. Session Feedback – now TechEvent September 201846 14.09.2018 Please use the Trivadis Events mobile app to give feedback on each session Use "My schedule" if you have registered for a session Otherwise use "Agenda" and the search function If the mobile app does not work (or if you have a Windows smartphone), use your smartphone browser – URL: http://trivadis.quickmobileplatform.eu/ – User name: <your_loginname> (such as "svv") – Password: sent by e-mail...
  45. 45. © Trivadis – Kick-Off ZID Delivery Model47 10/2/2018

×