vault backup: 2025-01-14 14:37:04

This commit is contained in:
2025-01-14 14:37:04 +01:00
parent 4a341b61b8
commit 98d70224b9

View File

@@ -48,6 +48,34 @@ The main benefits for your organisation:
#### Maturation Phases #### Maturation Phases
1. several sprints to learn scrum, learn small increment, 1. several sprints to learn scrum, learn small increment,
2. over time focus shifts to organisations interaction with teams
3. iteratively teams are transformed. They deliver quickly and change direction quickly, meaning the organization has strategic opportunities to plan and execute differently and better
4. meaning everything gets better and better over time.
#### Summary of Key principles
- **Inspect and Adapt**: Agile is empirical with focus on learning from experience. Meaning the framework should create opportunities to reflect periodically and make adjustments based on experience.
- **Start with Scrum**: might not be the final journey, but is the best structured and best supported place to start.
- **Build Cross-Functional Teams**: The teams should be self managed, meaning they need to include a full skillset to make well informed decisions that are binding to the organisation.
- **Integrate Testers into the Development Team**: Close feedback loop between development and test by having the people work together.
- **Motivate Teams Through Autonomy, Mastery, and Purpose**: Motivation factors are inherently supported: Teams work with Autonomy and to become better over time (Mastery). healthy Agile team and motivated Agile team are strongly intertwined.
- **Develop a Growth Mindset**: Agile teams have a big steady focus on getting better.
- **Develop Business Focus**: Developers should understand the business to fill the gaps in requirements.
- **Tighten Feedback Loops**: Don't take any longer to learn lessons than you need to. This supports more rapid progress from Inspect and Adapt and faster imporvements in Effectiveness.
- **Fix the System, Not the Individual**: If a developer is not performing look for the system problem that is frustrating the person. Usually it's the system, not the people.
- **Increase Team Capacity by Building Individual Capacity**: Team attributes are the combination of individual members attributes and interactions. By strengthening the people, you strengthen the team.
- **Keep Projects Small**: They are easier and more often successful. Not all work can be structured like this, but if you can you should do it.
- **Keep Sprints Short**: they support a frequent inspect and adapt feedback loop and expose problems quickly before they grow into large problems
- **Deliver in Vertical Slices**: Feedback is important and teams get better feedback on their product in vertical slices and thus improve more. This means the business improves more as well.
- **Manage Technical Debt**: Focus on Quality. Managing technical debt supports higher team morale, faster progress and higher quality products.
- **Support Large Agile Projects Through Architecture**: Good architecture even allows large projects to use agile. Good architecture can make a large project feel smaller
- **Minimize the Defect Detection Gap**: The cost of fixing a defect grows with the age of the defect. --> Detecting early and fixing it is cheaper and increases quality.
- **Create and Use a Definition of Done**: a good definition of done helps catch incomplete or faulty work early, minimizing the gap between defect insertion and detection.
- **Maintain a Releasable Level of Quality**: High quality helps catching additional defects that slip through
- **Use Automated Test, Created by the Development Team**: Helps minimizing the defect detection gap. Everyone on the team feels responsible and reinforces that quality is the responsibility of everyone.
- **Refine the Product Backlog**: this ensures the team tackles high priority tasks first and doesn't invent new requirements
- **Create and Use a Definition of Ready**: make sure requirements are truly ready before the team begins implementing them.
- **Automate Repetitive Activities**: You have more benefits when automating repetitive tasks.
- **manage to Outcomes, Not De**
--- ---
```query ```query