Module 9: Adaptive Approaches Flashcards
Guiding Principles of Agile Mindset
1) Value individuals and iterations over processes and tools
2) Value working software over comprehensive documentation
3) Value customer collaboration over contract negotiation
4) Value responding to change over following a plan
Agile Values
People
Customer Collaboration
Responding to Change
Working Product
12 Working Principles of Agile
Continuous Delivery
Changing Requirements
Frequent Delivery
Daily Collaboration
Motivated Individuals
Face-to-Face Conversation
Working Software
Sustainable Development
High Quality and Design
Simplicity
Self-Organizing Teams
Continuous Improvement
T-shaped skill
Key balance of skill sets where an individual has cross-disciplinary expertise across multiple areas in addition to a deep understanding of a specific skill
Predictive Team Role Characteristics
Distinct team roles
Different roles may be engaged in only different stages of the project
Hierarchical with centralized leadership
PM activities are across a PM team
Adaptive Team Role Characteristics
Cross-functional team roles
Roles last throughout the entirety of the project
Distributed management and leadership
Project team may self-organize
Servant Leadership
A leadership style where the leader’s focus is on supporting their team rather than exercising authority/control
Role:
Providing resources, support, and political assistance
Coaching the team
Fostering collaboration
Understanding team member’s needs
Maximizing team performance
Scope
The sum of all products, services, and results delivered by the project
Scope Statement
A project document that defines what is included (and not included) in a project, describing the project’s objectives, deliverables, boundaries, and constraints
Product Backlog
A prioritized list of work items that needs to be completed to develop and improve a product including all the features and user stories
Epic
A large, high-level work item that represents a broad objective or major part of the product that is too big to complete within an interation
Feature
A set of related requirements within an epic that delivers value to the user
User Story
A small, specific work item that defines a particular need from the user’s perspective
Definition of Done (DoD)
A checklist of all the criteria required to be met so that a deliverable can eb considered ready for customer use
Story Point Estimating
An estimation technique used to measure the effort needed to complete a user story relative to other stories
Retrospective
A lessons learned meeting to explore and improve both processes and product
Iteration
A time-boxed development cycle used to complete work tied to user stories and tasks
When to used an ADAPTIVE approach based on PRODUCT criteria
@ there is more innovation needed
@ requirements are not all known
@ there may be less regulations/need for compliance
@ multiple deliverables are possible
@ likelihood of scope change is high
@ deliverables can be easily adapted
@ there can be more risks because of ambiguity
When to use a PREDICTIVE approach based on PRODUCT criteria
@ there is less innovation needed
@ requirements are known in the initiation phase
@ detailed planning is possible
@ there are more regulations
@ there is a single point of delivery at the project end
@ scope is well known and established
@ the deliverable is not easily adaptable
@ risks are more well known and planned for
When to use an ADAPTIVE approach based on PROJECT criteria
@ stakeholders take an active role in feedback
@ there are iterations with multiple deliverables throughout the project
@ flexible spending is possible
When to use a PREDICTIVE approach based on PROJECT criteria
@ some stakeholders are not directly involved
@ schedule is based on fixed milestones
@ Funding is based on fixed budgeting
When to use an ADAPTIVE approach based on ORGANIZATION criteria
@ senior management supports an adaptive mindset
@ the culture is less hierarchical
@ there are less bureaucratic processes
@ teams are committed to the project full time and are collocated
When to use a PREDICTIVE approach based on ORGANIZATION criteria
@ organization management is rigid and well defined
@ the culture is hierarchical
@ there is a rigid structure with bureaucratic processes
@ teams may not be involved with the project full time with virtual support
Constraint
A fixed limitation/restriction that a project must operate within
