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 methodsteam 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

don't let broken stories wreck your team's velocity

Capturing requirements in Agile stories is finicky business. Stories need to be just the right size and shape, have the right bits of detail, point to a clear outcome. They must capture the who, what, and why in a way that speaks unequivocally to the user and to the team. Badly written user stories will slow down your team in any number of ways. A few recommendations... Get the right people writing the story. Even if you've done lots of requirements gathering, or the functionality seems like a no-brainer, don't assume that you have sufficient information to compose stories without stakeholder participation. In fact if at all possible, the stakeholders should do the writing. You are there to ask questions and help clarify. Without this collaboration, you will end up going into iteration planning with hobgoblins, not real stories. The team then must devote time to figuring out what's actually needed, returning to the stakeholder with lots of questions, rewriting and

Announcing the 45th Eastern Primitive Rendezvous

The 45th Eastern Primitive Rendezvous takes place September 23-October 1, 2022.   For more information, visit the official EPR website and Facebook group . We will be hosting the 45th Eastern Primitive Rendezvous on our family farm, near East Smithfield, PA. The dates are September 23 - October 1, 2022.  This is a living-history event depicting 18th-century activities. Visitors can tour the camp each day from 10 a.m. to 4 p.m.  Tuesday, September 27 is School Tours Day, during which we welcome classes from all of the area schools. Campers need to preregister ( ), and period-correct clothing and gear are required.  For the exact location and more details, visit the  official EPR website  and Facebook group . For those of you who attended the 2017 EPR, this is the same location.

get it done with trello, part ii

Everyone likes to think that the meeting they're sitting in is productive and staying on track. One of the best things about using a Kanban system is that it provides a highly visual representation of your team's progress. I've found that Trello works great for conducting meetings, work sessions, and other group activities. After all, what is a meeting but a short-duration collaborative project? If you go into every meeting with an agenda — as you should — then you have a predefined set of items for the To Do column. Then it is a matter of simply moving them through the steps required to bring them to conclusion. Furthermore, you can use Trello features such as commenting and voting to capture all sorts of information during the session. Here are a couple of the meetings and work sessions we handle using Trello: Agile Iteration Planning The main part of our Iteration Planning is done by the entire team. Once that is completed, the Scrum Master takes care of a