Jason argues that construction should use Scrum in design instead of forcing designers into Last Planner time scales. Two lessons first: (1) Flow requires seeing multiple swim lanes together; one pull plan in one swim lane never shows flow. Takt lets you compare swim lanes to see how crews flow area-to-area. (2) Don't change schedules to the LEFT (falsifying data), but you CAN change to the RIGHT (making more accurate, updating Takt, reflecting impacts, refining from level 2→3→4→5). Normal IPD process: conditions of satisfaction, teaming, onboarding, clusters, overall master plan with milestones, pull planning to milestones using Last Planner. Jason's proposal: Keep everything the same, but use Scrum within cluster groups instead of Last Planner. Scrum = 3 roles (product owner sets vision/priority, scrum master helps team succeed, development team builds), 5 events (sprint, sprint planning, daily scrum, sprint review, retrospective), 3 artifacts (product backlog, sprint backlog, product increment). Designers procrastinate for creativity; forcing them into time scales makes them nervous. Scrum gives autonomy, creativity time, and manages complexity without forcing into timelines. If Apple/Google/Intel use Scrum, why aren't we using it in design? Do twice as much work in half the time with less complexity?

What you'll learn in this episode:

• Lesson 1: Flow requires seeing multiple swim lanes together; a pull plan never shows flow

• Takt planning lets you compare swim lanes to see how crews flow area-to-area on time scale

• Lesson 2: Don't change schedule LEFT (falsifying), CAN change RIGHT (more accurate)

• RIGHT changes: Update Takt, reflect impacts, recovery schedule, refine level 2→3→4→5

• Normal IPD: Conditions of satisfaction, teaming, clusters, master plan, pull planning to milestones using Last Planner

• Jason's proposal: Use Scrum within cluster groups instead of Last Planner in design

• Scrum = 3 roles, 5 events, 3 artifacts (353 framework)

• 3 roles: Product owner (voice of customer, sets vision/priority), scrum master (servant leader, helps team), development team (cross-functional, builds product)

• 5 events: Sprint (fixed duration), sprint planning (what to accomplish), daily scrum (huddle), sprint review (check minimum viable product), retrospective (how to improve)

• 3 artifacts: Product backlog (all tasks), sprint backlog (this sprint's tasks), product increment (completed work)

• Scrum board: 4 columns (backlog, sprint backlog, in progress, complete)

• Why Scrum for designers: More autonomy, creativity time, and manages complexity

• Designers procrastinate for creativity, forcing them into time scales makes them nervous

• Scrum = small teams, small durations, prioritized tasks, autonomous work

• Apple/Google/Intel use Scrum, why aren't we using it in design?

• Do twice as much work in half the time with less complexity, no bureaucracy

• Minimum viable product mindset: Speed to market, get feedback, iterate (like video games, Jason's books)

Use Scrum in design. Designers will love it. On we go.

If you like the Elevate Construction podcast, please subscribe for free, and you'll never miss an episode. And if you really like the Elevate Construction podcast, I'd appreciate you telling a friend (Maybe even two 😊).

Also, here are links to our YouTube Channels:

· Jason Schroeder YouTube Channel: https://www.youtube.com/channel/UC4xpRYvrW5Op5Ckxs4vDGDg

· LeanTakt YouTube Channel: https://www.youtube.com/c/leanTakt

· LeanSuper YouTube Channel: https://www.youtube.com/channel/UCzQDevqQP19L4LePuqma3Fg/featured

· LeanSurvey YouTube Channel: https://www.youtube.com/channel/UC-Ztn3okFhyB_3p5nmMKnsw