Quickie: Coding to Other Things Ratio

When building a software-based product or service (not in itself a sound thing to do, see #NoSoftware), how much time and effort goes into coding vs other things like:

  • Requirements gathering
  • Architcture
  • Design (of various sorts)
  • Wranging tools
  • UI and UX
  • Testing
  • Documentation
  • Meetings
  • Marketing-related
  • Debugging
  • Etc.?

I’ve long held the view that 10% is a sound number. Your view/experience?

1 comment
  1. Andrew Webster said:

    Sounds about right. It’s a problem with Agile-washing – management throw Agile at their developers, as if that is the only bottleneck in a value stream that jumps around all over the place, then they complain that “Agile doesn’t work”. In a complex, emergent market and workplace, the systemic constraints are all over the shop and change all the time, and mostly originate in folks’ heads or between folks’ heads!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: