85 lines
5.6 KiB
Markdown
85 lines
5.6 KiB
Markdown
---
|
||
title: More Effective Agile by Steve McConnell
|
||
created_date: 2025-01-13
|
||
updated_date: 2025-01-13
|
||
aliases:
|
||
tags:
|
||
- book
|
||
type: book
|
||
book_name: More Effective Agile
|
||
author: Steve McConnell
|
||
status: not_started
|
||
---
|
||
# More Effective Agile by Steve McConnell
|
||
- **🏷️Tags** : #01-2025 #book
|
||
---
|
||
## Summary
|
||
|
||
> [!summary] Summary
|
||
> 3 Sentences only!
|
||
> - What are the main ideas?
|
||
> - If I implemented one idea from this book right now, which one would it be?
|
||
> - How would I describe the book to someone else?
|
||
|
||
---
|
||
## Ideas and Thoughts
|
||
|
||
> [!info]+ Inspiring Questions
|
||
> - Did you think about other concepts from other books?
|
||
> - Do the concepts fit to your past, to your memories?
|
||
> - Can you relive them and reflect them from a different angle?
|
||
|
||
|
||
---
|
||
## Clippings
|
||
|
||
> [!info] Import Clippings from Kindle
|
||
> Annotate Clippings with thoughts and cross references
|
||
|
||
### Enjoy the Fruits of Your Labor
|
||
The agile mindset is about decriminalising mistakes and develop a Growth Mindset. Use mistakes as learning opportunities, Inspect and Adapt, and gradually become better.
|
||
The main benefits for your organisation:
|
||
- teams that stay focused on goals and that are responsive when things change
|
||
- teams that monitor the effectiveness in order to replace ineffective practices with better ones meaning throughput increases over time
|
||
- teams that monitor workflows. they will know where the work is and if it's progressing as it should. Increasing visibility and keeping delivery promises with high quality
|
||
- teams work well with other teams and outside world
|
||
- constant discoveries, but few disruptive surprises. If they appear you find them early and can react to them
|
||
- high quality work at all times and identify opportunities for improvement. High motivation
|
||
|
||
#### Maturation Phases
|
||
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
|
||
More Effective Agile Steve McConnell
|
||
-file: "More Effective Agile by Steve McConnell.md"
|
||
```
|