New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

PMI PMP Exam - Topic 1 Question 96 Discussion

Actual exam question for PMI's PMP exam
Question #: 96
Topic #: 1
[All PMP Questions]

An agile team has been assigned to a project that mandates the implementation of changes to key government products. The team has been given 6 months to fulfill this mandate.

What should the team lead do next?

Show Suggested Answer Hide Answer
Suggested Answer: B

An agile team should create the epics at a high level for the requirements and begin grooming sessions as the next step after being assigned to a project that mandates the implementation of changes to key government products. This is because epics are large bodies of work that can be broken down into smaller and more manageable user stories. By creating the epics at a high level, the team can capture the overall scope and vision of the project and align it with the customer's needs and expectations. The team can also start grooming sessions, which are meetings where the team reviews, refines, and prioritizes the backlog of user stories. Grooming sessions help the team to clarify the requirements, estimate the effort, identify the dependencies, and plan the sprints. By creating the epics and grooming the backlog, the team can ensure that they deliver value to the customer in an iterative and incremental manner.

The other options are not the best next steps for the agile team. Creating all of the stories just for the next sprint and skipping the epics until the next sprint would be too short-sighted and risky, as the team would not have a clear understanding of the big picture and the long-term goals of the project. Creating the project charter and statement of work (SOW) to estimate the changes and the scope of the change would be too rigid and formal, as the team would not be able to adapt to the changing requirements and feedback from the customer. Creating all of the stories needed to fulfill this change, documenting them in the backlog, and prioritizing them according to business value would be too time-consuming and overwhelming, as the team would have to deal with a large number of stories without a proper structure and hierarchy.Reference:Project Management Professional (PMP) Certification | PMI,Epics, Stories, Themes, and Initiatives | Atlassian,Epics | Atlassian,Themes, Epics, Stories, and Tasks | Wrike Agile Guide,Understanding Epics in Agile for Managing and Chunking Work Items


Contribute your Thoughts:

0/2000 characters
Celestina
3 months ago
Not sure if they should jump straight to stories without a plan.
upvoted 0 times
...
Stephen
3 months ago
I’d go with option D, prioritizing is crucial.
upvoted 0 times
...
Marica
3 months ago
Surprised they’d skip the epics, that seems risky.
upvoted 0 times
...
Mozelle
4 months ago
Definitely agree, high-level requirements are key!
upvoted 0 times
...
Narcisa
4 months ago
I think creating epics first makes sense for clarity.
upvoted 0 times
...
Rikki
4 months ago
I think skipping to stories right away might not be the best. We need a clear understanding of the bigger picture, so option B sounds right to me.
upvoted 0 times
...
Erasmo
4 months ago
I practiced a similar question where prioritizing stories was key. Option D seems like a good approach, but I wonder if we should focus on epics first.
upvoted 0 times
...
Ling
4 months ago
I'm not entirely sure, but I feel like creating a project charter, like in option C, could help clarify the scope before diving into stories.
upvoted 0 times
...
Leah
5 months ago
I remember we discussed the importance of epics in our last study session. I think option B makes sense to start with high-level requirements.
upvoted 0 times
...
Simona
5 months ago
Ah, this is a tricky one. I'm leaning towards option C - creating the project charter and SOW. That'll help us get a better handle on the scope and timeline before we start planning the work. Gotta make sure we're not missing anything critical.
upvoted 0 times
...
Laquanda
5 months ago
I think option B is the way to go. Jumping straight into the stories without the epics could lead us down the wrong path. Let's get that high-level view first and then we can start refining the backlog. Sounds like a solid plan to me.
upvoted 0 times
...
Tomoko
5 months ago
Hmm, I'm a bit torn here. Option D looks tempting, but I'm not sure if we have enough information yet to create all the stories. Maybe we should start with the epics and then break them down as we go. What do you guys think?
upvoted 0 times
...
Francis
5 months ago
This seems like a classic agile scenario. I'd go with option B - creating the epics at a high level and starting the grooming sessions. That way we can get a good handle on the overall requirements before diving into the details.
upvoted 0 times
...
Teri
1 year ago
I think creating the project charter and statement of work would help in estimating the changes and scope of the project. It's important to have a clear plan in place.
upvoted 0 times
...
Kanisha
1 year ago
I believe creating the epics at a high level and starting grooming sessions would also be beneficial to get a better understanding of the requirements.
upvoted 0 times
...
Eulah
1 year ago
Haha, option A? Really? That's like trying to build a house without a blueprint. B all the way, baby!
upvoted 0 times
...
Junita
1 year ago
I agree with Paola. It's important to have a clear understanding of the work that needs to be done and prioritize accordingly.
upvoted 0 times
...
Judy
1 year ago
You know, I was tempted by C, but B just seems like the logical choice. Gotta love those grooming sessions!
upvoted 0 times
Denny
12 months ago
Prioritizing stories based on business value is crucial for success.
upvoted 0 times
...
Louann
12 months ago
D) Create all of the stories needed to fulfill this change, document them in the backlog, and prioritize them according to business value.
upvoted 0 times
...
Gerri
12 months ago
Yeah, grooming sessions are key to understanding the requirements.
upvoted 0 times
...
Shawnta
12 months ago
B) Create the epics at a high level for the requirements and begin grooming sessions.
upvoted 0 times
...
...
Paola
1 year ago
I think the team lead should create all of the stories needed and prioritize them based on business value.
upvoted 0 times
...
Carman
1 year ago
I'm going with D. Creating all the stories and prioritizing them based on business value is the way to go, especially with a tight 6-month deadline.
upvoted 0 times
Kimbery
1 year ago
Yes, it's important to have a clear plan and focus on delivering the most valuable features first.
upvoted 0 times
...
Adelle
1 year ago
I agree, prioritizing based on business value is crucial for meeting the deadline.
upvoted 0 times
...
...
Rosalyn
1 year ago
Option B makes the most sense to me. Epics at a high level will help the team get an overview of the requirements before diving into the details.
upvoted 0 times
Mohammad
1 year ago
D) Create all of the stories needed to fulfill this change, document them in the backlog, and prioritize them according to business value.
upvoted 0 times
...
Nakisha
1 year ago
C) Create the project charter and statement of work (SOW) to estimate the changes and the scope of the change.
upvoted 0 times
...
Wilbert
1 year ago
B) Create the epics at a high level for the requirements and begin grooming sessions.
upvoted 0 times
...
...

Save Cancel