Jason argues project management teams should use Scrum in daily morning huddles to remove roadblocks. Flow lesson: Machinery at 4-4-2-4-4-4 parts/hour has throughput of 1.2-1.8 (not 2) because inventory builds up. Either speed up slowest machine, add another, or slow everything to 2. Fastest = add machine (4 throughput). Second fastest = slow to 2. Slowest = different speeds with max efficiency (inventory buildup). Flow is everything. Inventory is bad for cash, work in progress reduces operating cash. Meeting system: afternoon foreman huddle (gather roadblocks, plan next day, create visual day plan) → morning worker huddle (communicate, ask about roadblocks) → crew prep huddle (pre-task plans, stretch/flex) → team huddle 8-9am (PM team removes roadblocks). Best practice: roadblocks on visual maps with plexiglass in common area, scrum major efforts. Scrum for PM team: 4 columns (product backlog, sprint backlog, in progress, complete). PM team tasks don't fit time scales—they're development work (coordination, buyout, change orders, RFIs, mockups, shoring design). Trade foremen want time scales (Takt, weekly work plans, day plans). PM team should scrum roadblocks/tasks from left to right weekly. Do twice the work in half the time.
What you'll learn in this episode:
Flow lesson: Machinery at 4-4-2-4-4-4 parts/hour = 1.2-1.8 throughput (not 2) due to inventory buildup
Fastest solution: Add machine (4 throughput). Second: Slow all to 2. Slowest: Different speeds with max efficiency
Flow is everything, inventory buildup slows entire system
Inventory is bad for cash: Work in progress reduces operating cash flow
Meeting system flows: Afternoon foreman huddle → morning worker huddle → crew prep → team huddle (8-9am PM team)
Afternoon foreman huddle: Daily reports, plan next day, create visual day plan, gather roadblocks
Morning worker huddle: 5-15 min with all workers, form social group, ask about roadblocks
Crew prep huddle: Pre-task plans for quality/safety, 5S area, stretch/flex, lean training
Team huddle (8-9am): PM team removes roadblocks gathered from field
Best practice: Roadblocks on visual maps with plexiglass in common area, scrum major efforts
Scrum for PM team: 4 columns (product backlog, sprint backlog, in progress, complete)
PM team = development team moving activities left to right
Trade foremen want time scales (Takt, weekly work plans, day plans) with rows as geographical areas/swim lanes
PM team tasks don't fit time scales—they're development: coordination, buyout, change orders, RFIs, mockups, shoring design
Why scrum PM tasks: More visibility, more collaboration, roadblocks gone faster
Scrum fits development work better than scheduling work
Do twice the work in half the time by scrumming roadblocks
Use Scrum in morning team huddles. Remove roadblocks visually. 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
