Post M&A Integration Project Management methodology – Waterfall vs. Agile
- This topic has 18 replies, 19 voices, and was last updated 3 months, 3 weeks ago by
.
-
Posts
-
Based on experience, both Waterfall & Agile (i.e. “Agile-Fall”) can be effective when working together. We need something defined & repeatable, but also the ability to adapt in real-time to the inevitable problems & changes of course that will inevitably arise.
From my experience Waterfall methodology is the more suitable for the overall IMO. However, there are certainly cases where workstreams can mix up methodologies. For example in the Tech workstream Agile can be used, as with cross workstream initiaves that impact a certain synergy case and need cross workstream collaboration and scales approach.
Similar to many others above, I have used a combination of waterfall and adaptive ways of working. I particularly like visual project management with time-boxed KANBAN and frequent demos of progress/ deliverables to gain timely feedback and builds from stakeholders.
In my experience, Waterfall methodology defines the sequencing of the entire program as a whole. However Agile methodology must be introduced in parallel to introduce sufficient degree of flexibility and adaptability for multiple workstreams within the program. One key milestone must not halt the entire program.
- You must be logged in to reply to this topic.