Page 1 of 1

Agile Assessment

Posted: June 9 15, 7:52 am
by Joe Shlabotnik
3 hours this morning. A consultant blah, blah, blahing about our agile process and us taking a survey to assess and 'coach' us. If I'm a good boy, maybe there's a trophy in it at the end!

God I hate this [expletive].

Re: Agile Assessment

Posted: June 9 15, 8:17 am
by Fat_Bulldog
Yuck. We have agile audits here.

Re: Agile Assessment

Posted: June 9 15, 8:52 am
by GeddyWrox
I hate Agile.

Re: Agile Assessment

Posted: June 9 15, 9:20 am
by Joe Shlabotnik
I don't mind the scrumming, the collaboration, the breakdown into 2-week sprints. But do we have to do all the introspection [expletive]? It's like we spend 40% of our time gazing at our navels. bleah.

Re: Agile Assessment

Posted: June 9 15, 9:26 am
by Fat_Bulldog
We do 3 week sprints which I find better because we have more time to work on the stories vs. planning / introspection.

I don't mind the way work is done and planned out but yeah, the retro / introspection crap gets tiresome.

Re: Agile Assessment

Posted: June 9 15, 9:31 am
by Jocephus
whatever it is, sounds awful

Re: Agile Assessment

Posted: June 9 15, 10:15 am
by cardsfantx
though this was a workout thread.

thank god i own my own business.

Re: Agile Assessment

Posted: June 9 15, 11:57 am
by IMADreamer
I don't even know what any of this means.

Re: Agile Assessment

Posted: June 9 15, 12:18 pm
by Joe Shlabotnik
IMADreamer wrote:I don't even know what any of this means.
It's a software development methodology that is The Latest Thing.

Re: Agile Assessment

Posted: June 9 15, 12:58 pm
by GeddyWrox
Joe Shlabotnik wrote:
IMADreamer wrote:I don't even know what any of this means.
It's a software development methodology that is The Latest Thing.
To elaborate, you do these things called "sprints" -- which are usually two or three weeks. So that means every sprint cycle, you are pushing whatever crap you can sling together. It may work in some environments (like a high visibility software product that needs lots of enhancements) but it's HIGHLY dependent on strong, self-sufficient coders. And it feels like you never have time to catch your breath. As soon as you finish a sprint, you immediately scope out the next one which starts right away.

My biggest beef with it is the fact that my clients all thought they needed to be doing Agile, but my line of IT doesn't fit into that structure well. Creating a data warehouse and business analytics requires a large foundation to be built first. Once you have that solid foundation, then sure, measure my progress in two week increments, but get the [expletive] out of my face until the basic foundation is built and solid.