What are the best practices for selecting an agile framework in construction projects?

1 Project characteristics

The first step in choosing an agile framework is to assess the project characteristics, such as the scope, complexity, uncertainty, and duration. Different agile frameworks have different strengths and weaknesses in dealing with these factors. For example, Scrum is a popular agile framework that works well for projects with clear and stable requirements, frequent feedback, and short iterations. However, Scrum may not be the best choice for projects with high uncertainty, changing scope, or long-term planning. In that case, other agile frameworks, such as Kanban, Lean, or Crystal, may be more suitable.

2 Team capabilities

The second step in choosing an agile framework is to evaluate the team capabilities, such as the size, skills, experience, and collaboration. Different agile frameworks have different requirements and expectations for the team members. For example, Scrum requires a small and cross-functional team that can self-organize and deliver a potentially shippable product increment every iteration. However, Scrum may not be the best choice for teams that are large, distributed, or specialized. In that case, other agile frameworks, such as SAFe, LeSS, or DAD, may be more suitable.

3 Stakeholder expectations

The third step in choosing an agile framework is to understand the stakeholder expectations, such as the quality, cost, time, and value. Different agile frameworks have different ways of managing and communicating these aspects. For example, Scrum relies on a product backlog, a product owner, and a sprint review to prioritize and deliver value to the stakeholders. However, Scrum may not be the best choice for projects that have multiple or conflicting stakeholders, fixed or rigid contracts, or complex or regulated environments. In that case, other agile frameworks, such as XP, FDD, or ASD, may be more suitable.

4 Agile maturity

The fourth step in choosing an agile framework is to consider the agile maturity of the organization and the team. Agile maturity is the degree to which an organization or a team has adopted and implemented agile principles and practices. Different agile frameworks have different levels of agility and complexity. For example, Scrum is a simple and lightweight agile framework that can be easily learned and applied by beginners. However, Scrum may not be the best choice for organizations or teams that have advanced or mature agile capabilities. In that case, other agile frameworks, such as Scrum@Scale, Nexus, or Spotify, may be more suitable.

5 Agile adaptation

The fifth step in choosing an agile framework is to remember that agile is not a one-size-fits-all solution. Agile frameworks are not meant to be followed blindly or rigidly. Agile frameworks are meant to be adapted and customized to fit the specific needs and context of each project. Therefore, the best practice for selecting an agile framework is to use it as a starting point, not as an end point. The team should continuously inspect and adapt the agile framework, based on the feedback, learning, and improvement that occur throughout the project.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?