Specification Killed The Innovation

This is how innovative and game changing ideas are not born:

Most companies think of their IT as being of strategic importance. So how does it come that this strip is reality for most of us working in the SW-business?

Now this is how it is supposed to be:

I think that the main reasoning behind this is that the specification document should not be used as a driving force in the development process, but as a mere way of documentation. The driving forces are the vision of the client and the ideas of the developer. Getting those together is a major management task of software projects. The developers in turn should structure and process the clients information and be creative. If your managers or developers can’t cut it you might just as well get this spec to an offshore software house.

One Trackback

  1. [...] This post was mentioned on Twitter by Jyrki Saarivaara, Conrad Hesse. Conrad Hesse said: Why #innovation is unknown in the real world of #software projects: http://bit.ly/a3q0k3 #mgmt [...]