|
I once took an "agile developer"role at a Pension Software firm (yes they may be running your pensions) Agile apparently meant Every morning the team stands around for 10 minutes waiting for the head of operations to turn up. Then he tells everyone what they are doing Then we do it. Stand ups are too short to have discussion or any input from the team. and if you want to refactor any code please liase with the head developer who is working off site 300 miles away and he was a "its my baby" dev who refused to accept any changes.. I left after 2 months (I also won an award for my first month there as going above and beyond the call of duty by staying late my first week to help the existing team fix the issues (and i had never seen the code base before)
|
# ¿ Sep 28, 2015 10:56 |
|
|
# ¿ May 10, 2024 18:46 |
|
Contra Duck posted:Hi I'm your new client. I'm very excited that we're going to be doing this agile thing but please take understand that we will need 7-10 days to make even the simplest of decisions. they obviously don't get agile, part of the pain with agile is whilst developers sign up the management is still under the remit of them versus us, rather than we all work together
|
# ¿ Sep 29, 2015 08:36 |
|
OWLS! posted:From an employee perspective, it's an amazing thing. Short, dense meetings with "go offline for the detailed tech stuff after we're done here" is pretty much my gold standard at this point. The meetings we have we do this, but then the people needing to talk never do.
|
# ¿ Sep 4, 2016 13:03 |