I read this webpage while researching an article (regarding PMP chages) for my blog. It says "The Agile Practice Guide, which was created in partnership with the Agile Alliance®, is a fitting companion to the PMBOK® Guide – Sixth Edition and is intended to serve as a bridge to connect waterfall and agile approaches."
I would like to understand from the experts - Was PMBOK Guide ever based on "waterfall approach"? I may be wrong here but as far as I understand, PMBOK Guide processes can be applied to any PM approach and/or lifecycle.
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I was part of the group of authors and reviewers. Between the PMBOK and the Agile Guide there is a hugh gap. Just read PMBOK Guide chapters 1-4 and the Agile Practice Guide and you will understand my point (in fact you will find into the Agile Guide and example related to pharmacy that was provided by me). The problem is the Agile Guide was not published for public review. And it was created with the Agile Alliance that is fully software focused. In fact, the Agile Guide relates Agile with the Manifesto and that is totally incorrect. In fact, for a reason the word "software" is used into the name of the Manifesto. First mistake is: Agile and Waterfall are not matter of comparison. Agile is a practice or discipline. Waterfall is a life cycle process. In fact, you can apply Agile using waterfall life cycle process.
...
2 replies by Kevin Drake and Praveen Malik
May 07, 2018 6:52 PM
Kevin Drake
...
Thanks Sergio
May 13, 2018 1:13 AM
Praveen Malik
...
Thanks for your reply.
I just wanted to know if this statement from PMI "Sixth Edition and is intended to serve as a bridge to connect waterfall and agile approaches." correct?
PMBOK Guide processes can be applied globally to any practice/lifecycle/approach. What is your opinion?
I'd agree that the PMBOK itself is approach neutral, but the PMBOK Guide till the current edition did not cover specific practices or considerations when utilizing an adaptive lifecycle and even though the inputs and outputs of processes were not defined as being documents and the processes themselves are iterative in natural, the "mainstream" perception was that the Guide was tied to a traditional deterministic approach.
Kiron
...
1 reply by Praveen Malik
May 13, 2018 1:26 AM
Praveen Malik
...
Thanks Kiron. You are in saying "the "mainstream" perception was that the Guide was tied to a traditional deterministic approach". But does that "mainstream" include PMI itself?
PMI presents the PMPBOK Guide as Standards & Guidelines for Project Management. PMBOK Guide processes were never based on a specific approach and even the first ed processes can be applied as an agile approach.
In my opinion, PMI' statement "Sixth Edition and is intended to serve as a bridge to connect waterfall and agile approaches." is redundant and borderline incorrect.
Although I am very new to this, I don't like the idea of processes being explained as a "waterfall" in approach. Although it describes processes in a more downward motion, I don't see it very likely with majority of projects to occur that way.
Although you wouldn't use all 49 processes within the steps taken for a project, it seems more realistic that within each process applying to the process groups, you can always go back and forth between them. This can also jump between processes within the 10 knowledge areas of a project.
So for instance if you notice there's a cost issue during the monitoring phase where you would control your costs, you would then be likely to go back to the planning phase to check on your budgets or cost plan based on the problem.
Waterfall describes everything flowing downward and I don't think real life is that way. Especially within the iron triangle, I would assume that you would always have a means to go back and forth between the flow of processes at some point within the project.
Hopefully I made some relevant sense in what I am saying.
Maybe the experts can also chime in on why the term "waterfall" and is it more general or specific to a certain factor within PM work? The term to me is like bouncing a ball on the ground expecting it to not come back up - it doesn't make much sense. Processes seem related to one another and the pathways of how they come together within a project some to go 2 ways, all interconnected.
...
1 reply by Praveen Malik
May 13, 2018 1:31 AM
Praveen Malik
...
Than Michael, What do you think of PMI's statement "Sixth Edition and is intended to serve as a bridge to connect waterfall and agile approaches."?
I was part of the group of authors and reviewers. Between the PMBOK and the Agile Guide there is a hugh gap. Just read PMBOK Guide chapters 1-4 and the Agile Practice Guide and you will understand my point (in fact you will find into the Agile Guide and example related to pharmacy that was provided by me). The problem is the Agile Guide was not published for public review. And it was created with the Agile Alliance that is fully software focused. In fact, the Agile Guide relates Agile with the Manifesto and that is totally incorrect. In fact, for a reason the word "software" is used into the name of the Manifesto. First mistake is: Agile and Waterfall are not matter of comparison. Agile is a practice or discipline. Waterfall is a life cycle process. In fact, you can apply Agile using waterfall life cycle process.
Thanks Sergio Saving Changes...
Praveen MalikIndependent Consultant| Independent ConsultantNew Delhi, India
May 05, 2018 6:10 PM
Replying to Sergio Luis Conte
...
I was part of the group of authors and reviewers. Between the PMBOK and the Agile Guide there is a hugh gap. Just read PMBOK Guide chapters 1-4 and the Agile Practice Guide and you will understand my point (in fact you will find into the Agile Guide and example related to pharmacy that was provided by me). The problem is the Agile Guide was not published for public review. And it was created with the Agile Alliance that is fully software focused. In fact, the Agile Guide relates Agile with the Manifesto and that is totally incorrect. In fact, for a reason the word "software" is used into the name of the Manifesto. First mistake is: Agile and Waterfall are not matter of comparison. Agile is a practice or discipline. Waterfall is a life cycle process. In fact, you can apply Agile using waterfall life cycle process.
Thanks for your reply.
I just wanted to know if this statement from PMI "Sixth Edition and is intended to serve as a bridge to connect waterfall and agile approaches." correct?
PMBOK Guide processes can be applied globally to any practice/lifecycle/approach. What is your opinion?
...
1 reply by Sergio Luis Conte
May 14, 2018 1:04 PM
Sergio Luis Conte
...
Is totally wrong because waterfall and agile are not matter of comparison, is like to compare apples with bananas. I wrote about that in my previous statement. You can apply Agile using waterfall life cycle process (we are doing that in my actual work place and it was one of my duties to work on that defining how to do that). On the other the PMBOK Guide is full compatible with all the well known agile based methods.Just the only thing perhaps you changes are tools listed on the PMBOK but the PMBOK do not stated that you have to use the tools listed inside it or nothing. In fact, just to add some kind of information about I am totally committed to that, let me say I have performed conferences inside the PMI World Tour in lot of countries from 2010 explaining that. So, there is not brigde at all because there is no sense. For example, in my actual work place, the same person is assigned as project manager to more than one initiative at the same time and those initiatives are based on different approaches (Agile with our own process, Scrum, SDLC, etc)
Saving Changes...
Praveen MalikIndependent Consultant| Independent ConsultantNew Delhi, India
May 06, 2018 10:02 AM
Replying to Kiron Bondale
...
Praveen -
I'd agree that the PMBOK itself is approach neutral, but the PMBOK Guide till the current edition did not cover specific practices or considerations when utilizing an adaptive lifecycle and even though the inputs and outputs of processes were not defined as being documents and the processes themselves are iterative in natural, the "mainstream" perception was that the Guide was tied to a traditional deterministic approach.
Kiron
Thanks Kiron. You are in saying "the "mainstream" perception was that the Guide was tied to a traditional deterministic approach". But does that "mainstream" include PMI itself?
PMI presents the PMPBOK Guide as Standards & Guidelines for Project Management. PMBOK Guide processes were never based on a specific approach and even the first ed processes can be applied as an agile approach.
In my opinion, PMI' statement "Sixth Edition and is intended to serve as a bridge to connect waterfall and agile approaches." is redundant and borderline incorrect.
...
1 reply by Kiron Bondale
May 14, 2018 5:52 PM
Kiron Bondale
...
Praveen -
I believe the "bridge" reference relates to the addition of the considerations for adaptive lifecycle projects sections in each knowledge area chapter.
Kiron
Saving Changes...
Praveen MalikIndependent Consultant| Independent ConsultantNew Delhi, India
May 07, 2018 2:47 PM
Replying to Michael Brian
...
Although I am very new to this, I don't like the idea of processes being explained as a "waterfall" in approach. Although it describes processes in a more downward motion, I don't see it very likely with majority of projects to occur that way.
Although you wouldn't use all 49 processes within the steps taken for a project, it seems more realistic that within each process applying to the process groups, you can always go back and forth between them. This can also jump between processes within the 10 knowledge areas of a project.
So for instance if you notice there's a cost issue during the monitoring phase where you would control your costs, you would then be likely to go back to the planning phase to check on your budgets or cost plan based on the problem.
Waterfall describes everything flowing downward and I don't think real life is that way. Especially within the iron triangle, I would assume that you would always have a means to go back and forth between the flow of processes at some point within the project.
Hopefully I made some relevant sense in what I am saying.
Maybe the experts can also chime in on why the term "waterfall" and is it more general or specific to a certain factor within PM work? The term to me is like bouncing a ball on the ground expecting it to not come back up - it doesn't make much sense. Processes seem related to one another and the pathways of how they come together within a project some to go 2 ways, all interconnected.
Than Michael, What do you think of PMI's statement "Sixth Edition and is intended to serve as a bridge to connect waterfall and agile approaches."?
...
1 reply by Michael Brian
May 14, 2018 12:26 PM
Michael Brian
...
I think the statement is true for particular applications such as projects within construction. Here a waterfall approach seems fitting and agile makes sense. In such a project you want high value, high quality work. Adding an agile method makes sense as it allows you to focus on each section of building in a waterfall methodology to ensure that every step created has high value and quality. It can allow you to limit risks by applying such focus based actions in a smaller chunk of time verses stretching a project where scope creep or other risks can find their way in.
Sort of like studying... Studying something for 1.5 hours and barely retaining any information is worthless compared to focused and attentive study for 30 minutes with more information retained.
There’s many methodologies to utilize and if the masses of project involve a waterfall approach than adding agile methods would be a positive consideration.
As I have not touched on agile methods and still early in my learning, I can imagine this method increases the potential risk or consequences within these sprints of work being done. I think quality, cost, and scope monitoring would be a huge factor to maintains a single oversight can throw things off and since agile approaches tend to speed things up with more focus demand, everyone involved needs to be present at all times in their actions. But I do think agile method does help to eliminate distractions when sticking with a schedule. To focus on each piece of the puzzle can definitely bring higher quality work to the project.
Than Michael, What do you think of PMI's statement "Sixth Edition and is intended to serve as a bridge to connect waterfall and agile approaches."?
I think the statement is true for particular applications such as projects within construction. Here a waterfall approach seems fitting and agile makes sense. In such a project you want high value, high quality work. Adding an agile method makes sense as it allows you to focus on each section of building in a waterfall methodology to ensure that every step created has high value and quality. It can allow you to limit risks by applying such focus based actions in a smaller chunk of time verses stretching a project where scope creep or other risks can find their way in.
Sort of like studying... Studying something for 1.5 hours and barely retaining any information is worthless compared to focused and attentive study for 30 minutes with more information retained.
There’s many methodologies to utilize and if the masses of project involve a waterfall approach than adding agile methods would be a positive consideration.
As I have not touched on agile methods and still early in my learning, I can imagine this method increases the potential risk or consequences within these sprints of work being done. I think quality, cost, and scope monitoring would be a huge factor to maintains a single oversight can throw things off and since agile approaches tend to speed things up with more focus demand, everyone involved needs to be present at all times in their actions. But I do think agile method does help to eliminate distractions when sticking with a schedule. To focus on each piece of the puzzle can definitely bring higher quality work to the project.
...
1 reply by Praveen Malik
May 18, 2018 3:11 AM
Praveen Malik
...
Thank again. Why do you think earlier PMBOK Guide processes cannot be applied to an agile lifecycle?
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
May 13, 2018 1:13 AM
Replying to Praveen Malik
...
Thanks for your reply.
I just wanted to know if this statement from PMI "Sixth Edition and is intended to serve as a bridge to connect waterfall and agile approaches." correct?
PMBOK Guide processes can be applied globally to any practice/lifecycle/approach. What is your opinion?
Is totally wrong because waterfall and agile are not matter of comparison, is like to compare apples with bananas. I wrote about that in my previous statement. You can apply Agile using waterfall life cycle process (we are doing that in my actual work place and it was one of my duties to work on that defining how to do that). On the other the PMBOK Guide is full compatible with all the well known agile based methods.Just the only thing perhaps you changes are tools listed on the PMBOK but the PMBOK do not stated that you have to use the tools listed inside it or nothing. In fact, just to add some kind of information about I am totally committed to that, let me say I have performed conferences inside the PMI World Tour in lot of countries from 2010 explaining that. So, there is not brigde at all because there is no sense. For example, in my actual work place, the same person is assigned as project manager to more than one initiative at the same time and those initiatives are based on different approaches (Agile with our own process, Scrum, SDLC, etc) Saving Changes...
Thanks Kiron. You are in saying "the "mainstream" perception was that the Guide was tied to a traditional deterministic approach". But does that "mainstream" include PMI itself?
PMI presents the PMPBOK Guide as Standards & Guidelines for Project Management. PMBOK Guide processes were never based on a specific approach and even the first ed processes can be applied as an agile approach.
In my opinion, PMI' statement "Sixth Edition and is intended to serve as a bridge to connect waterfall and agile approaches." is redundant and borderline incorrect.
Praveen -
I believe the "bridge" reference relates to the addition of the considerations for adaptive lifecycle projects sections in each knowledge area chapter.
Kiron
...
1 reply by Praveen Malik
May 18, 2018 3:19 AM
Praveen Malik
...
Thanks again.
The basic theme of the processes between PMBOK Guide 5th (and previous editions also) and 6th ed has not changed. They have added 1-2 paras describing agile in each KA.
On the contrary the statement at PMI's website refers to the Agile practice guide and PMBOK Guide 6th ed. Here it is again - "The Agile Practice Guide, which was created in partnership with the Agile Alliance®, is a fitting companion to the PMBOK® Guide – Sixth Edition and is intended to serve as a bridge to connect waterfall and agile approaches."
A "bridge" is required only if there is a "chasm". Like you said in your previous comment that PMBOK Guide is approach neutral.