UNITED WAY STL ACADEMY
  • Courses
  • Log In
  • Join Free
  • Home
  • Courses
  • Scrum Essentials

Scrum for Any Industry

Curriculum

  • 4 Sections
  • 15 Lessons
  • Lifetime
Expand all sectionsCollapse all sections
  • Software Development
    4
    • 1.1
      Scrum and Software Development: A Natural Fit
      10 mins
    • 1.2
      Software Flexibility and Refactoring
      10 mins
    • 1.3
      Embracing Change
      10 mins
    • 1.4
      Scrum Applications in Software
      10 mins
  • Tangible Goods Production
    5
    • 2.1
      The Fall of Waterfall
      10 mins
    • 2.2
      Construction
      10 mins
    • 2.3
      Scrum in Home Building
      10 mins
    • 2.4
      Manufacturing
      10 mins
    • 2.5
      Hardware Development
      10 mins
  • Services
    4
    • 3.1
      Health Care and Scrum
      10 mins
    • 3.2
      A Worldwide Pandemic
      10 mins
    • 3.3
      Education and Scrum
      10 mins
    • 3.4
      Military and Law Enforcement
      10 mins
  • Publishing: A Shifting Landscape
    2
    • 4.1
      A Changing Landscape in Publishing
      10 mins
    • 4.2
      News Media and Scrum
      10 mins

Construction

Scrum for Any Industry

Construction

🕐 12 min read
The Big Question

How can Scrum transform traditional construction projects to deliver faster results, better quality, and increased transparency?

Uses for Scrum within the vast world of tangible goods are enormous. The speed-to-market increase and cost savings that can be achieved in software are also possible in other areas. Construction with Scrum is an excellent example.

💡 Did You Know?

Scrum was originally designed for software development, but its principles are now revolutionizing industries from manufacturing to healthcare — including construction.

Scrum works with any project, provided you can list and prioritize the work to be done. Obviously, construction projects have these qualities. They also have challenges specific to the industry. Every segment of an industry does. Instead of saying, “Oh, Scrum won’t work with this because of X and Y and Z,” say, “These are the challenges we face, so let’s look at how Scrum will solve them and get us faster and cheaper to market.”

In the following sections, we outline specific issues in the construction industry and describe how Scrum helps solve them. By using Scrum, you see how to deal with traditional problems — those you’ve been dealing with your entire construction career.

Scrum and Lease Management

A leader of the Facilities Management technology organization for a multibillion-dollar nonprofit was in trouble. His team of experts worked to upgrade an expensive ERP (enterprise resource planning tool) but had very little to show for it. His budget was running out, and his business partners wondered where all the money was spent. He wondered if there was a better way. And there was.

How did he do it?

He found Scrum through research and signed his team and business partners up for training. Post-training, they began forming a small, cross-functional, co-located team. The team moved from their cubicles to an unused conference room where they could more easily collaborate and work together. The first product tackled using Scrum was leasing management in support of the organization’s strategy to centralize worldwide leasing while reducing headcount.

The conference room walls became the team’s workspace, where they transparently hung the product goal supported by cards describing the product roadmap divided into four balanced quadrants. The highest priority cards were progressively elaborated into sprint candidates and pulled into a sprint backlog taped on another wall with painter’s tape. The team planned their sprint, held daily scrums, and gathered feedback from stakeholders during sprint reviews and improvement ideas during sprint retrospectives.

The journey was not easy and exposed many challenges. To highlight a couple, the vendor intentionally designed the ERP platform to be manually configured. The team had to figure out how to migrate their changes consistently from a development environment to a test environment and finally into production, avoiding user downtime. They also had to integrate and collaborate with teams developing other modules in parallel using traditional project management practices (waterfall).

To overcome the platform constraints, the team adhered to a strict sprint definition of done. They created user stories with acceptance criteria as the starting point, collaborated on the process or workflow needed by the users, configured the workflow in Development, manually tested it, configured in Test, and then manually tested it there, too. They kept a change log, documentation, test cases, and a roles and responsibilities matrix updated for every story. The definition of done ensured a releasable product increment could be demonstrated every sprint.

To collaborate with the other teams using waterfall, they made an extra effort to provide transparency in their work. They published their sprint goal after every sprint planning session along with the supporting sprint backlog for all to see. They invited the other teams to listen in on their daily scrum and to participate in their sprint reviews. When dependencies were identified, the product owner worked to prioritize the team’s work navigating around or addressing the dependencies. They found open communication between the product owner and the other project managers was key.

The biggest breakthrough, however, came during a team retrospective when the team discovered keystroke automation tools existed, which created scripts that could be deployed in each environment. The automation discovery was HUGE, decreasing the time it took to promote changes from one environment to the next from multiple hours to seconds!

The results were astounding! The product was completed in three languages in half the expected time for a little less than half the remaining budget. The former project manager attended one of the team’s first sprint reviews, and their jaw dropped in amazement when they saw how much was accomplished in such a short period. More importantly, the business partner’s managing director was very pleased after the product’s iterative release and said, with a big grin, “I can’t wait to see what’s next!”

Want to go deeper? The science behind transparency in construction projects

Transparency, one of Scrum’s core pillars, directly addresses a major pain point in construction: the lack of real-time visibility. By making progress, issues, and decisions visible to all stakeholders, teams can quickly identify bottlenecks, prevent costly mistakes, and adapt to changing requirements. Research shows that transparent workflows reduce rework, improve trust, and allow teams to catch errors before they snowball.

What challenges in your current or past construction projects could benefit from Scrum’s approach to transparency and adaptation?

Construction teams adopting Scrum often report increased communication between trades, faster issue resolution, and fewer surprises at project milestones.

The Best in Bids

Competition in the bidding process for construction projects is fierce and shows no signs of trending toward easy. Combine this fact with a steady increase in construction cost, and you have a formula for cutting corners and the potential for skipping essential steps.

None of this is news to anyone in this industry. Your bid may be pristine, providing everything the client needs at a reasonable price, but you know that your competitors’ bids may undercut you by leaving things out that you know the client needs. Scrum can help both you and the client. After all, the better the client is served, the better the result, the better for your business, and the more potential for referrals.

Scrum provides the following:

  • Transparency: Let customers decide where they want their money to go. They can make changes, inspect, and adapt as the project progresses. But they’ll be fully informed each step of the way as they participate in regular progress review sessions in the sprint review, provide feedback, and ask questions.
  • Adaptability: Scrum allows the team to identify course-correcting issues early. Even when you’re building to completion, it’s better to resolve problems identified by completing a single house than to find out about them when ten houses simultaneously reach the same point of completion. Taking this example a step further, adapting to customer feedback about a nonload-bearing wall that’s misplaced is much easier to fix before electrical systems, plumbing, and drywall are installed.
  • Daily Scrum team coordination: Having an established forum for raising issues limits bottlenecks and prevents small issues from turning into big problems. If Acme Pipe Co. fails to deliver the materials you need, the Scrum master addresses the issue now and ensures it doesn’t happen again — not at the end of the week, when it comes up in a weekly status reporting meeting.

Recall the three pillars of empiricism: transparency, inspection, and adaptation. Although all three pillars serve you well throughout Scrum, the transparency issue is clearly key in the bidding and building process.

How might transparency in the bidding process influence client trust and project outcomes?

On a major hospital build, Scrum-based project teams empowered clients to adjust priorities in real-time, resulting in fewer change orders and a more satisfied stakeholder group.

⏱ 5 minutes
Activity: Mapping Construction Challenges to Scrum Solutions

Identify a challenge from your current or past construction experience and explore how Scrum could address it.

  1. Write down a challenge you’ve encountered in a construction project (e.g., missed deadlines, unclear requirements, poor communication).
  2. List the corresponding Scrum principle (e.g., transparency, daily scrum, adaptability) that could help solve this challenge.
  3. Briefly describe how that principle would change the outcome.

Consider a scenario where a minor issue is caught during a daily Scrum. How might this prevent larger problems later?

❌ Common Misconception

Scrum is only for software development and can’t handle the complexities of construction projects.

✅ The Reality

Scrum’s principles of transparency, iterative progress, and adaptability are just as effective in construction, helping teams overcome traditional bottlenecks and deliver projects faster and with higher quality.

Transparency

Ensuring all stakeholders have access to project information, progress, and challenges, enabling informed decisions and trust.

Adaptability

The ability to change course, address issues early, and incorporate feedback to improve outcomes throughout the project lifecycle.

  • Scrum can be applied to tangible goods projects like construction, not just software.
  • Transparency and adaptability are key to overcoming industry-specific challenges.

The biggest breakthrough, however, came during a team retrospective when the team discovered keystroke automation tools existed, which created scripts that could be deployed in each environment.

Flashcard

What is the primary benefit of transparency in construction projects using Scrum?

Tap to reveal
Answer

Transparency allows stakeholders to make informed decisions, adapt to changes, and build trust throughout the project.

Flashcard

What does ‘definition of done’ mean in Scrum?

Tap to reveal
Answer

‘Definition of done’ is a shared understanding of what it means for work to be complete, ensuring a releasable product increment every sprint.

Flashcard

How does Scrum help manage dependencies in construction?

Tap to reveal
Answer

Scrum encourages open communication and prioritization to address dependencies proactively, minimizing project delays.

+50 XP

Which Scrum principle is most critical in the bidding and building process for construction projects?

Review the “The Best in Bids” section above to find the answer.

Reflect on a construction project you’ve worked on or observed. If Scrum had been implemented, how would transparency, inspection, and adaptation have changed the process, communication, or outcomes?

0 words Take your time — depth matters more than length
Key Takeaway

Scrum’s principles of transparency, inspection, and adaptation empower construction teams to overcome industry-specific challenges and deliver projects faster, with higher quality and greater stakeholder satisfaction.

Key Takeaway

By embracing daily Scrum coordination, construction teams can catch and resolve small issues before they escalate, reducing delays and minimizing costly mistakes.

SHIFT

The Shift

  • Scrum can be effectively applied to construction projects, not just software.
  • Transparency and adaptability drive better outcomes, trust, and faster delivery in the construction industry.
  • Daily Scrum coordination and clear definitions of done help teams catch issues early and ensure quality.
End of lesson Ready for the next lesson?
Continue to next lesson  →

Leave a Reply Cancel reply

The Fall of Waterfall
Prev
Scrum in Home Building
Next

© 2026 United Way STL Academy | Powered by Sejal Learning Systems.

Modal title

Main Content