What is the
Agile Mindset Mapping Index™️?

1.

Design

Collaborating Roles:

  • Product Manager

  • Product Owner

  • Business Analyst

  • UX Designer

  • Artist

 

Example Tasks:

  • Research

  • UX/UI

  • Design

2.

Planning

Collaborating Roles:

  • ScrumMaster

  • Project Manager

  • Personnel Manager

  • Team Members

Example Tasks:

  • Scheduling

  • Facilitation

  • Communication

3.

Implementation

3.

Implement

Collaborating Roles:

  • Developer

  • Architect

  • Clerk

  • Writer

Example Tasks:

  • Coding

  • Writing

  • Construction

4.

Verification

4.

Verify

Collaborating Roles:

  • Tester

  • Quality Assurance

  • Quality Control

  • Developer

Example Tasks:

  • Testing

  • Code Review

  • Reporting

5.

Operations

Collaborating Roles:

  • Network Administrator

  • Support

Example Tasks:

  • Environments

  • Inventory

  • Maintenance

6.

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

Design

Plan

Implement*

Verify*

Operations

People

*NOTE: We usually see terms like “Coding” and “Testing” here, but Agile works in more places than IT/software.

Product

Design

Plan

Implement*

Verify*

Operations

People

Market

Design

Plan

Implement*

Verify*

Operations

People

Impact

Design

Plan

Implement*

Verify*

Operations

People

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
T1. Design

T1.1

Feature Mapping

T1.2

Iterative Prototyping

T1.3

Unknowns First

T1.4

Checklists

T2. Planning

T2.1

Collaborative Planning

T2.2

Resource Allocation

T2.3

Small Batches

T2.4

Prioritized Delivery

T2.5

Working Sessions

T3. Implementation

T3.1

Daily Collaboration

T3.2

Resource Management

T4. Verification

T4.1

Independent Verify

T4.2

Reproducible Testing

T4.3

Defect Tracking

T5. Operations

T5.1

Independent Test Environment

T5.2

Independent Customer Environment

T5.3

Delivery Tracking

T6. People

T6.1

Collaborative Growth

T6.2

Individual Growth

T6.3

Listening & Appreciation

Product Practices
P1. Design

P1.1

Team of Teams Alignment

P1.2

Iterative Cust Delivery

P1.3

Economic Prioritization

P2. Planning

P2.1

Data-Driven Forecasting

P2.2

Long-Range Planning

P2.3

Collab Depend Planning

P2.4

Stakeholder Reporting

P3. Implementation

P3.1

Implementation Debt

P3.2

Cross-Functional Teams

P3.3

Shared Better Practices

T5. Operations

P4.1

Test First

P4.2

Regression Testing

P4.3

Automated Verification

P4.4

Outcome Verification

P4.5

Direct Customer Testing

P5. Operations

P5.1

Automate Everything

P5.2

Automate Recovery

P5.3

Automation Reporting

P6. People

P6.1

Intrinsic Motivation

P6.2

Integrating Multiple POVs

Now Agile works in more places than IT/software...

…so the names may look unusual.

Practices go by many names…

Team Practices

T1. Design

T1.1

Feature Mapping

T1.2

Iterative Prototyping

T1.3

Unknowns First

T1.4

Checklists

T2. Planning

T2.1

Collaborative Planning

T2.2

Resource Allocation

T2.3

Small Batches

T2.4

Prioritized Delivery

T2.5

Working Sessions

T3. Implement

T3.1

Daily Collaboration

T3.2

Resource Mgmt

Scrum Version

User Story Mapping

Iterative Prototyping

Spikes

Definition of Ready

Planning Poker

Backlog Refinement

Sprints 

Burndown Charts

Sprint Planning

Daily Standup

Repository

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*

Mob Programming*

Repository

Non-IT Version

Flow Chart

Draft Reviews

Discovery Sessions

Scope Definition

Collaborative Planning

Resource Allocation

Wait List 

First In / First Out 

Working Sessions

Daily Collaboration

SharePoint

*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.

We call it: “Choose Your Own Agile Adventure”

Where would you like to go next?

Not every team needs every practice...

...and teams operate at different speeds.