Then that confirms my OP - everyone wants to embrace the cosmetic pieces but the actual meat of Agile is ignored.
Every control has to have consequences, or else bad behavior has no cost. Your organization is addicted to what the calendar says, and the software is neglected. The consequences are suboptimal productivity and/or quality. Appearing to work has more value than completing work.
No software process is immune to leadership failures.
Wasting time? Measuring twice and cutting once is done because it saves time. As a shirt I saw recently said, "weeks of programming saves hours of planning".
Comments
Then that confirms my OP - everyone wants to embrace the cosmetic pieces but the actual meat of Agile is ignored.
Every control has to have consequences, or else bad behavior has no cost. Your organization is addicted to what the calendar says, and the software is neglected. The consequences are suboptimal productivity and/or quality. Appearing to work has more value than completing work.
No software process is immune to leadership failures.
Wasting time? Measuring twice and cutting once is done because it saves time. As a shirt I saw recently said, "weeks of programming saves hours of planning".