To formalize requirements, have one repository where you document requirements. This authoritative resource is maintained by the core team and can vary from a spreadsheet, such as this sample template, to sophisticated requirements tracking applications. Regardless of the tool used, all parties must know that there is one authoritative list and if a perceived requirement is not on the list, then it is not being addressed.
This document outlines the strategy for deploying a standard systems development methodology and its supporting tools to IT project teams. It is a framework for ensuring that the project team understands, applies and measures the effectiveness of the methodology.
This is a high-level example of a Project Charter for implementing a methodology, but the structure and approach will work for many projects. This example is heavy on risks and assumptions, light on budgeting, role descriptions and conflict resolution.
Learn by doing, but be sure you have a winning coach. Mentoring is key to a successful project implementation. Use this guide to get the best out of a methodology guru to mentor your project team in action.
If you are dealing with consultants and sensitive proprietary information, you need a mutual nondisclosure agreement to protect yourself and your business secrets. This document is not a substitute for legal advice, though, so be sure your corporate lawyer takes a good, hard look at any nondisclosure agreement you produce.
ADVERTISEMENT
ADVERTISEMENTS
"Nobody can make you feel inferior without your consent."
