Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

PMP Exam Prep > AGILE CONCEPTS > Flashcards

AGILE CONCEPTS Flashcards

(163 cards)

Start Studying
1
Q

Agile Principle Prioritization

A

Agile projects prioritize customer collaboration over contract negotiation and working software over comprehensive documentation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Individuals and Interactions Over Processes and Tools

A

Agile emphasizes the importance of people and their interactions over rigid processes and tools.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Flexibility Over Strict Planning

A

Agile methodologies value responding to changes and adapting plans over following a fixed plan.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Adaptability Over Detailed Planning

A

Agile projects prioritize adaptability and responsiveness to change over comprehensive planning.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Change Management in Agile

A

Changes are welcomed in Agile, but they need to be understood, managed properly, and communicated with stakeholders.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Customer Collaboration for Efficient Decision-Making

A

Agile emphasizes collaborative communication with customers for immediate and efficient change management.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Agile Collaboration Over Contractual Obligations

A

Agile teams focus on collaboration and responsiveness over rigid contractual requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Contract Management in Agile Environments

A

Agile contracts should promote mutual trust, frequent communication, and a shared vision for project outcomes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Demonstrating Features to Stakeholders

A

Agile prioritizes frequent delivery of working software and obtaining stakeholder feedback after each increment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Servant Leadership in Agile

A

Agile promotes servant leadership, where the leader supports the team’s needs and trusts them to get the job done.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Agile Project Managers are Servant Leaders

A

Agile project managers should support and guide their team, removing obstacles and providing necessary resources.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Effective Communication in Agile

A

Face-to-face conversation is considered the most efficient and effective method of communication in Agile.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Work In Progress (WIP) Limits in Agile

A

Implementing WIP limits in Agile ensures teams do not overcommit, stabilizing the flow of work and enhancing predictability in release schedules.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Eliminating Waste in Agile

A

Agile practices focus on eliminating processes or steps that do not bring value to the end product or customer.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Visualizing Work in Kanban

A

Kanban provides visualization of work and workflow to improve flow and reduce bottlenecks.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Collective Ownership

A

Promotes a shared sense of responsibility for the work and project outcomes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Agile Scope in Uncertain Environments

A

Agile projects accept that the scope cannot be fully defined from the outset and advocate for flexibility and adaptation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Addressing Unclear Scope in Agile Projects

A

Agile projects divide the project into sprints, planning in detail only for the upcoming sprint, and adjusting as more information becomes available.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Frequent Delivery of Working Product Components

A

Agile projects aim to deliver working product components frequently, in small increments.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Harnessing Changing Requirements

A

Agile processes harness changing requirements, even late in development, for the customer’s competitive advantage.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Product Backlog Management

A

The Product Backlog is a living document in Scrum, containing evolving requirements and priorities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Sprint Review Objectives

A

Presenting and gathering feedback on the delivered product increment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Sprint Backlog Adjustments

A

The Development Team is empowered to make adjustments to the Sprint Backlog.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Focus of Agile Retrospectives

A

Identifying the root cause of issues and brainstorming potential solutions collaboratively.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Agile Team's Approach to Additional Features
Emphasizes simplicity and prioritizes essential features over exciting but non-essential ones.
26
Simplicity in Agile
Focusing on simplicity - doing only the necessary work that provides value.
27
Prioritizing High-Value Features
Agile methodologies prioritize features based on their value to stakeholders and end-users, breaking them into smaller deliverables for frequent releases.
28
Sustainable Pace in Agile
Agile emphasizes maintaining a sustainable pace and proper work distribution to avoid overwhelming team members.
29
Lean Agile Project Management
Focuses on eliminating wasteful processes to streamline operations.
30
Product Owner's Role in Change Management
Evaluating and prioritizing changes, and including them in the Product Backlog if necessary.
31
Scrum Master's Role in Removing Impediments
Working with stakeholders to remove blockers and facilitate smooth progress.
32
Scrum Master as a Coach
Clarifying doubts and ensuring the team understands Scrum values and principles.
33
Agile Documentation
Agile prefers just enough documentation that adds value, focusing on working deliverables.
34
Business and Developer Collaboration
Close collaboration between business people and developers is essential throughout the project.
35
Primary Measure of Progress
In Agile projects, the primary measure of progress is working product.
36
Technical Excellence Enhances Agility
Continuous attention to technical excellence and good design enhances Agile flexibility.
37
Architectures from Self-Organizing Teams
Self-organizing teams lead to the best project outcomes in Agile environments.
38
Regular Reflection and Adjustment in Agile
Agile teams regularly reflect on their progress and make adjustments for continuous improvement.
39
Stacey Matrix Simple Environment
Clear requirements and technology, low risk, suitable for predictive approaches.
40
Stacey Matrix Complicated Environment
Low to moderate uncertainty in requirements and technology, suitable for adaptive approaches.
41
Stacey Matrix Complex Environment
Moderate to high uncertainty in requirements and technology, suitable for adaptive approaches.
42
Project Life Cycles Predictive
Known as Traditional Approach, sequential phases, final deliverable is created at the end.
43
Project Life Cycles Iterative
Allows feedback for unfinished deliverable, spiral steps.
44
Project Life Cycles Incremental
Frequent small deliverables.
45
Project Life Cycles Agile
Mixture of Iterative and Incremental, high frequency of delivery, adaptability to change
46
Project Life Cycles Hybrid
Combines elements from different methodologies.
47
Agile Life Cycle’s Focus
Early and continuous customer feedback.
48
Agile vs Predictive
Agile adapts to changes, Predictive is less flexible.
49
Major Agile Principles/Attributes
Customer Feedback: Early and continuous.
50
Major Agile Principles/Attributes Customer Satisfaction
Priority in Agile, ensures end product meets needs.
51
Major Agile Principles/Attributes Smaller Working Products
Quick adjustments, reduced redesign time.
52
Major Agile Principles/Attributes High Uncertainty and Risk
Due to dynamic requirements.
53
Major Agile Principles/Attributes Work-in-Progress Limits
Set by the team in Flow-Based Agile.
54
Hybrid Life Cycle Examples Predictive followed by Agile
Starts Predictive, switches at a point.
55
Hybrid Life Cycle Examples Agile followed by Predictive
Starts Agile, switches at a point.
56
Hybrid Life Cycle Examples Combined Predictive and Agile Components
Neither a Predictive nor an Agile approach is completely followed.
57
Hybrid Life Cycle Examples Predictive with Agile Components
Majorly Predictive with Agile for specific features.
58
Project Life Cycle Choice
Depends on organizational, project, and team attributes.
59
Agile Suitability Filter
Helps determine if Agile is suitable for a project.
60
Tailoring in Project Management
Adapt processes to project's unique characteristics.
61
Application of Tailoring
Throughout the project lifecycle.
62
Agile Tailoring
Adjust Agile approach based on project's certainty level and requirements stability.
63
Continuous Improvement
Regularly improving processes through retrospectives in Agile projects.
64
Starting with a Pilot Project
Gradually introduces Agile in a less risky setting.
65
Designing Fit-for-Purpose
Combines Predictive and Agile features.
66
Right Team Structure in Agile
Enhances project goal visibility and collaborative approach.
67
Process Determination in Agile
Collaborative and continuous improvement based on project needs.
68
Key Characteristic of Agile Teams
Cross-functional.
69
Cross-Functional Teams
Enhance collaboration and knowledge sharing.
70
Benefit of Cross-Functional Teams
Increased work pace due to direct communication.
71
Cross-Functional Teams and Customer Satisfaction
Faster product delivery.
72
Project Manager's Role
Servant Leader, focusing on mentoring and serving team needs.
73
Servant Leadership
Encourages team self-decision making and empowerment.
74
Trustful Agile Environment
Created using emotional intelligence to build trust.
75
Agile Management Styles
Tailored to specific needs; primary style is Servant Leadership.
76
Appreciating Team's Success
Done after achieving each milestone to foster motivation.
77
Serving Team's Needs
Encourages self-confidence and team success.
78
Strong Communication in Agile
Fosters collaboration and reduces coordination overhead.
79
Ideal Team Structure for Agile
Co-located Teams.
80
Collocating Team Members
Enables constant communication and interaction.
81
Advantage of Co-located Teams
Faster and effective communication.
82
Distributed Teams
Fully functioning teams in multiple locations.
83
Enhancing Performance in Distributed Teams
Facilitate real-time communication (e.g., video conferencing).
84
High Uncertainty Management
Utilize Servant Leadership to serve team needs and facilitate adaptation.
85
Leadership for Low Competence, High Commitment
Directing Leadership Style.
86
Supporting Leadership Style
Low Directive, High Supportive Behavior.
87
Leadership for High Competence
Delegating Leadership Style.
88
Directing Leadership Style
High Directive, Low Supportive Behavior.
89
Leaders' Focus
Influencing people to realize a vision.
90
Coaching Leadership Style
High Directive, High Supportive Behavior.
91
Improving Product Quality
Instant feedback within cross-functional teams.
92
Collaborative Environment in Agile
Encourages a positive attitude and willingness to help.
93
T-shaped/M-shaped Individuals
Better understanding of project activities.
94
I-shaped Person
High-level knowledge in one skill only.
95
Team Responsibility in Agile
Collective ownership of product quality and success.
96
Collective Product Ownership
Shared responsibility for the work done among team members.
97
Role of Scrum Master/Team Facilitator
Ensures Agile processes work effectively.
98
Scrum Master's Responsibility
Ensure adherence to Agile framework and resolve impediments.
99
Product Owner's Role
Provides direction for the final product.
100
Stable Team Environments
Improves cost management by reducing mistakes.
101
100% Dedicated Agile Team Members
Prevents unclear assignments, increases efficiency.
102
Adapting to Frequent Requirement Changes
Foster open communication and collaboration.
103
Handling Stakeholder Feedback
Evaluate collaboratively and adapt continuously.
104
Handling New Ideas in Sprint Review
Open discussion to understand value, encourage collaboration.
105
Building Cohesive and Trusting Teams
Facilitate open dialogues for team member expression.
106
Leadership in Self-Organizing Teams
Servant Leadership is most effective.
107
Tailoring Leadership in Agile Projects
Focus on team's familiarity with agile, not collaboration tools.
108
Guiding Beginners in Agile
Directing Leadership Style for clarity and supervision.
109
Agile Project Charter
A flexible document outlining project objectives and approach.
110
Vision in Agile Charter
Represents the project's primary goal.
111
Mission in Agile Charter
Answers 'How will we achieve our Vision?'
112
Success Criteria in Agile Charter
Indicates results demonstrating the Vision's achievement.
113
Agile Charter Creation
Facilitated by Project Manager.
114
Kick-off Meeting Timing in Agile Projects
At project beginning, before Charter creation.
115
Team Charter in Agile
A 'Social Contract' outlining team values and norms.
116
Ground Rules in Team Charter
Focus on team collaboration norms and define working agreements within the team.
117
Team Norms in Charter
Shared values and beliefs guiding team behavior.
118
Benefits of Agile Chartering
Provides clear understanding of team values and norms.
119
Responsibility for Agile Charter
Project Sponsor.
120
Role in Agile Charter Review
Product Owner leads scope and deliverable alignment.
121
Backlog in Agile
A prioritized list of requirements.
122
Minimally Viable Product (MVP)
Minimum functionality for customer use and user feedback.
123
Product Owner's Role in Backlog
Create and update it.
124
Product Owner's Responsibility
Ensures product backlog aligns with product vision.
125
Epic in Agile
Large work body, not deliverable in a single iteration.
126
Agile Spikes
Explore uncertainties and solutions for stories.
127
Backlog Refinement Session
Clarify, re-prioritize, and modify items in the Backlog.
128
Backlog Refinement Purpose
Make Backlog ready for the next iteration.
129
Definition of Done for Backlog
Specifies quality criteria for completed work.
130
Story Points
Estimate story complexity relatively.
131
Relative Sizing in Agile
Estimating story points by comparison.
132
Planning Poker Technique
Estimation cards laid down post-discussion.
133
Daily Standup Meetings
Conducted standing to encourage brevity.
134
Kanban Board in Standup Meetings
Visualize workflow and progress.
135
Retrospective Meeting Discussion
Previous iteration's successes and improvements.
136
Addressing Sprint Challenges
Discussed in Sprint Retrospective.
137
Retrospective Findings
Ongoing 'lessons learned' log.
138
Agile 'Fast Failure'
Catch failures early to reduce costs and other negative effects.
139
Fast Failure Strategy
Build features incrementally and validate continuously.
140
Avoiding Poor User Experience in Agile
Frequent verification and validation.
141
Challenge in Determining Completion in Agile
Continuously changing scope.
142
Velocity in Agile Tracking
Story Points completed in an iteration.
143
Addressing Decreased Velocity
Understand underlying reasons and address challenges.
144
Lead Time Measurement
Duration from story addition to completion.
145
Backlog Burnup Chart
Represents completed Features in Backlog.
146
Cumulative Flow Diagram Usage
Measures Cycle Time, Response Time, Lead Time.
147
Advantage of Kanban Boards
Tracks work and visualizes progress.
148
Little's Law in Agile
Understanding the relationship between cycle time, work in progress, and throughput.
149
Value Stream Map
Identifies bottlenecks and wastes in value flow.
150
Cost Performance Index (CPI)
Indicates the cost efficiency of the project.
151
Schedule Performance Index (SPI)
Represents the time efficiency of the project.
152
Challenges in Procurement and Contract Management
Agile's uncertain nature vs. contracts' need for certainty.
153
Statement of Work (SOW)
Detailed description of work packages and deliverables.
154
Fixed Price Work Packages
Payment made upon completion of each work package.
155
Re-estimation Option
Enables scope changes in Agile contracts.
156
Graduated Fixed Price Clause
Adjusts payment rates based on actual time spent.
157
'Not to Exceed' Clause
Limits the buyer's financial risk.
158
Early Cancellation Clause
Allows buyer to cancel remaining work.
159
Dynamic Scope Clause
Allows scope changes without affecting cost or duration.
160
Agile PMOs vs. Traditional PMOs
Agile PMO focuses on on-demand support and consulting.
161
Support by Agile PMOs
Consulting with team members and stakeholders on-demand.
162
Handling Requirement Changes in Agile
Incorporate changes into the Backlog and prioritize.
163
Addressing Stakeholder Concerns
Sprint Review for stakeholder updates.

PMP Exam Prep (13 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions