- Recognize the expectations of business sponsors.
- Identify the true (not derived) cost benefits of IT projects.
- Review how business values will be measured. Without quantitative measures, there's no way to take corrective action.
- Define the roles and responsibilities of every employee, a prerequisite for accountability.
- Capture requirements for compliance with regulations, policies and procedures. "In terms of information architecture, compliance lets you do a better job," says Hazra.
- Agree on periodic milestone reviews, inspections and deliverables.
- Build and manage ground rules with incremental improvements from lessons learned. This offers a consistent way to manage relationships between business and IT groups.
This was first published in October 2005