Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Mounir, tailoring is "determining the appropiated combination of processes, inputs, tools, techniques, outputs and life cycle prhases to manage a project". After reading the work you post on other comments you participated I think is the same than you are doing. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Sep 17, 2017 10:57 PM
Replying to Morne Beeslaar
...
I would agree the methodologies defined in the PMBOK guide is general and it is up the PM to decide what is applicable and what not. Some IT projects need to be run with Waterfall and others can benefit from Agile. Same applied to any sector that executes projects.
Just a little comment. There are not methodologies or methods defined into the PMBOK Guide. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Just a little comment. I have the opportunity to work from the "genesis" from the academic and practical side. I worked where terms agile and agility were born "formally" (USA DoD NSF/Agility Forum, 1990) and I was part of the group of authors of DSDM (one of the four agile software development methods) where I worked with Arie Van Bennekum who is one of the authors of the Manifesto. Both things were born almost "in parallel". The point was that at the same time the USA Goverment tried to find an innovative answer to Toyota TPS (time after named Lean) and some people that have methods to create software products based on Toyota TPS took some of the ideas from the forum. For those interested into the Agile history here comes a great article written by Heidi Araya https://www.linkedin.com/pulse/when-agile-...e-title-publish I think is interested to know it because when you read this type of things you find new waves to applied Agile. In fact, the ways I am working on from the practical side from more than 20 years ago. Saving Changes...
Anonymous
Sep 18, 2017 5:06 AM
Replying to Sergio Luis Conte
...
Mounir, tailoring is "determining the appropiated combination of processes, inputs, tools, techniques, outputs and life cycle prhases to manage a project". After reading the work you post on other comments you participated I think is the same than you are doing.
Hi Sergio
I read the section on tailoring in Part 2 --- although it is good to see the PMBOK Guide emphasizing this topic instead of burying it in the text; it is not what I am doing; similar, but not the same.
The issue I have with the PMBOK Guide, in relation to this point and others, is that it gives an impression that the PM has a lot of power, more so than the organizational processes. I know this is not the intent but it is how it is understood by numerous people we engaged in discussions.
I am a believer in the SYSTEM (like you used in a different post) - SYSTEM as in the organizational project management system. CAMMP is about tailoring the system and developing standardized tailored methods. In other words, most of the tailoring should be done in the OPMS or what the PMBOK Guide calls OPA.
Then, when it comes to managing a given project, there might be a need for more tailoring; what I prefer to call "tweaking" or minor tailoring. If a PM thinks there is major tailoring required, then the PM and PMT must go back to the owner of the OPMS with recommendations and justifications.
Unfortunately, in the absence of OPMS (OPA), project managers end up having to define the method they want to use, the Project Life Cycle, and other processes. I am all for empowerment but this it goes beyond empowerment and in low PM Maturity organizations this is a recipe for project failure.
...
1 reply by Sergio Luis Conte
Sep 18, 2017 10:21 AM
Sergio Luis Conte
...
Fully agree with you Mounir. I had lot of discussions but as you know I am one more between other people. And in my case, I am a South American Indian (hehehehe. But I have to say they respect me). I am not confortable with the results. The thing that we got is to add a table where there is a difference between project/programs/portfolios. The point in all this new wave of viewing things and new role focus (business analyst) is: to select the process to create something is an strategical matter so it belongs to business analysis field. If you notice new things have been added related to process like Stage Gate. Then, to select the process is located (I hope, I do not know the final result) inside the Business Analysis Guide in the process named "Needs Assessment". Other point is the inclusion of a description of "Business Documents" and more specific "Project Business Case". That is the place (if you follow the recommendation of the PMI) where the life cycle is stated.
Saving Changes...
Anonymous
Sep 18, 2017 5:07 AM
Replying to Sergio Luis Conte
...
Just a little comment. There are not methodologies or methods defined into the PMBOK Guide.
Agree with Sergio
Some approaches or methods are mentioned but not defined in the PMBOK Guide. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Fully agree with you Mounir. I had lot of discussions but as you know I am one more between other people. And in my case, I am a South American Indian (hehehehe. But I have to say they respect me). I am not confortable with the results. The thing that we got is to add a table where there is a difference between project/programs/portfolios. The point in all this new wave of viewing things and new role focus (business analyst) is: to select the process to create something is an strategical matter so it belongs to business analysis field. If you notice new things have been added related to process like Stage Gate. Then, to select the process is located (I hope, I do not know the final result) inside the Business Analysis Guide in the process named "Needs Assessment". Other point is the inclusion of a description of "Business Documents" and more specific "Project Business Case". That is the place (if you follow the recommendation of the PMI) where the life cycle is stated. Saving Changes...
Anonymous
Sep 18, 2017 10:21 AM
Replying to Sergio Luis Conte
...
Fully agree with you Mounir. I had lot of discussions but as you know I am one more between other people. And in my case, I am a South American Indian (hehehehe. But I have to say they respect me). I am not confortable with the results. The thing that we got is to add a table where there is a difference between project/programs/portfolios. The point in all this new wave of viewing things and new role focus (business analyst) is: to select the process to create something is an strategical matter so it belongs to business analysis field. If you notice new things have been added related to process like Stage Gate. Then, to select the process is located (I hope, I do not know the final result) inside the Business Analysis Guide in the process named "Needs Assessment". Other point is the inclusion of a description of "Business Documents" and more specific "Project Business Case". That is the place (if you follow the recommendation of the PMI) where the life cycle is stated.
Appreciate your effort Sergio; I know how difficult it can be. I know there are serious issues identified years ago but unfortunately not much is done about them. I do not know if it is PMI or "the consensus" :)
Anyway, I am going through all of the details and blogging about them. I just did a post on Tailoring - the issue at hand but not ready to publish it yet.
Take care my friend
...
1 reply by Sergio Luis Conte
Sep 18, 2017 1:55 PM
Sergio Luis Conte
...
From my side, I am writting a series of articles named "understanding the new PMBOK Guide". The focus is not about the new items. The focus is about how to understand the new items because they are related each other with other guides. In parallel, I will perform a series of workshops inside the PMI Buenos Aires Chapter. Why I do that? Because it is a problem for me when other people create "noise" in our profession due to some of those people talk without understanding about what they are talking about. I will participate on your topic too.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
From my side, I am writting a series of articles named "understanding the new PMBOK Guide". The focus is not about the new items. The focus is about how to understand the new items because they are related each other with other guides. In parallel, I will perform a series of workshops inside the PMI Buenos Aires Chapter. Why I do that? Because it is a problem for me when other people create "noise" in our profession due to some of those people talk without understanding about what they are talking about. I will participate on your topic too. Saving Changes...
