|
Drythe posted:My work claims to the death we are agile despite me even giving all our management a presentation over what agile is and how we are not and what we can do to work towards it. We still require the business to give all requirements at the start, refuse to talk to them to clarify anything, only ever do one release of a product, and testing is still only at the end. We call that "sloganized agile". It usually happens in an old waterfall style development company with alot of lifer middle management. The terms used in agile are substituted in for old existing practices, (i.e. meetings become standups, design specs become user stories, managers become dual product owners/scrum masters because they're just that good...) ..and I work at that company! Everything's a disaster. The transparency that agile brings to the table was hijacked into micromanagement every morning where managers show up at stand ups and tell everyone they're doing it wrong. The moment a team starts showing any signs of success middle management is threatened so they work to break up the teams. Things have gotten so bad developers are required to fill out secret surveys at the end of a sprint detailing who they thought the best and worst performers on their team were and deliver it straight to management. We've something called a Definition of Done that must be met before a team can call a user story done. At some point that became optional because "We don't have time." Following that are celebratory emails about how everything was done on time. I got a scrum master certification out of it, which looks good on a resume but is virtually worthless as an indicator of skill or talent. It was a 2 day course outlining agile and scrum practices, that's about it. No tests to pass, etc. Fatz fucked around with this message at 17:44 on Jan 10, 2016 |
#
¿
Jan 10, 2016 17:31
|
|
|
|
| # ¿ Apr 28, 2024 10:16 |
|