Most of us know what an Analysis phase is, and we usually explain it as the execution of activities to demystify the customer's requirements and business processes in greater detail—the "What in detail" so to speak. Is that all?
By kicking off the Analysis phase, we start with the real implementation of the project. A good start will set the tone for our further implementation. The question, What is the purpose of the Analysis phase?, is usually responded to with the following answer: To further analyze and document the customer's requirements. Sounds right, or is it?
This answer is quite incomplete as it neglects the important function of starting the project. This is where we start our engines, set our course, and take off. In aviation, the departure is considered to be complex and critical. This is not really different in software implementation projects—the beginning is always crucial. In the Analysis phase, we are not only...