NEW
Font size
WorksheetsGITA Day 5 / PMI ACP D3
Total questions: 14
Worksheet time: 21mins
On an agile project, some of the development team is struggling to understand how the tasks and user stories fit into the MVP they are working on.
How should this be addressed?
A. Conduct root-cause analysis to ensure defects are being avoided
B. Create a story map for the MVP functionality
C. Capture this as a task in the planning meeting
D. Have the product owner explain the Sprint Goal
The product owner would like the team to devote the first release to delivering the minimal viable product. What does he mean by this?
He wants them to build only the functionality the end users will use the most
He wants them to deliver the smallest package of functionality that will be useful to the market and will enable validated learnings
He wants them to determine the minimal (most efficient and least costly) technological approach
He wants them to identify the most basic features that the product could include and still work
2. During an estimation meeting, the team was unable to reach consensus about the level of effort required to implement a high priority very complex feature with many technical unknowns.
What is the best way to handle this situation?
A.Remove the feature from the product backlog until it can be discussed with the product owner
B. Assign the feature the highest value of story points identified in a planning poker session
C. Allow time for a spike to be performed
D. Have the team leader estimate the effort for the feature
3. During an agile project chartering session, the project stakeholders were developing a product vision and created two artifacts. The first one was the vision box. The second one was just a couple of sentences that indicated the target customer, the key benefit, and competitive advantage.
What was the second artifact created by the project stakeholders?
A.Project charter
B.Project elevator statement
C. Business case
D. Statement of work
6. The acronym INVEST is used as a checklist to evaluate user stories for quality. An agile coach is explaining INVEST to their team.
What is a characteristic of a good user story for the team to aim for using the INVEST model?
A. "I" for iterative (developed over time)
B. "I" for independent (of all other user stories)
C. "I" for incremental (occurring over a series of gradual increments)
D. "I" for interdependent (associated with related user stories in the iteration)
10. An agile team and stakeholders are discussing the product to be developed in their upcoming project. They arranged user stories on a whiteboard using sticky notes by placing the essential functions from left to right across the top of the matrix, and by descending order of priority from top to bottom.
Which of the following visual tool did the project stakeholders use?
A. Story map
B. Prioritized product backlog
C. Product roadmap
D. Regression backlog plan
Which statement best describes the relationship between the product backlog and progressive elaboration in agile?
The product backlog is fully detailed at the beginning of the project and remains unchanged throughout.
Progressive elaboration involves refining the product backlog items over time to provide more detail as priorities and understanding evolve.
The product backlog is created at the start of the project and only updated after each sprint.
Progressive elaboration focuses solely on breaking down large epics into smaller tasks during the first sprint planning meeting.
Which of the following best describes a well-written user story in agile?
A technical specification written by developers to document system requirements.
A short description of a feature written in business language from the perspective of the user, capturing their need and value.
A detailed project plan outlining all tasks required to implement a feature.
A prioritized list of technical activities to be completed by the development team.
Which of the following best defines the INVEST principle in agile?
A framework for prioritizing work items based on business value and technical complexity.
A process for estimating the effort required for each task in a sprint backlog.
A methodology for dividing epics into smaller tasks to improve sprint velocity.
A guideline for creating high-quality user stories that are actionable, independent, and focused on delivering value.
During a sprint planning meeting, the team proposes adding a spike to the sprint backlog to address technical uncertainty in integrating a third-party API.
How should the product owner explain the purpose of this spike to stakeholders?
The spike is a deliverable feature that will immediately add value to the product.
The spike is a user story that will be prioritized and implemented like any other backlog item.
The spike is a time-boxed activity to investigate and resolve uncertainties, enabling the team to make informed decisions.
The spike is a workaround to defer development until a more stable solution is found.
A product owner is working with the development team to forecast the completion of a feature based on story points. The team’s velocity has been consistent at 30 story points per sprint, and the feature has been estimated to require 90 story points.
How should the product owner explain the use of story points in forecasting to stakeholders?
Story points directly correlate to the time required for completing a feature, so the feature will take exactly three sprints to complete.
Story points are used to estimate the relative effort and complexity of tasks, and based on the team’s velocity, the feature is expected to take three sprints to complete.
Story points indicate the dependencies on the other tasks, so the feature will be delivered when all dependent tasks are completed.
Story points are assigned based on the skills of individual team members, so completion depends on resource availability.
A startup is building a new mobile fitness app and decides to release a Minimum Viable Product (MVP) first.
What is the primary purpose of the MVP in an agile context?
To deliver a fully functional product to all target customers as quickly as possible.
To release a basic version of the product with just enough features to gather feedback and validate assumptions.
To ensure the product includes all the core features needed before moving to additional enhancements.
To create a prototype for internal testing without releasing it to customers.
An agile team is working on a project with the following details:
Average Daily Rate per Team Member: $400
Team Size: 6 members
Iteration Length: 8 days
Number of Iterations to Complete the Project: 5
What is the total budget required to complete the project?
$ 72,000
$ 120000
$ 96000
$ 196000
During a sprint planning session, the team decides to use Planning Poker to estimate the effort required for user stories.
What is the primary purpose of using Planning Poker in agile?
To assign specific tasks to team members based on their skill levels.
To generate consensus among team members on the effort and complexity required for each user story.
To finalize the exact number of hours needed to complete a task.
To prioritize user stories in the product backlog.
