DEV Community

Discussion on: Hands-on with the app that broke the Iowa caucus

Collapse
 
jwp profile image
John Peters

This is the signature of the age-old IT problem of agreeing to due-dates before knowing what is needed to complete the job.

It usually happens from the top down: Someone at the top asks someone else at the top "How long do you think this will take?" the answer is always "It's a simple request, which should take a month, but we'll be generous and assume it will take three months". The funds are approved on the generous three month estimate. The contracts are signed and the whole project launch (with no way of getting off the ground) is under-way.

The developers get going and really really want to be successful but alas today's complex world gets in the way.

As mentioned at the birth of Agile, this is not the way to do IT. There's too much complexity, lack of specifications, having to learn new technology, environments (multiple devices).

The only proper way to do this today is to sign a long term contract and agree to continuous delivery until the product owners are satisfied. Product Owners should never be satisfied without QA of their product. If they go live with a defective product are they responsible?

It's just a repeat of what we already know doesn't work and never has worked, but we keep going back to the old SDLC methodology. Will we ever learn?

(For the record: I'm not a democrat)