Project Management

Please login or join to subscribe to this thread

Create a new development approach to projects

linkedin twitter facebook   Change Management   Innovation   Organizational Project Management  
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
When I heard an interview with Roger L. Martin, in "Creating Great Choices" an idea occurred to me:
1. Take the waterfall development model and take it to the extreme
2. Take agile development models and take them to the extreme
3. Throw away what doesn't work
4. Build a model that is the fusion of what was not rejected in the two models

What do you think of this idea? (I'm not saying it's original)
Sort By:
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Luis -

When you say "throw away what doesn't work", do you mean throw away the elements which are inappropriate for a given project's context? Otherwise, all you'll end up with is a set of principles or guidelines similar to the DA mindset or the principles in the PMBOK Guide, Seventh Edition?

Kiron
...
1 reply by Luis Branco
Dec 22, 2021 3:37 PM
Luis Branco
...
Dear Kiron. Very interesting your question.
When we talk about projects and project management, can everything be reduced to the principles contained in the guides?
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
Dec 22, 2021 3:32 PM
Replying to Kiron Bondale
...
Luis -

When you say "throw away what doesn't work", do you mean throw away the elements which are inappropriate for a given project's context? Otherwise, all you'll end up with is a set of principles or guidelines similar to the DA mindset or the principles in the PMBOK Guide, Seventh Edition?

Kiron
Dear Kiron. Very interesting your question.
When we talk about projects and project management, can everything be reduced to the principles contained in the guides?
...
1 reply by Kiron Bondale
Dec 22, 2021 7:00 PM
Kiron Bondale
...
Without getting into specific practices, method, tools, life cycles or roles which are all context specific, what we are left with are "mindset" elements such as the DA principles, promises & guidelines. This is not to say that the ones listed in Choose Your WoW and the PMBOK Guide are exhaustive - there might be many more...

Kiron
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Dec 22, 2021 3:37 PM
Replying to Luis Branco
...
Dear Kiron. Very interesting your question.
When we talk about projects and project management, can everything be reduced to the principles contained in the guides?
Without getting into specific practices, method, tools, life cycles or roles which are all context specific, what we are left with are "mindset" elements such as the DA principles, promises & guidelines. This is not to say that the ones listed in Choose Your WoW and the PMBOK Guide are exhaustive - there might be many more...

Kiron
avatar
Abolfazl Yousefi Darestani Manager, Quality and Continuous Improvement| Hörmann-TNR Industrial Doors Newmarket, Ontario, Canada
It seems good. However, it may or may not apply. Case by case analysis needs to be done.
avatar
Peter Rapin Subject Matter Expect; Project Delivery| Independent Consultant Ontario, Canada
Ideally one would develop the best model (methodology/process/procedure ) for a specific project's needs borrowing from whatever is available in the various published models. In reality we are constrained to the model that the employer/client dictates or failing that, the one what we are personally familiar and comfortable with. Then we adjust to fit the project needs mostly on-the-fly. The rationalization for this approach is the we don't want to re-invent the wheel every time we go for a ride. The down side is that the wheel is not always the right or best answer.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
To develop a model people have to think in a pyramid. In the basement, the approach (Lean, Agile, etc), over the basement the life cycle process (waterfall, iterative, incremental, iterative-incremental, V, Spiral, etc), over the life cycle process the method (existing or your own), over the method the tools (where tools is everything that helps to implement all the other). All these stuff has to be made after performing, to put it in terms of business analysis, enteprise analisys. So, nothing new below the sun. All needed for doing this type of things can be find into business analisys related literature that belongs to the IIBA or the PMI (IIBA was the pioneer). I encourage people to take a closer look to Tom Gilb´s EVO and Martin Fowler / James Coplien on enterprise patters. No matter the first versions were for software it can be applied (and it was applied) to multiple domains.
avatar
Eduard Hernandez
Community Champion
Product Operations Program Manager Barcelona, Cataluña, Spain
Don't we do this to some extent already? Frameworks provide a playing ground, and it is down to the intrinsic and extrinsic project characteristics that the "model" is conveniently customized to maximize the delivered value.

In other words, "one size does not fit all".

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Without question, the greatest invention in the history of mankind is beer. Oh, I grant you that the wheel was also a fine invention, but the wheel does not go nearly as well with pizza."

- Dave Barry

ADVERTISEMENT

Sponsors