If we think of a tech company as a factory, then just like all factories, by streamlining the process we can improve safety and speed up delivery.

Here’s an idea to experiment with.

An agile process “drill”.

A workshop where we track a single requirement, from customer request to delivery, end to end.

Gathering feedback on each step can reveal many unexpected constraints in the workflow.

Is the hand-over process slow or lossy? Are code reviews taking too long? Are we unnecessarily waiting for individuals to make certain decisions? Do we simply not know who to signal next?

Example Worksheet.

Using a task tracking tool like JIRA or trello the following can be efficiently generated.

#### Requirement

"Bulk ordering of products."

###  Chronology

- Customer ({start, end}): REQUIREMENT
- CPO ({start, end}): HYPOTHESIS
- UI ({start, end}): RESEARCH
- SQUAD ({start, end}): ALLOCATION
- PM ({start, end}): REFINEMENT
- CX ({start, end}): REQUIREMENTS
- DATA ({start, end}): RESEARCH
- LEGAL ({start, end}): RISK
- DESIGN ({start, end}): LAYOUT
- ... ???
- SQUAD ({start, end}): REFINEMENT
- SQUAD ({start, end}): ESTIMATION
- CPO ({start, end}): PRIORITIZATION
- SQUAD ({start, end}): ALLOCATION
- ENGINEERING ({start, end}): CODE
- ENGINEERING ({start, end}): REVIEW
- QA ({start, end}): TEST
- SQUAD ({start, end}): RELEASE
- CUSTOMER ({start, end}): EXECUTE
- CX ({start, end}): TRAINING
- CPO ({start, end}): DONE

### Time Summary

- Initiation: 01/04/2018 16:00:00
- Completion: 04/08/2018 12:06:00
- Active working hours: 25hrs.
- Idle queuing hours: 600hrs.

Initiation, completion, active working hours, and idle queueing time are a powerful learning metric.

The goal is to help an organization to learn more about itself across disciplines and do more with less in a rapidly changing world.