AGILE

[nomadd]

You're not in retail are you?

Good god no. Did Retail once. Worst contract in 25 years of contracting. Never, ever again.

[DigitalUser]

"Agile" is among the terms I have in my contracts-to-email exclusions list. Its mere mention in an architect/developer spec suggests a culture of micromanagement and an atmosphere in which I would not enjoy working.

What makes you say that? It should encourage self-organisation (assuming the ScrumMaster allows this to happen) and therefore micromanagement wouldn't be an issue?

[darmstadt]

Software Development Life Cycle, not Syncronous Data Link Control.

My advice would be to stay out of threads you don't understand Dear. It makes you look like a know-it-all idiot.

Or a sockie.

Sadly I thought of Synchronous Data Link Control because I've never heard of the other one and that's a real problem in computing with too many TLAs being reused. I agree with your last sentence though

[cojak]

Sadly I thought of Synchronous Data Link Control because I've never heard of the other one and that's a real problem in computing with too many TLAs being reused. I agree with your last sentence though

It's all about context DS

[magicbuttons]

Sadly I thought of Synchronous Data Link Control because I've never heard of the other one and that's a real problem in computing with too many TLAs being reused.

FLA in this case, surely?

What makes you say that? It should encourage self-organisation (assuming the ScrumMaster allows this to happen) and therefore micromanagement wouldn't be an issue?

In my (admittedly limited) experience of Agile, it seems to involve more talking than doing, more meetings than necessary and more need to detail the minutiae than can be justified. Good developers don't need that, they just need a list of deliverables, a framework, a timescale and a bottomless supply of coffee.

Maybe I've just never seen it implemented properly, but I don't (yet) have any desire or need to find out.

[tranceporter]

FLA in this case, surely?



In my (admittedly limited) experience of Agile, it seems to involve more talking than doing, more meetings than necessary and more need to detail the minutiae than can be justified. Good developers don't need that, they just need a list of deliverables, a framework, a timescale and a bottomless supply of coffee.

Maybe I've just never seen it implemented properly, but I don't (yet) have any desire or need to find out.

It all depends on the way Agile is implemented. I have seen places where the morning standups drag on from anything between 30 -45 mins depending on the number of people involved. Not one of the things I look forward to as soon as enter the workplace.

[GB9]

It all depends on the way Agile is implemented. I have seen places where the morning standups drag on from anything between 30 -45 mins depending on the number of people involved. Not one of the things I look forward to as soon as enter the workplace.

I've seen a team of circa 20 standing around for over an hour every day at my last place. WTF were they doing?

[jmo21]

I've seen a team of circa 20 standing around for over an hour every day at my last place. WTF were they doing?

I've seen similar. Always turns into discussions over how to solve everyone's blocking issues and wastes everyone's time

[The Spartan]

Has anyone done planning poker?

[DigitalUser]

Re: AGILE

I've seen a team of circa 20 standing around for over an hour every day at my last place. WTF were they doing?

Misunderstanding Scrum by the sounds of it. Anything above a size of 8 and you should be looking to split your teams into smaller groups. The daily stand up should be timeboxed to 15 minutes. If it's going consistently over then you have problems with your process.

Sent from my Nexus 4 using Tapatalk 2