or how we got playful in search of a remote condition monitoring solution. In our continuing series of posts about the different stages that a software development project goes through from start to finish we constantly find ourselves saying “every project is different and we have to vary our approach accordingly". At one end of the spectrum we have projects where the requirements are very well defined, everyone has a clear picture of what the solution will look like, and the route for getting there is can be described accurately at the outset. At the other, however, are projects where the requirements are vague, it’s not clear what shape the solution will take and there’s no prescribed route for arriving at the answer. The first type requires a systematic and formalised approach, the second calls for imagination and creative problem solving capabilities.
28 11, 2014