|
|
|
|
|
by tenpoundhammer
393 days ago
|
|
Have done some of these recently
- Smaller teams are better value/$ spent [Confirmed] - More frequent releases accelerate learning what has real value [No improvement] - Limiting work in progress, solving one problem at a time,increases delivery throughput [Continued] - Cross-functional teams experience fewer bottlenecks and blockers than specialised teams [Confirmed] Empowered, self-organising teams spend less time waiting for decisions and more time getting sh*t done [Confirmed] Additionally, smaller teams 1-3 engineers per project who are empowered are much happier. Side effect was time spent on process, tickets, communication dropped dramatically. Time spent on creating and confirming increased. In a large organization solving your own blockers can be the difference between releasing next week and releasing next quarter. More frequent releases only help in a business where users adopt new features quickly. |
|