A meeting is an event at which the minutes are kept and the hours are lost

Apps Development intangible nature cuts in. It’s very difficult to see what value a software feature has until you see it for real. This Leads to the ironic point that people expect that requirement should be changeable.

But even if you could settle all that & really could get an accurate & stable set of requirements, you’re probably still doomed.

What might be a good set of requirements now, is not a good set in six months time. Meaning: - If you cannot get stable requirements you cannot get a predictable plan.

There are some developments where predictability is possible. However I don’t think much business software fits into that category.

One of the big dangers is to pretend that you can follow a predictable process when you cannot.

People who work on METHODOLOGY BASIS are not very good at identifying boundary conditions: the places where the methodology passes from appropriate to inappropriate.

The most important & still difficult part is to know accurately where we are.

We need an honest feedback which can tell us what the situation is at frequent intervals.

The key to this feedback is iterative development; to produce versions (working samples) of the final system that have a subset of the required features they should be fully integrated & as careful tested as a final delivery.

The point of this is that there is nothing like a tested – integrated system for bringing a forceful dose of reality into any project.

Best Regards  ·  Mit freundlichem Gruß · Cordialmente ·

André Vondran

Best Regards · Mit freundlichem Gruß · Cordialmente · 

André Vondran

Think Green! Please don’t print if it’s not necessary.

Follow Me on Instagram