2.
Design
Collaborating Roles:
-
Product Manager
-
Product Owner
-
Business Analyst
-
UX Designer
-
Artist
Example Tasks:
-
Research
-
UX/UI
-
Design
3.
Planning
Collaborating Roles:
-
ScrumMaster
-
Project Manager
-
Personnel Manager
-
Team Members
Example Tasks:
-
Scheduling
-
Facilitation
-
Communication
4.
Implementation
4.
Implement
Collaborating Roles:
-
Developer
-
Architect
-
Clerk
-
Writer
Example Tasks:
-
Coding
-
Writing
-
Construction
5.
Verification
5.
Verify
Collaborating Roles:
-
Tester
-
Quality Assurance
-
Quality Control
-
Developer
Example Tasks:
-
Testing
-
Code Review
-
Reporting
6.
Operations
Collaborating Roles:
-
Network Administrator
-
Support
Example Tasks:
-
Environments
-
Inventory
-
Maintenance
1.
People
Collaborating Roles:
-
ScrumMaster
-
Project Manager
-
Personnel Manager
Example Tasks:
-
Scheduling
-
Facilitation
-
Communication
Agile Helps Organizations in 6 Main Collaboration Areas...
*NOTE: We usually see terms like “Coding” and “Testing” here, but Agile works in more places than IT/software.
You may have noticed that the 6 words below are not names of roles. Agile is about collaboration, so these 6 areas are about how we work together.
But there are also spheres of influence at play...
...and not everyone interacts with all spheres.
Global
Impact
Competitors
Team
Team
Team
Product
Teams
Team
Team
Team
Product
Teams
Market
Team
People
Design
Plan
Implement*
Verify*
Operations
*NOTE: We usually see terms like “Coding” and “Testing” here, but Agile works in more places than IT/software.
Product
People
Design
Plan
Implement*
Verify*
Operations
Organization
People
Design
Plan
Implement*
Verify*
Operations
Impact
People
Design
Plan
Implement*
Verify*
Operations
So we started cataloguing Agile practices...
Some people use Agile within teams. Others are focused on Agile practices within teams of teams, collaboratively building products together. Still other groups use Agile practices to establish an organization’s position within its market, and some Agile practices help us establish our place and impact on the world.
And we organized them for clarity...
Team Practices
T2. Design
T2.1
Feature Mapping
T2.2
Iterative Prototyping
T2.3
Unknowns First
T2.4
Checklists
T3. Planning
T3.1
Collaborative Planning
T3.2
Resource Allocation
T3.3
Small Batches
T3.4
Prioritized Delivery
T1. People
T1.1
Collaborative Growth
T1.2
Individual Growth
T1.3
Listening & Appreciation
T5. Verification
T5.1
Independent Verify
T5.2
Reproducible Testing
T5.3
Defect Tracking
T6. Operations
T6.1
Independent Test Environment
T6.2
Independent Customer Environment
T6.3
Delivery Tracking
T4. Implementation
T4.1
Daily Collaboration
T4.2
Resource Management
T3.5
Working Sessions
T3.4
Prioritized Serial Delivery
Product Practices
P2. Design
P2.1
Team of Teams Alignment
P2.2
Iterative Cust Delivery
P2.3
Economic Prioritization
P3. Planning
P3.1
Data-Driven Forecasting
P3.2
Long-Range Planning
P3.3
Collab Depend Planning
P3.4
Stakeholder Reporting
P4. Implementation
P1. People
P1.1
Intrinsic Motivation
P1.2
Integrating Multiple POVs
P5. Verification
P5.1
Test First
P5.2
Regression Testing
P5.3
Automated Verification
P5.4
Outcome Verification
P5.5
Direct Customer Testing
P6. Operations
P6.1
Automate Everything
P6.2
Automate Recovery
P6.3
Automation Reporting
P4.1
Implementation Debt
P4.2
Cross-Functional Teams
P4.3
Shared Better Practices
Practices go by many names…
Team Practices
T2. Design
T2.1
Feature Mapping
T2.2
Iterative Prototyping
T2.3
Unknowns First
T2.4
Checklists
T2. Planning
T3.1
Collaborative Planning
T3.2
Resource Allocation
T3.3
Small Batches
T3.4
Prioritized Delivery
T3.5
Working Sessions
Scrum Version
User Story Mapping
Iterative Prototyping
Spikes
Definition of Ready
Planning Poker
Backlog Refinement
Sprints
Burndown Charts
Sprint Planning
Kanban Version
User Story Mapping
Iterative Prototyping
Design Sprint
Definition of Ready
Mob Programming*
Triage
Work In Progress (WIP)*
Work In Progress (WIP)*
Mob Programming*
Non-IT Version
Flow Chart
Draft Reviews
Discovery Sessions
Scope Definition
Collaborative Planning
Resource Allocation
Wait List
First In / First Out
Working Sessions
*NOTE: Some techniques perform double duty.
The names in the catalog are designed to be inclusive (especially outside IT) and represent the many flavors of Agile. All of them are valid, though some techniques make other techniques unnecessary.
