To the PMP community, I request your support to clarify concepts or definitions of requirement, deliverable and criterion of acceptance, at what time you can talk about one or the other and their rel
Juan Carlos Cruz VegaSUBDIRECTOR DE PROYECTOS ESTRATEGICOS PMP®, SMC™, ITIL®| PGR / COPLADIIMéxico, D.F., Mexico
If I want to develop a pen this is my final product, which would be the requirements and acceptance criteria? and at what time they apply?, eg are recorded in the project constitution, the project plan or the traceability matrix...
I appreciate your support and mentoring. Saving Changes...
So, you want to develop a pen. At the highest level, you can state:
"I need a pen that writes in black and can be erased"
It is a high-level requirement in can be stated in the Project Charter during the project Initiation.
Later during the Planning phase, you will elaborate on more detailed requirements of the pen. For example:
- The Pen should be able to write 10000 words.
- The pan should have a soft touch body,
- The pan should retract and hide the tip with a button.
These requirements will go into the Requirement Traceability Matrix.
Acceptance Criteria can be stated in WBS Dictionary, RTM, or Quality documentation.
It may say something like: "I will know the requirement of 1000 words is meat when QA team performs testing of 100 pens on different types of paper."
Requirements and acceptance criteria are developed during project planning.
Please let me know if this answers your question.
...
2 replies by Anupam and Juan Carlos Cruz Vega
May 11, 2017 10:33 AM
Juan Carlos Cruz Vega
...
Thanks Mr. Nizhebetskiy, it was very illustrative and clear his example, which has helped me close a breach of definitions.
Regards.
May 17, 2017 9:02 PM
Anupam
...
Agree.
The requirements are test cases for QA.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
My recommendation is going to the BOK`s Glossary of Terms and the Lexicom, both PMI`s documents. Is the best way to avoid any type of subjetive interpretations. I could write a lot about that because is my field of research and practices mainly because my involvement with business analysis and project management working with the PMI and the IIBA, but I encourage you going to the definitons inside the documents.
...
1 reply by Juan Carlos Cruz Vega
May 11, 2017 2:12 PM
Juan Carlos Cruz Vega
...
Thanks Mr. Conte, reviewing the definitions of the BoK was the first thing I did, my problem was in practice what is the difference between a requirement and an acceptance criterion,
My requirement was to develop a pen, which would paint blue. so; My requirement is a blue ink pen, but my acceptance criterion is that after the feathers have been developed, it is verified in QA that the blue ink complies with a blue color range from pattern A to B say that the density of the stroke Whether of x millimeters,
Saving Changes...
Seema SonkiyaHead Business Analysis Practices, PMI-PBA trainer| iZenBridge Consultancy Private LimitedJaipur, Rajasthan, India
I agree with Dmitriy, just to add, User stories and acceptance criteria need the involvement of all relevant people who can contribute in exploring needs. Acceptance crietria are designed as per users needs.
...
1 reply by Juan Carlos Cruz Vega
May 11, 2017 2:22 PM
Juan Carlos Cruz Vega
...
Many thanks, Miss Sonkiya, the link you have given me tells me that if there is a confusion of terms or definition and that until we are in need of explaining the point to someone else is when we have to have clear concepts we use Everyday
Saving Changes...
Juan Carlos Cruz VegaSUBDIRECTOR DE PROYECTOS ESTRATEGICOS PMP®, SMC™, ITIL®| PGR / COPLADIIMéxico, D.F., Mexico
May 11, 2017 6:47 AM
Replying to Dmitriy Nizhebetskiy
...
So, you want to develop a pen. At the highest level, you can state:
"I need a pen that writes in black and can be erased"
It is a high-level requirement in can be stated in the Project Charter during the project Initiation.
Later during the Planning phase, you will elaborate on more detailed requirements of the pen. For example:
- The Pen should be able to write 10000 words.
- The pan should have a soft touch body,
- The pan should retract and hide the tip with a button.
These requirements will go into the Requirement Traceability Matrix.
Acceptance Criteria can be stated in WBS Dictionary, RTM, or Quality documentation.
It may say something like: "I will know the requirement of 1000 words is meat when QA team performs testing of 100 pens on different types of paper."
Requirements and acceptance criteria are developed during project planning.
Please let me know if this answers your question.
Thanks Mr. Nizhebetskiy, it was very illustrative and clear his example, which has helped me close a breach of definitions.
Regards. Saving Changes...
Juan Carlos Cruz VegaSUBDIRECTOR DE PROYECTOS ESTRATEGICOS PMP®, SMC™, ITIL®| PGR / COPLADIIMéxico, D.F., Mexico
May 11, 2017 8:17 AM
Replying to Sergio Luis Conte
...
My recommendation is going to the BOK`s Glossary of Terms and the Lexicom, both PMI`s documents. Is the best way to avoid any type of subjetive interpretations. I could write a lot about that because is my field of research and practices mainly because my involvement with business analysis and project management working with the PMI and the IIBA, but I encourage you going to the definitons inside the documents.
Thanks Mr. Conte, reviewing the definitions of the BoK was the first thing I did, my problem was in practice what is the difference between a requirement and an acceptance criterion,
My requirement was to develop a pen, which would paint blue. so; My requirement is a blue ink pen, but my acceptance criterion is that after the feathers have been developed, it is verified in QA that the blue ink complies with a blue color range from pattern A to B say that the density of the stroke Whether of x millimeters,
...
1 reply by Sergio Luis Conte
May 11, 2017 4:26 PM
Sergio Luis Conte
...
Well, take into account that theare two types of requirements: product requirements and project requitements. Project manager is in charge of project requirements. So, product requirements and acceptance criteria is outside your scope as project manager. The business analyst is accountable for that. The only thing you must do is to define project requirements from product requirements. In this case, you must define what quality activities you have to consider to get the deliverables approval. So, acceptance criteria is needed to perform quality control activities BUT once again, the business analyst msut define it. Acceptance criteria is composed by two parts; the criteria and the process to achive the criteria. Suppose you have to create a light bulb and one of the non-functional requirements is a 100 hours duration. Then the criteria could be "light bulb must remain in operation along 100 hours" and the process could be "turn the light bulb on and off along more than 100 hours".
Saving Changes...
Juan Carlos Cruz VegaSUBDIRECTOR DE PROYECTOS ESTRATEGICOS PMP®, SMC™, ITIL®| PGR / COPLADIIMéxico, D.F., Mexico
May 11, 2017 8:32 AM
Replying to Seema Sonkiya
...
I agree with Dmitriy, just to add, User stories and acceptance criteria need the involvement of all relevant people who can contribute in exploring needs. Acceptance crietria are designed as per users needs.
Many thanks, Miss Sonkiya, the link you have given me tells me that if there is a confusion of terms or definition and that until we are in need of explaining the point to someone else is when we have to have clear concepts we use Everyday Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
May 11, 2017 2:12 PM
Replying to Juan Carlos Cruz Vega
...
Thanks Mr. Conte, reviewing the definitions of the BoK was the first thing I did, my problem was in practice what is the difference between a requirement and an acceptance criterion,
My requirement was to develop a pen, which would paint blue. so; My requirement is a blue ink pen, but my acceptance criterion is that after the feathers have been developed, it is verified in QA that the blue ink complies with a blue color range from pattern A to B say that the density of the stroke Whether of x millimeters,
Well, take into account that theare two types of requirements: product requirements and project requitements. Project manager is in charge of project requirements. So, product requirements and acceptance criteria is outside your scope as project manager. The business analyst is accountable for that. The only thing you must do is to define project requirements from product requirements. In this case, you must define what quality activities you have to consider to get the deliverables approval. So, acceptance criteria is needed to perform quality control activities BUT once again, the business analyst msut define it. Acceptance criteria is composed by two parts; the criteria and the process to achive the criteria. Suppose you have to create a light bulb and one of the non-functional requirements is a 100 hours duration. Then the criteria could be "light bulb must remain in operation along 100 hours" and the process could be "turn the light bulb on and off along more than 100 hours".
...
1 reply by Juan Carlos Cruz Vega
May 17, 2017 7:44 PM
Juan Carlos Cruz Vega
...
I totally agree on PM role activities, the problem is when you work in small, non-mature businesses, where there are not all roles and the MP has to absorb several more activities.
Regards.
Saving Changes...
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
Acceptance criteria must be defined and linked to the requirements as soon as possible i.e. as soon as requirements are clarified and documented, whether as a specification, user story or use case. This link could typically exist in a few places and would depend on you project requirements. The most common would be the RTM and VCRM.
...
1 reply by Juan Carlos Cruz Vega
May 17, 2017 7:33 PM
Juan Carlos Cruz Vega
...
I appreciate your note to clarify my doubt sr. Oosthuizen.
It is important for me to clarify conceptual doubts to avoid making mistakes in practice, my doubt is in 3 concepts: Request against requirement and criterion of acceptance, in my example, the request is that the pen I want to be developed is blue ink .
A requirement is that the ink length is 10000 short words, another requirement is that the tone of blue be RGB (0, 153, 255)
What would be my acceptance criteria?
Mr. Dmitriy was very clear in his reply; The criterion of acceptance would be that 100 feathers on different paper surfaces were tested for 10000 short words and the result was satisfactory.
Saving Changes...
Juan Carlos Cruz VegaSUBDIRECTOR DE PROYECTOS ESTRATEGICOS PMP®, SMC™, ITIL®| PGR / COPLADIIMéxico, D.F., Mexico
May 12, 2017 2:51 AM
Replying to Anton Oosthuizen
...
Acceptance criteria must be defined and linked to the requirements as soon as possible i.e. as soon as requirements are clarified and documented, whether as a specification, user story or use case. This link could typically exist in a few places and would depend on you project requirements. The most common would be the RTM and VCRM.
I appreciate your note to clarify my doubt sr. Oosthuizen.
It is important for me to clarify conceptual doubts to avoid making mistakes in practice, my doubt is in 3 concepts: Request against requirement and criterion of acceptance, in my example, the request is that the pen I want to be developed is blue ink .
A requirement is that the ink length is 10000 short words, another requirement is that the tone of blue be RGB (0, 153, 255)
What would be my acceptance criteria?
Mr. Dmitriy was very clear in his reply; The criterion of acceptance would be that 100 feathers on different paper surfaces were tested for 10000 short words and the result was satisfactory. Saving Changes...
Juan Carlos Cruz VegaSUBDIRECTOR DE PROYECTOS ESTRATEGICOS PMP®, SMC™, ITIL®| PGR / COPLADIIMéxico, D.F., Mexico
May 11, 2017 4:26 PM
Replying to Sergio Luis Conte
...
Well, take into account that theare two types of requirements: product requirements and project requitements. Project manager is in charge of project requirements. So, product requirements and acceptance criteria is outside your scope as project manager. The business analyst is accountable for that. The only thing you must do is to define project requirements from product requirements. In this case, you must define what quality activities you have to consider to get the deliverables approval. So, acceptance criteria is needed to perform quality control activities BUT once again, the business analyst msut define it. Acceptance criteria is composed by two parts; the criteria and the process to achive the criteria. Suppose you have to create a light bulb and one of the non-functional requirements is a 100 hours duration. Then the criteria could be "light bulb must remain in operation along 100 hours" and the process could be "turn the light bulb on and off along more than 100 hours".
I totally agree on PM role activities, the problem is when you work in small, non-mature businesses, where there are not all roles and the MP has to absorb several more activities.
Regards. Saving Changes...