Software Complexity + Human Frailty + Changing Circumstances = ???

If we accept the above formula, why in non agile development methods is there so much emphasis on analysis, planning and change control?

High level planning, such as a feature list (or Product Backlog in Scrum), and an outline plan based on the affordable team size; Yes. Otherwise you’ve no idea what you’re in for.

But a detailed specification and detailed plan? I don’t think so.

Two problems…

First, they give an artificial impression of accuracy, which given the above formula is unlikely to be possible, however firm it seems at the start.

Second, detailed analysis and detailed planning takes a long time, and given the unlikely accuracy, in my experience it’s simply not worth the effort.

Kelly.

One Response to “Software Complexity + Human Frailty + Changing Circumstances = ???”

  1. James says:

    Great question and my answer must be = ‘Risk management’

    1: Software Complexity:
    a) Remove the ‘bells & whistles’ … are they really needed?

    2: Human Frailty:
    a) Include less humans … In my experience reliance on too many ‘others’ holds things up!

    3: Changing Circumstances
    a) Move fast … keeping software simple is really important, does not need to look too flashy because it does the job!

    Personally I think you hit on a few great ideas here and If you/we can reduce risk to our projects we are all the better for it.

Leave a Reply

What is 8 + 7 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”

DAN PULHAM, DIGITAL DIRECTOR
TELSTRA