Getting the Requirements Right is Half the Battle
Conclusion: Immediately after the project Kick Off meetings, project managers find it tempting to hit the ground running and tackle tasks identified straight away to communicate a sense of urgency. However, without a comprehensive statement of requirements and having got consensus to them from stakeholders, the probability of design or programming rework is high.
Set out below is a process for capturing requirements and getting consensus to them from business managers. I have used the process successfully many times. It precedes, and must not be confused with, the JAD (Joint Application Design) activity.
About The Advisor
Alan Hansell is an IBRS advisor who focuses on IT and business management. Alan is able to critique and comment on IT and business management trends, ways to justify and maximise the benefits from IT-related investment, IS management development and the role of the CIO. Alan has extensive experience in IT management, consulting and advising senior managers in matters related to IT investment. He was a Director in Gartner's Executive program and adviser to over 50 CIOs and business managers and before joining Gartner a consultant with DMR Group. He also worked as an IS professional, manager and industry consultant for IBM for nearly 30 years. Alan is a CPA and Associate of Governance Institute of Australia.