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
Variable
A changing factor within a project that can be adjusted or influenced based on decisions and circumstances
Characteristics of PREDICTIVE approach with Constraints & Variables
Predictive approaches have variable time and resources, but with a fixed scope
Characteristics of ADAPTIVE approach with Constraints & Variables
Adaptive approaches have fixed time and resources, but more variability with scope
Steps of an Adaptive Project
1) Concept
2) Construct & deliver (with working increments and iterations)
3) Close
Concept (steps of an adaptive proejct)
The initiation and planning stage where you:
1) i dentify the vision and objectives
2) Identify key stakeholders
3) Prioritize features and requirements
4) Establish team, tools, and workflows
Key artifacts:
Project charter
Product vision statement
High-level portfolio/requirements (includes epics and themes)
Product roadmap
Construct and Deliver (steps of an adaptive project)
This is the stage of iterative execution and delivery that includes:
1) Working in short iterations
2) Continuously gathering feedback
3) Adapting to changing requirements
4) have frequent, usable deliveries to stakeholders
Key artifacts:
Product release plan
User stories
Product backlog
Iteration plan
Daily task plan
Demonstration results
Retrospective results
Control charts
Minimum Viable Product (MVP)
Close (steps of an adaptive project)
This is the final stage of the process that includes:
1) Delivering the final product/service
2) Conducting a retrospective to capture lessons learned
3) Ensure proper handover/transition and documentation
Key artifacts:
Final product
Vision Statement
A summarized, high-level description of the expectations for a product such as target market, users, major benefits, and what differentiates the product from others in the market
Elevator Statement (vision statement)
A brief pitch of the purpose and outcome of the project within 30 seconds
Press Release Vision Statement (vision statement)
Making a statement on the product as if the product was available describing what a press release should say about it
Product Vision Board of the Product Datasheet (vision statement)
A vision board that shows the big-picture goals of a product showing the project purpose, target groups, benefits, and achievable outcomes
Product Roadmap
A high-level timeline that depicts such things as milestones, significant events, reviews, and decision points
Characteristics of a Vision Statement
A project summary with a powerful phrase or short description
A list of major benefits
What differentiates the product from others in the market (unique value/competitive advantage)
Iteration Process
1) Initial planning
2) product backlog
3) iteration backlog
4) iteration
5) iteration review
6) retrospective
1-6 repeats until you can do 7) the demo
Simple Scheme (prioritization method)
A prioritization method where stakeholder rank the priority of features using simple numbers (ex 1-10)
MoSCoW Prioritization Scheme (prioritization method)
A prioritization method where stakeholders rank the priority of features based on the categories must have, should have, could have, and won’t have
Dot Voting (prioritization method)
A prioritization method where each stakeholder gets a certain number of dots and votes on what gets higher priority where the feature with the most dots is the most important
Buy a Feature (prioritization method)
A prioritization method where stakeholders get a certain amount of pretend money (ex $100) and have to split it up based on the priority of features where the most important has the most money
Kano Model (prioritization method)
A framework used to model, categorize, and prioritize product features based on a graph
X-axis: execution feasibility
Y-axis: customer satisfaction
5 Product Feature Categories:
@ Basic - expected to be present by default in the final product
@ Performance - features that stakeholders desire and used to evaluate the final product
@ Delighters - features that create a competitive advantage against competitors
@ Indifferent - features that neither satisfy nor dissatisfy
@ Reverse - features that increase satisfaction when excluded from the final product and decrease satisfaction when present
Stack Ranking (prioritization method)
A prioritization method where you stack the highest priority feature at the top and the least at the bottom
Release Backlog
A collection of features, user stories, or tasks that need to be completed to release a product or version of the product
Sprint/Iteration Backlog
A list of tasks or user stories selected from the product backlog to be complete during a single sprint
Minimum Viable Product (MVP)
the most basic version of a product that can be released to the market with just enough features to satisfy early adopters and gather feedback for future development
Absolute estimate
A prediction of the exact time or effort needed to complete a task based on units of time
Relative estimate
An estimation of the amount of time/effort it will take for a task by comparing one task to another
Story Points
Comparative values for relative estimation that are used to compare and estimate the relative size or complexity of a user story or task (this is not an actual unit of measure)
Lean Methodology
An adaptive framework that focuses on delivering value to customers while minimizing waste and inefficiencies
Scrum
An agile framework used for managing and completing complex projects done within sprints
Accountabilities (aka roles):
Product owner
Scrum master
Developers
Events (the responsibilities of the accountabilities):
Sprint planning
Daily scrum (standup)
Sprint review
Sprint retrospective
Kanban
A visual management tool used to track the flow of work and ensure tasks are completed in time that reduced bottle necks and increases quality
Extreme Programming (XP)
An agile software development methodology that focuses on improving software quality and responsiveness to changing customer requirements
Key Concepts:
Pair programming - 2 developers work on tasks
Refactoring - reorganize existing code, remove dupes, and increase cohesion
Continuous integration - spot defects early
Collective code ownership - every developer can improve and amend any code
Feature Driven Development (FDD)
An agile software development methodology that focuses on delivering software in short, structured iterations that emphasizes building and designing software
Focuses on Dynamic Systems Development Method (DSDM) and its key principles:
Focus on the business need
Deliver on time
Collaborate
Never compromise quality
Build incrementally from firm foundations
Develop iteratively
Communicate continuously and clearly
Demonstrate control
Crystal
A family of agile methodologies that emphasizes people, communication, and flexibility over strict processes and tools based on color coding
Key tasks for Eliminating Waste
Identify the value
Study the value stream
Investigate waste in the flow
Streamline the process of agility
Perform continuous improvement
