Lost in Specifications
Each Information System project needs detailed specifications (functional, technical, ). In complex and dynamic business environment it is not an easy task to make stabile detailed specification. There are simple many hidden variables that might affect your specification, because companies are completely process and information interrelated. Everything affects everything, there are no information autonomous parts – closed systems. Simple change in one logistic process might affect financial statement, change in customer care might affect technical production systems, change of one functionality in ERP will affect somebody’s ERP functionality in totally different organizational division. Information connect and integrate internal company information flow.
In complex company environment with many core production systems, many processes and large product portfolio detailed specification for development of any information system will be large and complex. Production of detailed specification will acquire many workshops and participants, and it is easy to fail to include certain portion of important information. Actually, it for sure.
Certain project leaders fail in trap of iterative upgrade of specification due to fear of missing something important. This is legitimate fear.
Disadvantage of many iterative specification upgrade is that they require time, and to enlarge planned specification finalization date. Well, this might mean to postpone budget usage for dedicated task, your project.
What to say, if you do not use your budget, somebody else will. And that is not an illusion, it is so easy to lose budget. Is over detailed specification worth of budget loss?