Agile Principles & PMI-ACP Mindset

Question 1

works with dynamic requirements for the development team to deliver working software frequently through small releases

Answer 1

Agile life cycle

Question 2

is a broad document that establishes the values of agile project management. The four values are individuals and interactions over pro- cesses and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; responding to change over following a plan

Answer 2

Agile Manifesto

Question 3

is a way of thinking about and doing agile projects. Having the agile mindset means you exemplify the values and principles of agile in how you work, how you lead a project, and how you share a passion for agile with others

Answer 3

Agile mindset

Question 4

is a Scrum event where the product owner, the Scrum Master, and the development team work together to dis cuss the backlog items and prioritize the items

Answer 4

Backlog refinement meeting

Question 5

This is an XP role that is like a project manager but is more of a mentor and facilitator. The coach mentors people on the project team, helps get things done, and serves as the hub of communications for the project stakeholders.

Answer 5

Coach

Question 6

An XP concept is that all programmers on the development team follow defined and communicated standards for developing the code.

Answer 6

Code standards

Question 7

An XP concept is that any pair of programmers on the development team can edit anyone’s code.

Answer 7

Collective code ownership

Question 8

is an agile approach that uses eight different schemes of agile project management based on several factors, such as the complexity of the project, the number of project team members, and the criticality of the project

Answer 8

Crystal

Question 9

This is a daily 15-minute meeting during which the team members share progress updates; it is sometimes called a standup meeting because everyone stands for the duration. The Daily Scrum happens every day at the same time, in the same place.

Answer 9

Daily Scrum

Question 10

is responsible for sizing the requirements of the product backlog and getting work done in each sprint; is self-organizing and self-led, and its members are called generalizing specialists because they can often do more than one function on the team.

Answer 10

Development team

Question 11

How many people does an ideal Scrum team has?

Answer 11

no less than five people and no more than eleven people.

Question 12

one of the predecessors of today’s agile project management and relied on a business case to show value and a feasibility study to determine if the development team could create the architecture and requirements the customer identified.

Answer 12

Dynamic Systems Development Method (DSDM)

Question 13

are based on observation, trial and error, and the experience of the person doing the work. Agile projects rely on the knowledge worker to be creative, innovative, and to figure out the work to reach the desired results.

Answer 13

Empirical processes

Question 14

an iterative approach to software development that bases its progress on the client’s values of features the software will provide.

Answer 14

Feature-Driven Development (FDD)

Question 15

works with dynamic requirements for the development team to quickly deliver working software through increments of product releases.

Answer 15

Incremental life cycle

Question 16

utilize defined approaches to com plete processes and tasks; the project team members know exactly what to do and what to expect in the project and in the project management approach

Answer 16

Industrial-work projects

Question 17

Agile projects invert the traditional triple constraints (or iron triangle) so that time and cost are fixed, but the scope is now flexible.

Answer 17

Inverted triple constraint

Question 18

Projects that are driven by creativity and brain power, rather than brawn and effort applied to defined processes and tasks

Answer 18

Knowledge-work projects

Question 19

this agile approach uses a visualization of what needs to be done, creates requirements based on the customer’s definition of value, and includes opportunity for learning and process improvement throughout the project.

Answer 19

Lean Product Development

Question 20

The theorem that explains the more items that are in the WIP queue, the longer it will take the team to complete the items in the queue.

Answer 20

Little’s Law

Question 21

the average number of items in a queuing system equals the average rate at which items arrive multiplied by the average time that an item spends in the system

Answer 21

Little’s Law

Question 22

explains the project’s goal and function in plain, understandable language for all stakeholders.

Answer 22

Metaphor

Question 23

an XP approach where developers work in pairs; one person codes while the other checks the code. The pair switches roles periodically

Answer 23

Pair programming

Question 24

works with dynamic requirements for the development team to create a single delivery of the software solution at the end of the project

Answer 24

Iterative life cycle

Question 25

This approach helps to visualize the flow of the work through a system

Answer 25

Kanban

Question 26

is the long list of prioritized project requirements.

Answer 26

Product backlog

Question 27

This is a role in the Scrum agile methodology that describes the individual that manages the product backlog for the project.

Answer 27

Product owner

Question 28

involves cleaning up the code to remove waste, redundancy, dependent connections, and shortcuts.

Answer 28

Refactoring

Question 29

This is a meeting for larger Scrum projects where multiple teams are working together. Rather than having a huge Daily Scrum, the teams meet separately and then a representative from each team meets in a Scrum to report on each team’s progress. The team representatives answer the same questions as in the Daily Scrum, but for the team rather than individuals. In addition, a fourth question is often posed: Will our team be putting something in another team’s way?

Answer 29

Scrum of Scrums Scrum

Question 30

This role ensures that everyone understands the rules of Scrum, removes impediments for the team, facilitates Scrum meetings, helps the product owner groom the backlog, and communicates the vision of the project to everyone that’s involved.

Answer 30

ScrumMaster

Question 31

In this Scrum event, the development team determines how much work they can take on from the prioritized backlog for the next sprint.

Answer 31

Sprint planning meeting

Question 32

In sprint planning meeting, how do you determine the amount of work you can take on from the prioritized backlog for the next sprint.

Answer 32

based on estimates of the items in the product backlog and past sprints

Question 33

This Scrum event is held after the sprint review and before the next sprint planning meeting. The team discusses what’s worked well with people, prod- uct, and processes in the project, what needs improvement, and the feedback from the product owner from the sprint review meeting.

Answer 33

Sprint retrospective

Question 34

This Scrum meeting is held at the end of each sprint. The development team demonstrates for the product owner, the ScrumMaster, and other key stakeholders the work they’ve accomplished in the past sprint.

Answer 34

Sprint review

Question 35

This Scrum meeting is for the product owner to offer feedback on whether the work has reached the done stage, and, if it hasn’t, describe what’s missing and elaborate on corrections or modifications for the increment of work created.

Answer 35

Sprint review

Question 36

Timeboxed iterations

Answer 36

Sprints

Question 37

Used to create prioritized requirements for the customer.

Answer 37

Sprints

Question 38

last from two to four weeks to complete the selected requirements for the current iteration.

Answer 38

Sprints

Question 39

is sloppy code, shortcuts, and redundancies that need to be cleaned up as the project moves forward.

Answer 39

Technical debt

Question 40

can accumulate and cause the project code to become more complex.

Answer 40

Technical debt