Creating Good Practice Playbooks
Creating Good Practice Playbooks involves developing detailed guides that provide step-by-step instructions and strategies based on established good practices to assist teams in executing their tasks effectively.
Goal
The goal is to provide actionable, detailed guidance that enables teams to implement best practices in their operations, thereby enhancing efficiency and consistency across the organisation.
Context
Stream Teams are all building parts of the product. While there work might not be exactly the same, there are often common processes that are executed across teams. Creating Good Practice Playbooks ensures that teams have access to standardised, proven strategies and methods for executing these processes effectively and they don't have to reinvent the wheel.
Inputs
| Artifact | Description |
|---|---|
| Process Vision | A clear, concise statement of the desired state of the development process and the principles that guide it. |
| Experience | Insights and lessons learned from past feature development or experiences that can inform the creation of effective playbooks. |
Outputs
| Artifact | Description | Benefits |
|---|---|---|
| Good Practice Playbooks | Comprehensive guides that encapsulate good practice strategies and steps for specific functions or challenges. | Ensures teams have clear, practical guidance on applying good practices to their work. |
| Repository Database | A structured database containing all guidelines, playbooks, and templates. | Ensures all teams have consistent access to organisational knowledge. |
Anti-patterns
- Overcomplexity: Creating playbooks that are too detailed or complex, making them difficult to understand and use.
- Lack of Customisation: Failing to consider the diverse needs of different teams, leading to playbooks that are not fully applicable to all situations.
- Mandating Compliance: Forcing teams to follow playbooks without allowing for necessary adaptations based on their unique contexts.