Kim HannerProject Manager| SkillPathKs, United States
During UAT you discover a missed requirement, do you consider that a bug, enhancement, or create a new user story for the requirement? Saving Changes...
It is not necessarily any of the above. It is not a bug (error performing a function) or an enhancement (increase in capability over the baseline). It may not even be a feature (tool to enable a function).
Requirements are constraints that *may* apply to functions or features. They are distinct from functions/features. Many requirements are invisible to the user but may apply to an existing user story such as the required response time of a specific feature.
...
1 reply by Kim Hanner
Oct 27, 2021 2:06 PM
Kim Hanner
...
Thank you. I was really trying to get at how would I classify the missed requirement. It should have been included in the initial requirements and is part of the overall scope.
It depends Kim. A missing detailed requirement might have been a missing acceptance criteria on a user story in which case it might be classified as a defect originating from a missed requirement. A missing higher-level functional need might be captured as a story but it would still be of "some" value to recognize that it originated from a missed requirement.
Assuming it is truly a missed requirement, then that means it was part of the scope baseline so I wouldn't consider that an enhancement.
Kiron
...
1 reply by Kim Hanner
Oct 27, 2021 2:07 PM
Kim Hanner
...
Thank you. I don't consider it an enhancement either, that is the current debate. The missed requirement is part of overall scope and was truly missed.
Saving Changes...
Kim HannerProject Manager| SkillPathKs, United States
Oct 27, 2021 1:49 PM
Replying to Keith Novak
...
It is not necessarily any of the above. It is not a bug (error performing a function) or an enhancement (increase in capability over the baseline). It may not even be a feature (tool to enable a function).
Requirements are constraints that *may* apply to functions or features. They are distinct from functions/features. Many requirements are invisible to the user but may apply to an existing user story such as the required response time of a specific feature.
Thank you. I was really trying to get at how would I classify the missed requirement. It should have been included in the initial requirements and is part of the overall scope.
...
1 reply by Keith Novak
Oct 27, 2021 3:45 PM
Keith Novak
...
I would classify it as a missed requirement. Requirements come in different types. They may be part of the scope such as customer driven requirements, and they may relate to features such as each feature must meet some security requirement, but it depends on the type of requirement.
In the case of derived requirements, they may be internal and invisible except for the intended system operation For example, Programs A and B need to communicate data and that requires a specific data exchange protocol which is a lot lower level detail than the scope, but missing that requirement may generate a bug where the 2 programs don't work together.
Since the requirements may impact the scope, one or many features, and the logical interactions between parts of your system, they generally get their own classification in systems engineering terminology. A miss or a gap is as good a term as any.
Saving Changes...
Kim HannerProject Manager| SkillPathKs, United States
Oct 27, 2021 2:03 PM
Replying to Kiron Bondale
...
It depends Kim. A missing detailed requirement might have been a missing acceptance criteria on a user story in which case it might be classified as a defect originating from a missed requirement. A missing higher-level functional need might be captured as a story but it would still be of "some" value to recognize that it originated from a missed requirement.
Assuming it is truly a missed requirement, then that means it was part of the scope baseline so I wouldn't consider that an enhancement.
Kiron
Thank you. I don't consider it an enhancement either, that is the current debate. The missed requirement is part of overall scope and was truly missed. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Hi Kim,
in the end it comes down to the question who pays for the damage and the implementation. If it is a true miss, who was in charge of requirements and made the omission?
If the requirement is needed, you might claim, implementation would have to be payed for, at an estimated amount. The fact the requirement comes so late leads to extra cost (and maybe delays), this is the cost of damage and should be bourne by the party in charge of requirements.
The requirement indeed is a change request too, to the approved plan.
It could be called a bug in the completeness of requirements. A new user story might be reasonable to understand the details and consequences. And it enhances the current functionality.
Thomas
...
1 reply by Kim Hanner
Oct 27, 2021 3:15 PM
Kim Hanner
...
Thank you! We are still in development and testing. This was a true missed requirement and is something that is part of scope. I am pretty sure I have settled on the notion that this is NOT and enhancement, and isn't a bug, it's a requirement that was missed.
Saving Changes...
Kim HannerProject Manager| SkillPathKs, United States
Oct 27, 2021 3:10 PM
Replying to Thomas Walenta
...
Hi Kim,
in the end it comes down to the question who pays for the damage and the implementation. If it is a true miss, who was in charge of requirements and made the omission?
If the requirement is needed, you might claim, implementation would have to be payed for, at an estimated amount. The fact the requirement comes so late leads to extra cost (and maybe delays), this is the cost of damage and should be bourne by the party in charge of requirements.
The requirement indeed is a change request too, to the approved plan.
It could be called a bug in the completeness of requirements. A new user story might be reasonable to understand the details and consequences. And it enhances the current functionality.
Thomas
Thank you! We are still in development and testing. This was a true missed requirement and is something that is part of scope. I am pretty sure I have settled on the notion that this is NOT and enhancement, and isn't a bug, it's a requirement that was missed. Saving Changes...
Thank you. I was really trying to get at how would I classify the missed requirement. It should have been included in the initial requirements and is part of the overall scope.
I would classify it as a missed requirement. Requirements come in different types. They may be part of the scope such as customer driven requirements, and they may relate to features such as each feature must meet some security requirement, but it depends on the type of requirement.
In the case of derived requirements, they may be internal and invisible except for the intended system operation For example, Programs A and B need to communicate data and that requires a specific data exchange protocol which is a lot lower level detail than the scope, but missing that requirement may generate a bug where the 2 programs don't work together.
Since the requirements may impact the scope, one or many features, and the logical interactions between parts of your system, they generally get their own classification in systems engineering terminology. A miss or a gap is as good a term as any.
...
1 reply by Kim Hanner
Oct 27, 2021 3:50 PM
Kim Hanner
...
That is exactly what I am planning to do, classify as a missed requirement. We can then use this classification to run reporting and work on bettering our BA team.
Saving Changes...
Kim HannerProject Manager| SkillPathKs, United States
Oct 27, 2021 3:45 PM
Replying to Keith Novak
...
I would classify it as a missed requirement. Requirements come in different types. They may be part of the scope such as customer driven requirements, and they may relate to features such as each feature must meet some security requirement, but it depends on the type of requirement.
In the case of derived requirements, they may be internal and invisible except for the intended system operation For example, Programs A and B need to communicate data and that requires a specific data exchange protocol which is a lot lower level detail than the scope, but missing that requirement may generate a bug where the 2 programs don't work together.
Since the requirements may impact the scope, one or many features, and the logical interactions between parts of your system, they generally get their own classification in systems engineering terminology. A miss or a gap is as good a term as any.
That is exactly what I am planning to do, classify as a missed requirement. We can then use this classification to run reporting and work on bettering our BA team. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
While it depends on your defined process let me put this so simple than that: everything that has to be done must be part of the backlog. So, something has to be created to be placed into it. For example a user story. And that must not be done in the current iteration/sprint. It is for the next. Saving Changes...
Classifying it as a bug or enhancement matters much less than what you want to do about it. Avoid having the "bug or feature?" discussion at all if you possibly can.
If this is something in the current iteration then the team can decide whether they can complete the required change as part of that iteration without compromising any other goal. If the answer is no, then your "Definition of Done" should be the guide as to whether the story is deemed complete or not. Those two decisions (sprint goal and DoD) are what should tell you whether you need a new backlog item or consider it part of the existing one. Saving Changes...
