When is Enough, Enough?

by on August 26, 2013 12:00 pm

This summer, I had the pleasure of chatting with a distant cousin who was traveling through town. He is a retired project manager from NASA, but they keep bringing him back as a consultant, so obviously they like his work. I had never dealt with him as an adult, and he was insistent we talk when he learned I was a software developer. He asked me one of the strangest questions I think I have ever heard from a project manager:

“How can I get my developers to stop?”

Now, I’m sure we have all fallen into the trap of wanting to add just one more feature, tweak one more method, to be a bit better. But we also have deadlines, don’t we? And clients that we have to answer to?

It turned out that in my cousin’s case, there was too broad a gulf between the actual consumer of the software and the people developing it. They never spoke to one another. Everything was done through intermediaries. While I’m sure part of this was due to the nature of government work, where almost everything is contracted out (and you can’t have the contractors talking to each other without a government employee being involved), but this seemed more fundamental than that. It was what I thought was the extinct mix of waterfall and cowboy programming.

Calling something “waterfall” has become a severe term of derision in lots of shops these days. And while I think the waterfall process really should be derided, it is getting to the point where processes that aren’t at all “Waterfall” are being labeled as such because someone doesn’t like them. Unfortunately it is much easier to say, and more widely understood than “non-agile” or something similar. And while I don’t have enough information to know if these projects truly were waterfall or not, they were certainly not agile. And throwing an isolated developer into the mix only made the situation worse.

When discussing agile development techniques, the list of benefits is usually skewed to those for the developers. Less time spent in meetings and more time coding. Let the code be the ultimate requirement document. Things like that. What I think gets lost all too often (and far too frequently not utilized) is the engagement of the ultimate consumer (or their representative within the company).

At the end of each sprint, the developers should give the consumer’s stakeholder deployable code with something for them to test. If they sign off on it, it should go into production.

And here’s the important part: further development on that code should STOP. The stakeholder with the responsibility for making that call has said it is good enough. The developers should move on to other tasks in the backlog. If they have ideas for how the just released code could be improved, then that should be added to the backlog and prioritized along with everything else.

Of course, this requires that the stakeholder who is supposed to make the final go/no-go decision has all the relevant data. They can’t approve a new algorithm that hasn’t been stress tested, or a new UI that has only been tested in one environment. It is our job to present them all the facts, and then let them make the decision. And I have found that if you have been open and upfront about all the design choices and their trade-offs, and engaged them in the decision making process, they almost always make what developers would consider the “right” decision. However, we as developers must realize that even when they make the “wrong” decision after getting all the facts, it is our responsibility to implement what they ask for in the best way possible.

Final Thoughts

The agile methodology and extreme programming techniques have given a lot of power back to the regular developers. We get to make a lot more choices about tools and architectural decisions about how things should be done than we did in the bad old (waterfall) days.

But we shouldn’t abuse that power either. As Uncle Ben said, “With great power comes great responsibility.”

We have to remain aware of who our ultimate customer is and keep them happy. If we keep missing deadlines, or don’t get some new feature in a sprint because we are tweaking something that is already good enough, more people will start to ask “How can I get my developers to stop?” And once they get you to stop, they may not ask you to start again, but ask someone else who knows when enough is enough instead.

– Clayton Neff,

  • Share:

8 Responses to “When is Enough, Enough?”

  1. Phil says:

    This is where things like acceptance criteria and TDD can be really helpful. They define the expected checklist, and when that checklist is complete, you’re done.

    • Clayton says:

      I am finding it really difficult to get much buy-in for TDD despite its many advantages. And I think we have to be wary of it making people complacent that they have defined all the requirements by defining the first round of tests. We still have to iterate through the design and implementation, adding and changing tests as needed.

      But you make an excellent point about how TDD can help define what “Done” is more clearly than many other methodologies.

      • Phil says:

        ATDD is a necessary counterpart, and is probably even more important than TDD. That becomes the meta checklist for delivering the feature. You and the client can write that list together, agree on it, and everything is directed to making those scenarios pass.

        That doesn’t mean the list can’t change, but it’ll only change through interaction with the client, and both parties have the same understanding at any given time of what “done” means.

  2. Jerry Horn says:

    I whole-heatedly agree with this article. However, as business processes change, so do systems. I think the trick is trying to determine what tweaks make a material difference to the overall system and ultimately, support the business process. I find that changes will be requested based on an individual’s personal preference. This can create a vicious circle of changes for the sake of changing, not true improvent.

  3. Clayton says:

    I have also run in to the “vicious circle” affect, but I think that is a different problem. That is more a matter of two stakeholders not agreeing on a requirement, and the project manager not using the system to make them agree before creating a backlog item.

    When you don’t have a stakeholder that can truly represent the end user, you will always end up with “best guess” requirements. Sometimes we may not agree with that guess, but it is still our responsibility to code it as specified (perhaps in such a way that will be easy to change later).

  4. Jerry Horn says:

    I had not heard of Gold plating either. I guess the idea is that we can always achieve some sort of perfect solution if we keep working at it. Thanks for the link.

Leave a Reply

Things Twitter is Talking About
  • #HTML5 is a viable technology for the enterprise & a must-know for single page applications. Learn how - #tutorial
    April 24, 2014 at 4:19 PM
  • JSF components can be used to quickly bring up a user interface. Here's a quick example using #ICEFaces:
    April 24, 2014 at 11:35 AM
  • Signed up for Keyhole's free monthly tech newsletter yet? Latest resources compiled to a quick email. Sign up here:
    April 24, 2014 at 10:35 AM
  • code smell: dev practices that leave a stench of inexperience. Avoid it in method implementation with these tips -
    April 23, 2014 at 9:20 PM
  • Tech Night is now! Mark D is presenting to the group on #Grunt 101. Good technology talk, food & team makes for a fantastic night.
    April 23, 2014 at 5:10 PM
  • Single Page Application architectures allow for rich, responsive UIs. #JavaScript is a must-know for SPA - #tutorial
    April 23, 2014 at 2:15 PM
  • Vacuole #Encapsulation aims to minimize the code necessary for routinely verbose data tasks -
    April 23, 2014 at 9:45 AM
  • DYK? We translate our hands-on experience to custom courses to train your dev teams. Our new course on #AngularJS:
    April 23, 2014 at 8:45 AM
  • Interested in #Backbone & #Marionette but not sure where to start? Check out the Marionette-Require-Boilerplate: #SPA
    April 22, 2014 at 4:50 PM
  • Responsive Design can help in giving your users a consistent app experience across devices. Quick tutorial -
    April 22, 2014 at 2:31 PM
  • Tips & tricks to save time in the #Eclipse IDE - (keystroke combos, navigation, time tracking & more)
    April 22, 2014 at 8:40 AM
  • Join us! Looking to add to our team a developer w/ advanced #JavaScript & #NodeJS exp (& love of tech variety). Info:
    April 21, 2014 at 7:35 PM
  • Looking into #ExtJS but don't know where to start? Check out our video tutorial series to find your way around -
    April 21, 2014 at 4:35 PM
  • We've been tinkering with JS library since its public release 4/10. What we've learned so far via a POC app -
    April 21, 2014 at 2:03 PM
  • RT @CompSciFact: Rivest, Shamir, and Adleman published the RSA public key cryptography algorithm in 1978.
    April 21, 2014 at 11:13 AM
  • DYK? When we share/RT/blog/etc, it doesn't mean that Keyhole endorses it - we just like variety of opinions! Info:
    April 19, 2014 at 3:01 PM
  • A huge welcome to Justin Graber who joined the Keyhole team this week!
    April 18, 2014 at 3:25 PM
  • Pssst... @kc_dc early bird pricing ends on Sunday. Shoot us a note if you want to save 10% off of your ticket with our sponsor promo code!
    April 18, 2014 at 2:49 PM
  • Join our team! Looking for a developer w/ advanced #JavaScript & #NodeJS experience (& love of tech variety). Info:
    April 18, 2014 at 11:21 AM
  • .@befamous has huge potential to make HTML5/JS/CSS web pages feel as native apps. Here's our inital tech takeaways -
    April 18, 2014 at 9:50 AM
Keyhole Software
8900 State Line Road, Suite 455
Leawood, KS 66206
ph: 877-521-7769
© 2013 Keyhole Software, LLC. All rights reserved.