{"id":23325,"date":"2023-11-18T01:22:16","date_gmt":"2023-11-18T09:22:16","guid":{"rendered":"https:\/\/essential.construction\/news\/agile-project-management-in-the-construction-industry\/"},"modified":"2023-11-18T01:22:18","modified_gmt":"2023-11-18T09:22:18","slug":"agile-project-management-in-the-construction-industry","status":"publish","type":"post","link":"https:\/\/essential.construction\/news\/agile-project-management-in-the-construction-industry\/","title":{"rendered":"Agile Project Management in the Construction Industry"},"content":{"rendered":"

\"-\"<\/a>
\n<\/p>\n

\n

The linear workflows used in the construction industry, such as the RIBA plan of work, have a history of starting when the previous phases end. The stages in these workflows are often distinct and sequential, and it might be difficult or expensive to go back after a stage is finished. Design reviews are required in this method, which is also known as the \u201cWaterfall,\u201d and they must be completed before moving on to the next level.\u00a0<\/p>\n

Cross-phase iterations are a rare symptom of problems, and the majority of design specifications will be locked early to prevent rework. Additionally, common planning and scheduling methods for the construction industry, like the Critical Path Method (CPM) and Program Evaluation and Review Technique (PERT), lack the ability to represent feedback and iteration in projects because they only permit one-way progression.\u00a0<\/p>\n

As a result, these processes have come under fire for being a linear paradigm that encourages a fragmented approach to project management, and the need for a more iterative procedure has increased.<\/p>\n

\n
\n
\n
\n
\n

To learn more about Agile project management in construction, please refer to the chapter \u201cNonlinear Project Management: Agile, Scrum and Kanban for the Construction Industry\u201d by the author, as part of a Springer book\u00a0Industry 4.0 for the Built Environment<\/a>, edited by Marzia Bolpagni, Rui Gavina, and Diogo Rodrigo Ribeiro.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

The roots of Agile project management<\/h2>\n

The Agile project management idea can be traced back to the \u201cToyota Way\u201d however, it wasn\u2019t until 1995, when Jeff Sutherland and Ken Schwaber discussed the first Agile technique for software development, that the Agile concept started to catch on. The Agile Manifesto was later written by 17 software developers who met in Utah in 2001.<\/p>\n

\u201cWe are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:<\/p>\n