A project is starting its third iteration out of six. During planning, the team realized that all of the requirements were not defined clearly enough to start working.
What should the project manager do?
A.
Review and replace the unclear requirements with ones that are clear.
B.
Update the issue log and escalate it to the project sponsor.
C.
Meet with the product owner to review the project backlog.
D.
Invite key users to the next daily meeting to get requirement clarification.
Evolving and discovering requirements. On projects that do not have clearly defined
requirements up front, prototypes, demonstrations, storyboards, and mock-ups can be
used to evolve the requirements. In these situations, stakeholders are more likely to take
an “I’ll know it when I see it” approach to developing requirements. Evolving requirements
are common in projects using iterative, incremental, or adaptive development approaches.
In some cases, new opportunities arise that change requirements.
Managing requirements. Regardless of whether requirements are documented up
front, evolved along the way, or discovered, there is a need to manage them. Ineffective
requirements management can lead to rework, scope creep, customer dissatisfaction,
budget overruns, schedule delay, and overall project failure. Therefore, many projects
have one accountable person for requirements management. This person may serve as
business analyst, product owner, value engineer, or other title. Those individuals managing
requirements may use specialized software, backlogs, index cards, traceability matrices, or
some other method to ensure there is an appropriate level of requirement flexibility versus
stability, and that new and changing requirements are agreed to by all relevant stakeholders.
When facing unclear requirements, it's important to collaborate with the product owner to review and clarify the project backlog. This allows for a better understanding of the requirements and helps in providing the necessary details for the team to proceed with the work. Regular communication with the product owner ensures that requirements are clarified and addressed promptly during the planning and execution phases of the project.
Product owners should review the backlog before each iteration planning meeting to ensure prioritization is correct and feedback from the last iteration has been incorporated. Regular review of the backlog is often called "backlog grooming" in agile circles (some use the term backlog refinement).
Ans A
I don’t know how C is the right answer. First thing to do is to see if there are requirements in backlog that are well defined and can be prioritized for this sprint. If there are none, then you invite the key stakeholders to next daily meeting and make sure you get all the clarifications to move ahead with the backlog for current sprint. So after A, my 2nd choice would be D.
upvoted 1 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
victory108
3Â weeks, 6Â days agosidje
6Â months agoDelab202
10Â months, 2Â weeks agoDelab202
10Â months, 2Â weeks agoAbdelmonm
10Â months, 2Â weeks agokevzzz
10Â months, 3Â weeks agopsvexam
11Â months ago