| |
In order to better understand the importance of Scaled Project Management Frameworks, let us first understand a little bit about how they came into being…
Most projects, in the service industry or manufacturing follow standard project methodology- traditional/classical Waterfall which is recommended by the Project Management Institute (PMI). Of course, this is a time tested methodology and depending on details of the industry, this classical approach has been modified in many ways. Then of course there is the Agile way of working…
Probably the most famous methodology that is known within the Agile framework is Scrum. It was made particularly popular by the web and application development groups that needed to react to and incorporate client requirements and feedback in a fast-responsive, iterative approach even while the product (or application) development was underway. But classical Scrum mainly works well for software development.
When it comes to other development efforts, it fails miserably in its effectiveness. The very essential component- “Agility” leads to scope creep, budget overshoots ultimately leading to out-of-control project metrics and dissatisfied clients!!
This led to several scaled frameworks. These came into existence to bridge the gap between classical methodologies mainly Waterfall and Agile to better, more effectively incorporate the best of both these approaches. Scaled frameworks allow for the firm sequencing of steps which ensures that key sign offs happen at crucial stages to encourage stakeholder commitment while allowing for the flexibility of Agile ways of working to incorporate changing client requirements even after a solution has been designed and a development effort is underway.
Scaled Project Frameworks (SPFs) offer a streamlined and effective way of working to service a fluid environment with constantly evolving project work demands. Kanban and Lean-Agile are two of the most used Scaled Project Frameworks (SPFs).
Lean- Scrum heavily utilizes lean principles to enhance Agile-Scrum way of working. Lean-Scrum reduces wasteful steps and processes to increase overall process (methodology) efficiency.
Lean- Kanban on the other hand utilizes efficient Lean methods along with visual signage (Kanban hallmark) and other agile principles.
And then there is the Scaled Waterfall: where we incorporate agile way of incremental working (instead of the traditional phased approach) along with Lean efficiency principles that reduce wasteful steps and ensure high activity-coherence and optimal quality of deliverables.
As we evolve into complex work environments where project mandate changes constantly because of changing user needs, government regulations or simply changing market-feedback analytics, Scaled Project Frameworks will start becoming more of a norm rather than a novel way of Project Management.
Most projects, in the service industry or manufacturing follow standard project methodology- traditional/classical Waterfall which is recommended by the Project Management Institute (PMI). Of course, this is a time tested methodology and depending on details of the industry, this classical approach has been modified in many ways. Then of course there is the Agile way of working…
Probably the most famous methodology that is known within the Agile framework is Scrum. It was made particularly popular by the web and application development groups that needed to react to and incorporate client requirements and feedback in a fast-responsive, iterative approach even while the product (or application) development was underway. But classical Scrum mainly works well for software development.
When it comes to other development efforts, it fails miserably in its effectiveness. The very essential component- “Agility” leads to scope creep, budget overshoots ultimately leading to out-of-control project metrics and dissatisfied clients!!
This led to several scaled frameworks. These came into existence to bridge the gap between classical methodologies mainly Waterfall and Agile to better, more effectively incorporate the best of both these approaches. Scaled frameworks allow for the firm sequencing of steps which ensures that key sign offs happen at crucial stages to encourage stakeholder commitment while allowing for the flexibility of Agile ways of working to incorporate changing client requirements even after a solution has been designed and a development effort is underway.
Scaled Project Frameworks (SPFs) offer a streamlined and effective way of working to service a fluid environment with constantly evolving project work demands. Kanban and Lean-Agile are two of the most used Scaled Project Frameworks (SPFs).
Lean- Scrum heavily utilizes lean principles to enhance Agile-Scrum way of working. Lean-Scrum reduces wasteful steps and processes to increase overall process (methodology) efficiency.
Lean- Kanban on the other hand utilizes efficient Lean methods along with visual signage (Kanban hallmark) and other agile principles.
And then there is the Scaled Waterfall: where we incorporate agile way of incremental working (instead of the traditional phased approach) along with Lean efficiency principles that reduce wasteful steps and ensure high activity-coherence and optimal quality of deliverables.
As we evolve into complex work environments where project mandate changes constantly because of changing user needs, government regulations or simply changing market-feedback analytics, Scaled Project Frameworks will start becoming more of a norm rather than a novel way of Project Management.
#ScaledProjectManagementFramework #LeanKanban #LeanAgile
Sandhya U Bhat MSc, CSSMBB, CSSE has developed several new (under patent filing) and enhanced existing strategic methodologies to improve technology and human capital utilization, produce greater ROI on investments and streamline service delivery. She is an acclaimed author, speaker, a sought after thought leader and an avid world traveler.
