On this reflection I will deal separately with traditional models and agile models. A small SWOT analysis is shown for each model below.
Traditional Project Management
Strengths
They are ideal for predictable projects, also for those in which a command and control approach is looked for as they are used to gain control. This model could work in chaotic systems, those that are in the unknown space with not much time to react.
Weaknesses
Suffer from a bad adaptation to late change requests. It's sequential and rigid approach - closed to the option of going back and review a certain stage, once each of the stages is over - is their biggest weakness. That makes it inflexible. It's prone to too much red tape if applied 'by the book'. It focuses on what was signed off, leaving outside what could have turned to be the real need. It can get to be too procedural.
Opportunities
Those projects where all requirements are known in advance or they can be found up front; or projects with repeating patterns or well known steps are a good opportunity for traditional models.
Threats
Change requests, problems with documentation being unnecessarily excessive as it´s applied by the book instead of as and when needed.
Documentation is not always easy to mantain, analysis paralisis can be a problem during some phases.
It can end up perversely transformed in a formal justification of who did what to avoid being pointed out as the one to blame, losing focus on what needs to be done and focusing on "protecting oneself from future punishment".
Agile Project Management
Strengths
Ideal for projects with emergent answers across time or where many ideas exist and compete between them. It´s adaptability, flexibility and transparency make it ideal for hearing everyone involve, discussing different ideas and approaches and reaching agreements, modifications, etc. based on the feedback received from all parties involved (including the final user). It potentiates a more effective communication, collaboration and cross-functionality. It empowers those with the knowledge to do the correspondent tasks. It (hopefully) provides a product that it's fit for purpose, with all the involved parties taken in consideration. It provides the product the customer wants, not the one the company wanted without receiving feedback from customers.
Weaknesses
It doesn´t work in chaotic systems and it's not needed in situations where all the answers are known in advance and there is no change to be expected, those projects that are in the fully unknown space with not much time to react or take decisions are not fit for an agile model. The model turns innefficient when the some stakeholders are voluntarily absent during the process or when no self-organising is present and this turn the experience in an environment where the focus is moved into the wellbeing of the team and delivering the product takes a second place.
Opportunities
Projects where changes are expected, where there is enough time to take the right decisions and where the final product is not 100% defined in advance, following the idea that the client cannot know exactly what they want until they see it.
Transforming entire organisations was left for traditional models in the past as big organisations where afraid of trying, fortunately there is now an opportunity for the agile model to transform organisations entirely, including departments where the idea of transition them into Agile was considered taboo not so long ago, we are talking about departments as accountancy or HR.
Threats
Failed attempts to remain in waterfall but calling it agile are the main thread as companies don't know what to expect or blame these brainchildren generated by consultancies where the main interest is cashing in.
Agile myths are promoted by people without enough knowledge making teams believe agile means they now do not need to provide any documentation, that everything will emerge by its own, etc.
Replicating old waterfall approaches in agile kills agility. Agile is still very misunderstood, even some of those that promote certain things lack real knowledge on what Agile is about.
