Skip to main content

is your team using fake agile?

So, your team has been practicing Agile for a while, but it's not making a whole lot of difference.
Excessive planning sucks up weeks of time before the work even starts. Releases still take forever to accomplish, and you are not delivering value to the customer but once every few months. Iterations don't stay inside their time box but straggle all over the place. Has anything really changed?

Maybe not. Because maybe you are using Fake Agile.

In the big and overlapping world of The Agiles and their ilk, teams can adopt and fine tune a combination methods—team roles from Scrum, user stories from Lean, project boards from Kanban, pair programming from Extreme.

But that does not mean you can borrow one or two techniques and call yourself Agile. You absolutely need to put in place the following:
  • An iterative process in which the customer is an integral part of the team. Base changes and enhancements on customer feedback. Then do it again. And again. 
  • A team environment in which information is shared regularly and readily, cooperation and collaboration are the norm, and work is transparent. This must take precedence over feeding  precious time and energy into extensive planning processes and the unwieldy tools thereof. In fact, do away with the latter altogether. 
  • A process in which releases delivering business value happen early and often.  Stop messing around with long-range plans and milestones and start providing your customers with working software. Or magazine issues. Or new websites. Or bicycles. Whatever your team's raison d'ĂȘtre is, it is not creating milestones. This is important. Repeat after me: A milestone is not a product.
  • Enough discipline and backbone to stick with the Agile process. When politics and whims threaten your team's velocity, when somebody asks you to start writing lengthy weekly progress reports, when a team member turns cowboy, be strong. Push back.
So, if Agile isn't working for you, ask yourself if what you are really practicing is AgileBut.

"We're practicing Agile, but no, we don't really have anybody in the Product Owner role."

"We're using Agile, but we're still putting a lot of time into planning documents and progress reports."

"We're practicing Agile, but management frequently pulls us off onto other projects in the middle of iterations."

"We're doing Agile, but we actually haven't gotten around to changing our coding practices."

"We're an Agile team, but some of us work outside iterations or skip ahead to future iteration work when we get bored."

"We're doing Agile. In combination with Waterfall."

You get the idea.

Further Reading

Popular posts from this blog

the case for incremental redesign: part ii

If you are in any way responsible for a Web site, you should have some understanding of the principles of Extreme Programming . Cultivated as a discipline of software development, it is a combination of ensuring that designs remain uncomplicated, centering changes around user requirements, and employing the concept of the "Whole Team." The result is that small changes are released as they are needed - and endorsed - by the client. Not surprisingly, Extreme Programming speaks well to Web management. Consider its core values: simplicity, communication, feedback, and courage. These are the bedrock incremental redesign. Simplicity - Integrate all site changes in small doses. Avoid tectonic disruption of the entire Web presence. Document faithfully, but do not get bogged down in over-documenting. Or overplanning. Leverage reusable objects. Better yet, get the site into a content management system - one that is scaled to its requirements. Eliminate unmanageable code morass by fol...

replicate, replicate, replicate

Aside from the usual reasons why it's silly to duplicate static content from Web page to Web page, here is yet another: If your Web site has content copied and pasted from one page to another, it is very likely that Google is filtering out some or all of the involved Web pages from search results. The reason: The Google search engine does its best to optimize user experience by returning unique content. Because no one wants search results listing page after page of the same stuff. always crashing in the same car: recurring mistakes and misuses of the web Higher Education and other organizational Web sites tend to needlessly replicate content. This happens perhaps most frequently when information is repurposed as marketing material. The same content ends up appearing at its original source as well as at one or two marketing pages. Unfortunately, if this marketing material resides above the core content in the site hierarchy - and it usually does - it can end up replacing the core ...