Difference between revisions of "Operations review"
Jump to navigation
Jump to search
(Source: Kanban—Successful Evolutionary Change for Your Technology Business, David Anderson) |
m (Added some bullets.) |
||
Line 1: | Line 1: | ||
Operations Review: | Operations Review: | ||
*reminds everyone that we are running a business; | *reminds everyone that we are running a business; | ||
*presents a summary of the overall performance for the month; | |||
**budget details; | |||
**throughput; | |||
**headcount; | |||
*takes place on second Friday of the subsequent month so that the financial data after the books for the prior month are closed; | |||
*compares planned versus actual numbers; | |||
*is the feedback loop between adjacent layers in the holarchy: | *is the feedback loop between adjacent layers in the holarchy: | ||
**the Check in the PDCA-cycle; | **the Check in the PDCA-cycle; |
Revision as of 10:06, 5 March 2013
Operations Review:
- reminds everyone that we are running a business;
- presents a summary of the overall performance for the month;
- budget details;
- throughput;
- headcount;
- takes place on second Friday of the subsequent month so that the financial data after the books for the prior month are closed;
- compares planned versus actual numbers;
- is the feedback loop between adjacent layers in the holarchy:
- the Check in the PDCA-cycle;
- the Measure in Sociocracy;
- Sprint Review Meeting in Scrum;
- Release Review Meeting in Scrum.
A mini Operations Review:
- is an objective, data-driven retrospective on the squad's or organization’s performance rather than the more subjective, anecdotal, qualitative management.
- is above and beyond any one sprint or project;
- sets an expectation;
- provides the feedback loop that enables growth of organizational maturity and organization- level continuous improvement.
- reviews data like:
- defect rates
- average lead time distribution
- throughput
- value-added efficiency, and, occasionally,
- a specific report that would drill into some aspect of our process on which the business needs more information
- wraps up with questions & answers, comments, and suggestions from the floor for a few minutes.
Source:
- Kanban—Successful Evolutionary Change for Your Technology Business, David Anderson