Project Management

Project Management Central

Please login or join to subscribe to this thread

Product delivery in hybrid organizations.
Agile project management has progressively spread, however, most companies don’t use the Classic (Waterfall) or Agile approach exclusively. They create or try to create their own blend of Hybrid methodologies. I wonder if you faced product failure due to complication in mixing approaches and how did you manage the situation?
Sort By:
@Anna. One of the problems is there is a lot of confusion outside there. Lean, Agile, Six Sigma, etc are approaches that must be implemented taken into account the whole organization as a system. Those approaches can be used to put strategy in practice and strategy, while it could be one for the whole organization, usually depends on the market where the organization is playing and the product/service/result to deliver. Organizations are playing in more than one market usually. Let me a comment just to pointed out my level of involvement in my last assignment. I was in charge to lead my actual world place transformation mainly for going to be an agile enterprise. To do that, it is important to think in a pyramid where in the basement you have the approach (Lean, Agile, etc), on top of it the life cycle to support the approach (waterfall, iterative, iterative-incremental, V, etc), on top of it the method/approach to support the life cycle (SDLC, Scrum, DSDM, V, etc) and on top of it the tool. All composes an architectural view with high cohesion and low coupling between layers. Then, you can use agile with waterfall life cycle without problem. In my actual work place, we are using Lean and Agile and to support it we are using different defined life cycles. The problem is not what you use. The problem is most of the companies do not make the key activity of understanding the current situation and the situation to reach with focus on the solution to create taking into account the organization is an open and adaptative system.
Product failure is not due to the use or misuse of adaptive or predictive approaches. Products fail because of a lack of management. We've put a lot of emphasis on managing project. Adaptive approaches are highlighting the importance of product management.

Product management lives before and after the project. If you don't have a permanent product owner and product manager, you can expect difficulties and issues.
Anna -

The failure occurs when the wrong approach, life cycle, tools or techniques are used for a given project's context. Lower maturity organizations will take a one size fits all approach to standards whereas more mature ones will focus on principles and control/delivery objectives but let the specific "how" be defined by the team with guidance from coaches, communities of practice or from established bodies of knowledge.


for me it was always important to chose the appropriate approach for the specific project situation. Depends on many factors, like company culture, available competencies, newness of the product. Available competencies is important, as if you have much experience with one approach, you will not be capable to be as effective with another one you have no experience yet.

So I do not see a limitation on waterfall and agile, but a wide range of possible ways of working. OIt goes way beyond of what is understood as hybrid. Discipled Agile can give a hint on how to select your way of working, though even it is very biased towards agile concepts.


Please login or join to reply

Content ID:

People on dates shouldn't even be allowed out in public.

- Jerry Seinfeld