Hi everyone,
While studying Agile concepts for the PMP exam, I came across a practice situation that left me a bit unsure about how to interpret PMI’s perspective.
Here’s a similar example:
During testing of a digital payment system, the team discovered that it couldn’t process international transactions — a key capability that was expected by stakeholders. Earlier in the project, there was a backlog item described as “Customer can complete a purchase online,” but it was considered too broad for the current iteration and postponed.
The suggested “best” approach in the practice material said the Project Manager should have made sure a more specific and well-defined item was shared with the team early on.
However, my interpretation is that it might have been more effective to facilitate ongoing backlog review sessions to continuously clarify and refine items. My reasoning:
In Scrum, it’s typically the Product Owner who brings product backlog items to the team for discussion and prioritization.
Regular backlog review (refinement) helps the team break down complex or vague items into smaller, clearer pieces, ensuring critical needs (like international payments) aren’t overlooked.
This process encourages continuous collaboration and stakeholder engagement, aligning expectations and priorities before development begins.
While having precise backlog items is certainly important, I believe consistent backlog review offers a proactive and collaborative approach that aligns with Agile’s principles of transparency and adaptability.
Could anyone share how PMI would likely expect us to interpret this on the PMP exam? I’d like to be sure I’m distinguishing between these two perspectives correctly.
Thank you in advance for your insight!
Community Champion
