Now getting to specifics:
>Here's a process that works: leave me alone to get the job done, and I'll report progress to you regularly. Leave the manager out of my day to day activities.
I do not think agile requires the manager be involved in day to day activities. If he's insisting on it, he's the problem - not agile.
Reporting progress daily is reporting progress "regularly". Having said that, I do not think agile requires daily progress reports.
As for leaving you alone - that's great if your work doesn't depend on anyone and no one depends on your work. It works if your work is small enough that it can be done by one person. Rarely is that true. But if it is for your work, by all means it's a fine approach.
>That's how I'd fix it. In fact I became a contractor so I didn't have to do agile any more. Now I get tremendous amounts of work done, using my experience and talent to attack root causes and write the critical code to get the job done.
There's plenty of work that can be done that way. I think you'll find plenty that cannot. I don't think you can build a standards observing web browser as a contractor.
And as for 'small units', that's an agile myth. Many important tasks take concentrated effort over many days or weeks. 'Small enough for one person' doesn't quite cover it. It about how many folks can understand the topic without being there with you in the trenches. Its pointless to go to standup and say "I've a problem with logging in the presence of disk errors, where the driver interacts with the log buffering by generating more log messages". Nobody going to offer useful help without actually recapitulating the work you've already done. So what's the point?
I admit there are many generate-the-web-page-of-the-day tasks that can be turned into assembly-line work. Sadly there are too many jobs like that. I'm not working at any of them.
This is commonly claimed, but I've never seen an example (in software) that stood up to scrutiny. People can always find a way to deliver some useful, visible value within two weeks of one person's work if they spend 5 minutes actually trying to think of a way to do it.
> Its pointless to go to standup and say "I've a problem with logging in the presence of disk errors, where the driver interacts with the log buffering by generating more log messages". Nobody going to offer useful help without actually recapitulating the work you've already done. So what's the point?
If you're making progress on your task and just need to spend some more time, it's fine to just say as much. If you've been stuck for a while, maybe it is time to ask someone else to come work on the problem with you - or at least time to warn the end client that what you're doing is going to be late. Taking a few minutes once a day to look back and decide whether you're actually making any progress or need to stop and reassess is about the right cadence, rather than blindly bashing your head against the problem for weeks or months.
(Sometimes bashing your head against the problem for weeks or months is the right thing, but it should be an explicit, conscious decision to do that)
And the flipside is that it gives people who need input from you a scheduled point to ask for it, rather than interrupting your work. Presumably you're working on the same product with these people and so what you do affects each other - otherwise why are you in the same standup or even the same team?
I think you're confusing me with someone who is a big fan of agile.
>And as for 'small units', that's an agile myth. Many important tasks take concentrated effort over many days or weeks.
Nothing in my comment suggested small work means it can't take days or weeks.
Note the following phrases in my comment:
>It may for you,
>But if it is for your work, by all means it's a fine approach.
>There's plenty of work that can be done that way.
I've repeatedly given hints that I don't think agile is a universally valid approach. I have my own criticisms of it. I left my last team due to some of the problems that agile presented. At the same time, I've been in teams where agile definitely would be an improvement and I would recommend it to them.
You are coming across as someone who is not OK unless everyone agrees with you that agile sucks and is always a poor idea. Sorry - I don't agree. Just please don't characterize those who disagree with you as agile fans.
Finally, let me address this (said by others in this thread):
>Yeah its always somebody's fault, never agile. That's what makes this classic No True Scotsman.
No True Scotsman applies only when there is not a clear definition or source. It arises from vague notions, which results in everyone having their own definition of what a Scotsman is to the benefit of their own argument. This is not what is going on here. In fact, the argument applies more to those who are criticizing agile as they are the ones who are creating different definitions of agile.
What is agile is not ambiguous. This document is what agile is:
http://agilemanifesto.org/principles.html
Criticizing what is not in there is like me criticizing the US Constitution because there exist some silly laws in my state. And then when people point out the constitution doesn't mandate those laws, responding with "That's just a No True Scotsman!"
If its not exactly what NTS is then lets use some other phrase that better captures "Lets continue to apologize for the failure to implement the agile manifesto effectively in many situations". An effective business practice has to be able to be put into practice. Without a large potential-energy-hill of retraining and right-think and group buyin. I don't think agile is that thing. I'm sure some small groups have successfully done something they call agile (not yet convinced its by simply adhering to the manifesto), that's great for all who succeeded.
But the war stories of failure are pervasive.
I do not find them to be any more pervasive than non-agile methodologies. And success stories do exist, so it clearly is not an unqualified failure. This looks like a case of "We can hate it because someone gave a name to it".
Hah, I almost said that that's where this genre of agile criticism seems to come from: the coder who believes they can produce a good product by writing good code without interacting with a customer and so regards any process as an impediment, and isn't actually attacking agile so much as attacking the very concept of process. What you propose is a good way to produce elegant code that doesn't actually do what the customer wanted at all; even if you personally can magically understand the requirements every time, a customer (or a manager) is right to be skeptical, because most programmers can't.
Agile explicitly puts people in my way, regularly, and with demands that I report progress with imaginary metrics.
That's how I'd fix it. In fact I became a contractor so I didn't have to do agile any more. Now I get tremendous amounts of work done, using my experience and talent to attack root causes and write the critical code to get the job done.
I see its a whole different attitude from Agile, I get that. But I'm adamant that I don't want what Agile does.