• Skip to primary navigation
  • Skip to main content

Scruffy Writer

be scruffy

  • Home
  • How to be Scruffy
  • Be Kind
  • Blog
  • Show Search
Hide Search

Agile is Broken

J. C. Wrenn · September 23, 2022 · Leave a Comment

Well, in the current software development market it is. Let me explain.

People are changing jobs more now than ever before in the development world, making relationships more transient. With remote work, the relationships are becoming shallower. This is bad for Agile, because the Agile framework fails when developers are frequently being swapped out. Consider these principles stated in the Agile Manifesto:

“Individuals and interactions over processes and tools”

When there is little focus on processes and tools, roll-ons take a long time. Not helpful in a market of job hopping. Getting a developer up to speed is very easy when you can tell him exactly what your processes and tools are. And since everyone on the team uses the same tools, they are all able to help.

“Working software over comprehensive documentation”

Have you had a key developer leave your organization and leave little documentation about the great software they wrote? How’s it going for that new developer? How will it go for the developer who replaces this one next year?

“Customer collaboration over contract negotiation”

Customers love it when work gets done. Do you know what they don’t love? Constantly meeting the new developer they’ll be working with.

“Responding to change over following a plan”

Responding to change PRODUCTIVELY often requires the person who is responding to have a good understanding of where you have been. This works great when a developer has been on a project for years and understands its background. But when there is employee turnover, it’s very valuable to have a documented plan to show them where you’ve been, where you are, and where you’re going.

The more consistency you have within your team and the processes they follow, the faster they can change the product they are building.

A key feature of Agile is the ability for the team to give somewhat accurate estimates of when features can be delivered. This depends on a good velocity measurement, which depends on consistency within the team.

Related

The Simplest Solution

Last week my headphones started misbehaving in a very annoying way. I could only hear sound out of the right earphone. I tried debugging it with my standard options for fixing all things computer: reset stuff. First the headphones, several times off, and then on. Disconnect bluetooth, reconnect. Reset my computer, then try all the […]

Dumbbell-only Exercises for Weightlifting

It is amazing how many great exercises you can do with just free weights / dumbbells / body weight. Don’t let cost or travel keep you from building muscle. Here are some winners for getting a great exercise in with just dumbbells. We’ve already made the case for why you should be lifting weights. And […]

Your Workspace is Worse Than You Think

Waste One striking thing Paul Akers says is that humans are waste factories. One of the key skills he challenges readers to learn in his book “2 Second Lean” is to see waste. That’s a whole other topic, but for now, let’s just start with this. Our work is full of waste. While it clearly […]

XFacebookLinkedInEmail

Uncategorized

Reader Interactions

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Interested in blogging on Scruffy Writer? Learn More

Scruffy Writer

Copyright © 2025 Scruffy Writer