Baddar RehmaniSenior Project Manager| Ufone - PTML (Pak Telecom Mobile Limited)Islamabad, Federal Capital, Pakistan
Hi, I have a question to PM gurus.
As per PMI's PMBoK 6th Edition,in "Project Quality Management" knowledge area and specifically in "Manage Quality" process, there is an output called "Test and Evaluation Documents". This output, as per my understanding, contains QC checklist and relevant documents but this output should be taken from "Plan Quality Management" process and I am not getting its logic coming out from "Manage Quality" process.
Can someone shed some light on this as I might not be comprehending it the way it is. Thanks.
//
Regards,
Baddar Muneer, PMP Saving Changes...
Actually I have the exact same concern , it seems to me as an input manage quality for the purpose of process improvement not the other way around.
Also,I think it is mentioned in the Plan quality management that the sheets are planned during planning. Saving Changes...
I would start out by saying that process groups can be organized in many ways, and I'm sure there was a fair amount of spirited discussion on how to organize them in the PMBOK. There are certainly a lot of questions regarding them, and I had a difficult time rationalizing how some processes fit where they do myself as well.
With respect to T&E Docs, determining what documents are required and by whom is part of planning. The output of the quality process however is the documentation of the T&E results.
For example, I manage test activities on a program introducing various hardware and software changes aligned to blockpoints (structured iterations of configuration changes). During the planning phase, changes are aligned to blockpoints dictating who must provide quality documentation. The program determines what documentation is required based on the nature of the changes, and the design teams plan what specific tests to run or evaluation to perform. All of that is planning.
Once the plan is established, management covers execution of the detail level plans up through and including release of the quality deliverables. Schedules may change for individual tests. Dependencies between different groups with interfacing HW/SW must be maintained. Testing may reveal bugs which drive additional T&E. Output documents must be written and approved. All of that is managing quality based on the plan.
I hope that helps.
...
1 reply by Hisham Osman
May 13, 2021 12:34 PM
Hisham Osman
...
Thanks,does that mean that additional tailoring for test scripts is expected in execution without iterating back to planning?
I would start out by saying that process groups can be organized in many ways, and I'm sure there was a fair amount of spirited discussion on how to organize them in the PMBOK. There are certainly a lot of questions regarding them, and I had a difficult time rationalizing how some processes fit where they do myself as well.
With respect to T&E Docs, determining what documents are required and by whom is part of planning. The output of the quality process however is the documentation of the T&E results.
For example, I manage test activities on a program introducing various hardware and software changes aligned to blockpoints (structured iterations of configuration changes). During the planning phase, changes are aligned to blockpoints dictating who must provide quality documentation. The program determines what documentation is required based on the nature of the changes, and the design teams plan what specific tests to run or evaluation to perform. All of that is planning.
Once the plan is established, management covers execution of the detail level plans up through and including release of the quality deliverables. Schedules may change for individual tests. Dependencies between different groups with interfacing HW/SW must be maintained. Testing may reveal bugs which drive additional T&E. Output documents must be written and approved. All of that is managing quality based on the plan.
I hope that helps.
Thanks,does that mean that additional tailoring for test scripts is expected in execution without iterating back to planning?
...
1 reply by Keith Novak
May 13, 2021 1:56 PM
Keith Novak
...
No, re-planning is still planning. Remember that the process groups are not sequential, and are often occurring simultaneously. It's really just an organizational structure to collect like types of processes. You're not going *back* to planning, but rather as part of the execution, you learn you must do more planning.
Even in development models which are largely predictive and linear, there are always rework loops, because we learn more information along the way. If you look at the Systems Engineering "Vee" model where planning/validation occurs largely on the left side and execution/verification on the right, at each layer of system development, there are feedback loops.
Thanks,does that mean that additional tailoring for test scripts is expected in execution without iterating back to planning?
No, re-planning is still planning. Remember that the process groups are not sequential, and are often occurring simultaneously. It's really just an organizational structure to collect like types of processes. You're not going *back* to planning, but rather as part of the execution, you learn you must do more planning.
Even in development models which are largely predictive and linear, there are always rework loops, because we learn more information along the way. If you look at the Systems Engineering "Vee" model where planning/validation occurs largely on the left side and execution/verification on the right, at each layer of system development, there are feedback loops. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
One of the key changes in this version of PMBOK is the division between Project Management Plan documents and Project Documents. Project Documents contains work performance data and they are considered Organizational Process Assets (OPAs). Inside OPAs, Project Documents are considered templates to support organization’s processes and procedures for conducting project work. So, they can or cannot being part of the Plan´s documents. The idea is not, in the plan is just a reference about the Project Document to be used for running a particular process. In the line of thinking of the PMI, during Manage Quality what to do is taking the Project Management Plan (the Quality Management Plan is part of it) and taking the needed OPAs (Test and Evaluation Document is a template inside them) and creating all the test and evaluation artifacts needed to perform Quality Control activities. Inside the artifacts is the Test and Evaluation Document filled with all needed. What the PMI tried to do is to put on the table that Manage Quality scope is boarder than quality assurance (quality assurance is on process only) while it includes it. Just for the PMI line of thinking. Just to comment, when this version of the PMBOK was create, there was a lot of debate about this change. Saving Changes...
Community Champion
