New PMP Question & Answers with explanation
Directing project work on an agile project consists of several steps. Match the following steps with their descriptions.
Matching
| Directing agile teamwork | ||
| Steps |
Directing agile teamwork | Steps | Description
|
Description |
|
Second Step
|
Daily stand-ups are conducted to examine what was worked on yesterday, what will be worked on today, and what obstacles are standing in the way.
|
|
|
Third Step
|
The product backlog is defined.
|
|
|
First Step
|
Retrospectives are held at the end of the iteration to determine what went well, what improvements can be made to the process, and what didn't go well.
|
|
|
Fourth Step
|
Review meetings are held to examine the work of the iteration and provide and receive feedback.
|
|
|
Fifth Step
|
Planning meetings are held at the beginning of the iteration to pull user stories into the iteration backlog
|
|
Match the following scaling agile frameworks with their description.
Matching
| Scaling agile frameworks | ||
| Framework | Description | |
|
Less
|
Two or more Scrum teams work on the project together. Each Scrum team focuses on a portion of the work.
|
|
|
Safe
|
This consists of up to eight Scrum teams with up to eight members each who all work on the project together.
|
|
|
Enterprise Scrum
|
This extends Scrum practices to all aspects of the organization.
|
|
|
Scrum of Scrums
|
This combines several agile best practices and includes information from functional areas of the business.
|
|
|
DA
|
This is an interactive knowledge base consisting of technical guidance, knowledge, and information on agile.
|
|
Match the following types of tests that are used on agile-based software projects to their description.
Matching
| Testing at all levels | ||
| Name of test | Description | |
|
End to end test
|
A high-level test designed to identify simple failures that could jeopardize the software program.
|
|
|
Smoke test
|
This test is performed after changes are made to the code or when maintenance activities are performed on the hardware the code resides on to ensure the software works the same way it did before the change.
|
|
|
Regression test
|
This test combines software modules and tests them as a group.
|
|
|
Integration test
|
This test is performed on individual modules or individual components of source code.
|
|
|
Unit test
|
Testing the software from the start to the end to ensure the application is working correctly.
|
|
Match the following agile measurements with their definitions.
Matching
| Agile measurements and definitions | ||
| Agile measurements | Definitions | |
|
Definition of done
|
A type of in-the-moment measure
|
|
|
Lead time
|
Typically expressed as deliverables, functionality, or features
|
|
|
Empirical measure
|
The time it takes to complete work on a task from the time work starts
|
|
|
Definition of ready
|
A checklist of elements needed to ensure the deliverable is ready for the customer to use
|
|
|
Response time
|
Describes the specifics of the tasks planned for the iteration before the team begins work
|
|
|
Cycle time
|
The time it takes for a task to go from request to completion
|
|
|
Capacity measures
|
The time a task waits before work starts
|
|
This tool and technique of the Close Project or Phase process looks at project variables and how they contributed to project outcomes. This is for the purpose of improving performance on future projects.
Select one