The primary challenge we faced was the rigidity and inefficiency inherent in traditional construction project management methods, especially within Virtual Design and Construction (VDC). Traditional approaches rely heavily on linear processes and static Gantt charts, which often lack the flexibility to adapt to changes or incorporate iterative feedback effectively. This rigidity can lead to miscommunication, delays, and increased costs, particularly in complex projects like SAMIH.
Additionally, quantifying the scope of work for VDC was particularly challenging due to the high level of uncertainty at the project's inception. When VDC teams begin their work, detailed information is often lacking, and the construction project is at its peak uncertainty. This scarcity of information necessitates the use of placeholders in models and plans, which can negatively impact productivity and lead to significant rework as more information becomes available. The inability to accurately define the scope and account for these uncertainties makes planning and resource allocation difficult, hindering the efficiency of VDC processes under traditional methodologies.
Another significant problem was the difficulty in measuring productivity and progress in a meaningful way. Without agile metrics like story points and velocity, it was challenging to quantify team performance, forecast project timelines accurately, or identify areas needing improvement.
Our goal was to overcome these challenges by introducing a more flexible, collaborative, and efficient methodology that could handle the complexities of modern construction projects. By integrating Scrum and agile practices into VDC, we aimed to enhance adaptability, improve stakeholder communication, and deliver higher-quality outcomes within shorter timeframes.
Our solution involved integrating Scrum, an agile methodology, into the VDC processes of the SAMIH construction project, effectively creating Agile VDC. This approach directly addresses the challenges of rigidity, inefficiency, and high uncertainty in traditional project management by introducing flexibility, collaboration, and iterative development.
By productizing traditional VDC processes, we reimagined each deliverable—such as the 3D BIM model, installation drawings, and fabrication spool drawings—as individual products. Instead of viewing these tasks as sequential steps in a linear process, we treated each deliverable as a standalone product with its own development lifecycle, applying Scrum to develop these products iteratively.
This shift allowed us to focus on each product's requirements and manage uncertainties more effectively. Treating each deliverable as a product enabled us to prioritize features, incorporate stakeholder feedback promptly, and adapt to changes without derailing the entire project. Specialized teams dedicated to each product enhanced collaboration and alignment with overall project goals.
We also broke down the construction project into zones that align with sprint durations, enabling iterative progression. Each zone and product underwent the "plan-do-check-act" cycle inherent in Scrum, allowing continuous improvement and rapid adaptation to changes or stakeholder feedback. The use of a Definition of Done and obtaining stakeholder approval before moving on ensured quality and alignment with client expectations.
Replacing the traditional Gantt chart with a dynamic roadmap provided greater agility in planning and execution, allowing teams to adjust priorities without disrupting the entire project schedule.
By employing agile metrics such as story points, user stories, and velocity, we gained valuable insights into team productivity and project progress, facilitating better forecasting, resource allocation, and identification of areas needing improvement.
Overall, our solution resolved the challenge by transforming traditional VDC deliverables into products developed through Scrum, creating a more adaptable, collaborative, and efficient project management framework that directly addresses uncertainties at the project's inception.
