Skip to main content

Gimme back my waterfall!

I caught up with a friend, developer and fellow Agile Evangelist over coffee a few days ago. As it happened, he is currently obliged to work on a waterfall project -- working for a service company, you don't always get to choose. So I asked him, what's it like to go back to the waterfall?

His answer: "Right now, I'm having a great time. I don't have to explain myself to my colleagues every day. If want to read a book or blog, or experiment with a couple different approaches to solve a problem, I can! And I don't have to feel guilty at the next Daily Scrum. And if a specification is incomplete or contradictory, all I have to do is tell the Project Leader and I have peace and quiet for a few days while he clears things up with the customer. And of course, if I tell the Project Leader that task X will take 5 days, I have no one bothering me before the time is up. I am much less responsible for the solution. Of course, I do my job conscientiously, but where my responsibility ends, it ends."

"How long till the next release?" I asked. "Oh, about 4 months."

Gee, why doesn't everyone want to move back?

Comments

Franco said…
You will be surprised how many developers like this kind of situation ;o)
Jose Noheda said…
It depends heavily on the motivational aspect of course. In my daytime job I have to admit that waterfall is a bless ;-)
Anonymous said…
Sure he could have a great time...but after 4 months, don't look the quality of the code, the amount of features, the matching between features and the real user requirements...
Peter said…
Personally, I expect 3 months of bliss and at least one month of torture.
Of course developer would have enjoyed and will enjoy to do the same. And I guess all developers would love waterfall methodology. But what happened to the project finally??!!!.

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …