Hybrid represents an infinitely large variety of contexts. It could imply the life cycle (e.g. water-scrum-fall), how individual work streams are managed (e.g. work stream 1 = predictive, work stream 2 = adaptive) or the use of a combination of predictive and adaptive tools and methods (e.g. project charter and WBS along with use of work boards and burn down charts).
As such, you could be on a hybrid project and use NO framework or methodology but rather mix and match roles, tools, artifacts and so on from different frameworks or you could stick with a specific framework for the adaptive work streams and a different one for the predictive ones.
By using a hybrid model, you are picking the best tools for the job, presumably because any one model you can find has shortcomings to what you need to achieve.
Part of that tool selection is justifying to your executives, why they should pay to change what THEY are comfortable doing based on YOUR input.
If they are very logical and take the time to listen, selling a combination of methods based on how well they fit the technical problem is the engineered solution, and my personal favorite. They may even name it after you if it works well.
Executive stakeholders however, typically buy things based on brand appeal. If you have enough personal brand credibility that you can sell your own engineered approach, by all means read up on them all and write your own framework.
More often, you only have enough credibility to sell them something with more brand recognition like SAFe, or Diciplined Agile. You can both explain the rationale as to why it works, and convince the execs that it is a proven approach, which once accepted, you will then tailor to your own engineered solution. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Nikolay,
what is called hybrid is indeed good project management since decades. Does not need any methods or tools labeled agile. But requires a PM and team to select the most appropriate ways to be successful. And to adapt - as humans usually do if something changes. I heard Russians are good at improvising.
Selecting a tool or method includes to consider how well a team can use it. It is not sufficient to use a tool considered best by some, if you cannot apply it to the situation. Saw projects go downhill because of tool and method misuse.
Thomas Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
What does mean hybrid for you? Hybrid is about mixing two life cycles (waterfall and iterative for example) but not what some people call hybrid which is mixing an approach (agile) with a life cycle (waterfall), including it they are confusing waterfall with sequential. So, mixing life cycle is not new. Each time there is a possibility to mixing life cycles it has to be taken to improve the project schedule. Saving Changes...
Peter RapinSubject Matter Expect; Project Delivery| Independent ConsultantOntario, Canada
When people start talking of project management frameworks, models, methodologies or tools I keep going back to Risk Driven Project Delivery. One selects the methods and tools that most effectively mitigate risks and enhance benefits in order to achieve project success. Frameworks, models, methodologies are not one size fits all. Each has their strengths and weaknesses, some are more applicable then the others in specific circumstances, some carry higher risks but promise greater benefits. I would argue that successful projects are delivered through the hybrid approach - pick and choose your methodologies and tools to fit the occasion.
Don't bring the carpenter's tool box to an electrician's party but be prepared to adapt when the wire has to penetrate a 2x4. Saving Changes...
The hybrid approach is a mixture of methodologies and practice, where the practitioner chooses them from a toolkit for tailoring. So he takes the best that fit with uncertainty (agile methodologies) when the stage of the project is within an uncertain environment and other practices that work better with certainty if the context of the project allows use them. There is no cooking recipe because the characteristic of your context varies along with the execution and circumstances. The most successful project use modelling practices that suit well with transition condition.
However, the mindset should drive by principles of value delivery, collaboration, trust environment and searching excellency to continuous improvement. Those values and principles enable to make adaptations, where the changes of methodologies flow easily during the different project stages. Saving Changes...
