Team Transformation Workshop

616 views
463 views

Published on

Workshop for the Database Management Services team at University of Michigan Medical school where they reviewed a strategy canvas, created a team canvas, decided on a methodology, played a lean game to learn a pull versus a push workflow and built a team kanban board.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
616
On SlideShare
0
From Embeds
0
Number of Embeds
14
Actions
Shares
0
Downloads
30
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Team Transformation Workshop

  1. 1. @_AprilJefferson CuriousAgility.blogspot.com Team Transformation Workshop Working Agreements Big Picture 9:30 Review Strategy Canvas 30 MINS Create Team Canvas 60 MINS Break 15 MINS Style 11:15 Review Options 30 MINS Decide 15 MINS Lunch Break 30 MINS Pull Systems 12:30 Lean Simulation 60 MINS Review Options 30 MINS Break 15 MINS Design Workflow 90 MINS End 4:00
  2. 2. TRANSFORMATION CANVAS Agree on Change Negotiate the Change Validate Behavior Verify Performanc e
  3. 3. @_AprilJefferson CuriousAgility.blogspot.com Why Transformation Canvas? Discovery • What’s Really Going On • Most Valuable Change Transparency • Urgency for Change Visibility • Changes Being Made Alignment • Change Agents • Open and Honest Dialogue
  4. 4. Process Pushing Machine Change Team as a Support Group
  5. 5. Look at Improvement Strategy with Change Options of Change Agents Big Picture Review
  6. 6. @_AprilJefferson CuriousAgility.blogspot.com What Change Are We Making?
  7. 7. @_AprilJefferson CuriousAgility.blogspot.com Why is this Change Important?
  8. 8. @_AprilJefferson CuriousAgility.blogspot.com How Will We Measure Success?
  9. 9. @_AprilJefferson CuriousAgility.blogspot.com How Will We Demonstrate Progress?
  10. 10. @_AprilJefferson CuriousAgility.blogspot.com Who Are Affected By This Change?
  11. 11. @_AprilJefferson CuriousAgility.blogspot.com What Investments Are Needed?
  12. 12. @_AprilJefferson CuriousAgility.blogspot.com How Will We Help People Transition?
  13. 13. @_AprilJefferson CuriousAgility.blogspot.com How Will Change Be Made Visible?
  14. 14. @_AprilJefferson CuriousAgility.blogspot.com Change Options
  15. 15. The Enabling of Strategic Synergies Between All Affected Parties Calling Shenanigans!
  16. 16. @_AprilJefferson CuriousAgility.blogspot.com How Will We Do This? Powerful Questions Silent Brainstorming One thought per sticky Review as a Group Discuss and refactor
  17. 17. @_AprilJefferson CuriousAgility.blogspot.com What words/phrases stuck out for you?
  18. 18. @_AprilJefferson CuriousAgility.blogspot.com What was interesting to you?
  19. 19. @_AprilJefferson CuriousAgility.blogspot.com What did you find worrisome about this canvas?
  20. 20. @_AprilJefferson CuriousAgility.blogspot.com What is supporting this change?
  21. 21. @_AprilJefferson CuriousAgility.blogspot.com What is working against this change?
  22. 22. @_AprilJefferson CuriousAgility.blogspot.com How can your team contribute to this vision?
  23. 23. @_AprilJefferson CuriousAgility.blogspot.com What help would you need to contribute to this vision?
  24. 24. Feedback Driven Change Process Now What?
  25. 25. @_AprilJefferson CuriousAgility.blogspot.com Strategy Canvas Team Canvas Feedback and Iterate • Share with Change Agents • Explore Similarities and Differences • Make Changes from Feedback
  26. 26. @_AprilJefferson CuriousAgility.blogspot.com Feedback  Please score this session on a sticky 5 Awesome to 1 Needs Work If below 5 include what would make it better Place Sticky on door under “Big Picture”
  27. 27. @_AprilJefferson CuriousAgility.blogspot.com 15 MINUTE BREAK
  28. 28. STYLE How Will We Do Agile/LEAN?
  29. 29. Scrum Kanban Scrumban Board/Artifacts simple board product backlog sprint backlog product increment burndown chart board mapped on the process board mapped on the process Ceremonies daily Scrum sprint planning sprint review sprint retrospective none required daily Scrum other Scrum related ceremonies if needed Prioritization Part of backlog grooming. Done by PO Out of the process. There should be a prioritized backlog. Out of the process. There should be a prioritized backlog. Who feeds the work in progress ("brings new work") PO Depends on defined roles and necessities Depends on defined roles and necessities Iterations yes (sprints) no (continuous flow) not mandatory (continuous flow); could have sprints Estimations yes (in ideal days or story points) no (similar work size items) (a) no (similar work size items) (a) Teams recommended cross functional cross functional or specialized cross functional or specialized Roles Product Owner Scrum Master Team as needed Team + as needed Teamwork collaborative based on pull approach based on pull approach WIP planned for the duration of the sprint controlled by workflow state controlled by workflow state changes to work scope should wait for next sprint added as needed (JIT) added as needed (JIT) Product backlog prioritized list of user stories (estimated) no (JIT) no (JIT) Impediments addressed immediately addressed immediately (b) addressed immediately (b) When does it fit? Product development Small value adding increments development possible Requirements are in good shape Support/maintenance work (operational level) Product development (unclear vision) Evolving requirements (no clear roadmap) Need to include support/maintenance (event driven) work in the process (a) team needs to comment on non-fitting work items in order to ensure readiness (b) "stop the line" approach; teams should swarm to solve the impediment http://www.ontheagilepath.net/2013/09/scrum-kanban-scrumban-fast-overview-and.html#sthash.zTUaNzB7.dpuf
  30. 30. @_AprilJefferson CuriousAgility.blogspot.com What works for you?
  31. 31. @_AprilJefferson CuriousAgility.blogspot.com Feedback  Please score this session on a sticky 5 Awesome to 1 Needs Work If below 5 include what would make it better Place Sticky on door under “Style”
  32. 32. @_AprilJefferson CuriousAgility.blogspot.com 30 MINUTE LUNCH BREAK
  33. 33. PULL SYSTEMS Learn, See, Create
  34. 34. Game to demonstrate LEAN principles Lean Simulation
  35. 35. @_AprilJefferson CuriousAgility.blogspot.com Dot Game Complete features which are defined to be 1 yellow sticky note that has 6 colored stickers in the following pattern B B G R Y G
  36. 36. @_AprilJefferson CuriousAgility.blogspot.com Choose a Role  BA picks 6 post-its and passes them to Technical Analyst  TA puts on yellow dots  Designer puts on red dot  UX DEV puts on green dots  DEV puts on blue dots  Tester tests putting in defect area if it doesn’t look like sample  Project Manager times Time it takes for first batch to be completed Warms team when there is one minute left Tells team when time is out (after 5 minutes)  Customer accepts or rejects
  37. 37. @_AprilJefferson CuriousAgility.blogspot.com Get in Position Designer IN Area (materials) UI Developer Technical Analyst Developer Business Analyst Tester OutArea
  38. 38. @_AprilJefferson CuriousAgility.blogspot.com Round 1 5 MIN  Each role should work as fast as they can  Don’t worry if the person next to you is keeping up  Remember you are working in batches  Do 6 at a time then handoff all 6 at the same time
  39. 39. @_AprilJefferson CuriousAgility.blogspot.com So how many accepted?
  40. 40. @_AprilJefferson CuriousAgility.blogspot.com What Is Our . . .  (WIP)Work In Progress = Stickys Started  (TP) Throughput = Stickys Done/5 MINS  (CT)Cycle Time = WIP/TP MINS
  41. 41. @_AprilJefferson CuriousAgility.blogspot.com What Did We Learn? WIP Rises with Bottlenecks Cycle Time Unstable & Unpredictable
  42. 42. @_AprilJefferson CuriousAgility.blogspot.com How Could We Improve?  Smooth Flow  Increase Productivity and Quality Minimize WIP Pull instead of Push Slow Down to Speed Up
  43. 43. @_AprilJefferson CuriousAgility.blogspot.com BATCH VS LEANInputArea Backlog WorkArea Empty OutputArea Occupied InputArea Backlog WorkArea Empty OutputArea Empty Push Pull If work area empty then take from input area If work area empty and output area empty then take from input area
  44. 44. @_AprilJefferson CuriousAgility.blogspot.com Round 2 5 MIN  Minimize WIP Finish Before You Start Set Limits  Quality Matters B B G R Y G
  45. 45. @_AprilJefferson CuriousAgility.blogspot.com So how many accepted?
  46. 46. @_AprilJefferson CuriousAgility.blogspot.com What Is Our . . .  (WIP)Work In Progress = Stickys Started  (TP) Throughput = Stickys Done/5 MINS  (CT)Cycle Time = WIP/TP MINS
  47. 47. @_AprilJefferson CuriousAgility.blogspot.com What Did We Learn? Bottlenecks Gone Cycle Time Improved
  48. 48. @_AprilJefferson CuriousAgility.blogspot.com How Could We Improve?  Smooth Flow Balancing Number of Dots “In Place” Testing Talking to Customer Remove Waste & Get Feedback
  49. 49. @_AprilJefferson CuriousAgility.blogspot.com Round 3 5 MIN  Maximize Throughput
  50. 50. @_AprilJefferson CuriousAgility.blogspot.com So how many accepted?
  51. 51. @_AprilJefferson CuriousAgility.blogspot.com What Is Our . . .  (WIP)Work In Progress = Stickys Started  (TP) Throughput = Stickys Done/5 MINS  (CT)Cycle Time = WIP/TP MINS
  52. 52. @_AprilJefferson CuriousAgility.blogspot.com What Did We Learn? Cycle Time Stable & Predictable without Bottlenecks & with Smooth Flow!
  53. 53. @_AprilJefferson CuriousAgility.blogspot.com Feedback  Please score this session on a sticky 5 Awesome to 1 Needs Work If below 5 include what would make it better Place Sticky on door under “Dot Game”
  54. 54. Endless Options Kanban Boards
  55. 55. @_AprilJefferson CuriousAgility.blogspot.com What Are The Possibilities? 10 MINS  Review Examples Around Room  Silently Identify Observations 1Thought per Sticky Adhere to Board Avoid Duplicates
  56. 56. @_AprilJefferson CuriousAgility.blogspot.com What Did We Learn? 2 MINS EACH Quickly Discuss Observations Together
  57. 57. @_AprilJefferson CuriousAgility.blogspot.com Feedback  Please score this session on a sticky 5 Awesome to 1 Needs Work If below 5 include what would make it better Place Sticky on door under “Kanban Boards”
  58. 58. @_AprilJefferson CuriousAgility.blogspot.com 15 MINUTE BREAK
  59. 59. An inspection and adaption using lean principles So What’s Our Workflow?
  60. 60. @_AprilJefferson CuriousAgility.blogspot.com What kinds of work do we want to visualize? Why?
  61. 61. @_AprilJefferson CuriousAgility.blogspot.com Pair Up then Put on Your Designer Hat! Choose Share Refactor Design Define Design workflow proposal with a Kanban 30 MINS Each pair gives elevator pitch Team identifies what they like about it 10 MINS Team picks board for final group refactor 5 MINS Team uses feedback to revise design together 20 MINS Decide on the policies for each part of workflow 25 MINS
  62. 62. @_AprilJefferson CuriousAgility.blogspot.com Design Board Choose Share Refactor Design Define Design workflow proposal with a Kanban 20 MINS
  63. 63. @_AprilJefferson CuriousAgility.blogspot.com Share Board Choose Share Refactor Design Define Each pair gives elevator pitch Team identifie s what they like about it 20 MINS
  64. 64. @_AprilJefferson CuriousAgility.blogspot.com Choose Board Choose Share Refactor Design Define Team picks board for final group refactor 5 MINS
  65. 65. @_AprilJefferson CuriousAgility.blogspot.com Refactor Board Choose Share Refactor Design Define Team uses feedback to revise design together 20 MINS
  66. 66. @_AprilJefferson CuriousAgility.blogspot.com Define Rules Choose Share Refactor Design Define Decide on the policies for each part of workflo w 25 MINS
  67. 67. @_AprilJefferson CuriousAgility.blogspot.com
  68. 68. @_AprilJefferson CuriousAgility.blogspot.com Feedback  Please score this session on a sticky 5 Awesome to 1 Needs Work If below 5 include what would make it better Place Sticky on door under “Workflow Design”
  69. 69. Sources Thanks! Lean Change Management Jason Little, LeanChange.org Methodology Comparison http://www.ontheagilepath.net/2013/09/scrum-kanban-scrumban-fast-overview- and.html#sthash.zTUaNzB7.dpuf Lean Dot Game http://www.netobjectives.com/system/files/DotGame_vas11_0.pdf Sample Kanban Boards Mattias Skarin, blog.crisp.se/mattiasskarin Random Boards from Google images that were not copyrighted Peer Consulting Gerry Kirk, GerryKirk.org
  70. 70. @_AprilJefferson CuriousAgility.blogspot.com BLOG CuriousAgility.Blogpost.com TWITTER @_AprilJefferson

×