We don't bite newbies here... much | |
PerlMonks |
Re^5: Beyond Agile: Subsidiarity as a Team and Software Design Principleby chacham (Prior) |
on Jul 27, 2015 at 13:19 UTC ( [id://1136454]=note: print w/replies, xml ) | Need Help?? |
in many cases they will But what changes? The approach, the rules, or the UI? Otherwise, why release again? To ensure the team's existence. It is sad how often this is the primary motivator in large companies. You actually get fewer of these changes per release if you release more often. That minimizes scope creep during the release. Customer fatigue over changes? Customers generally do not like change in their routines. Release more often and they dread any changes that aren't the bare minimum of what they asked for. New releases also tend to break things.
In Section
Meditations
|
|