Analysis is not a four letter word
Understand where you are going before you leave.
Sounds simple enough. And yet despite all the theory and experience of decades of software development, it’s amazing how often projects are pursued in a ‘pioneering’ fashion.
An impatience to start build can be overwhelming, but projects routinely fail because insufficient thought and preparation is done before cutting code.
For the project team to work effectively, developers need to know where their work fits into the whole and also what business needs they are aiming to satisfy.
A failure to adequately comprehend and define how the solution will acheive the business objectives and ‘realise the benefits’ is a big risk and can easily mean the project will be late, blow the budget and leave an unhappy customer in it’s wake.