Thumbnail: 

If your organization is not predictably successful in technology projects, there is likely an issue in requirements. CIO’s must take action and own requirements maturity improvement.

They are in the best position to sell requirements maturity improvement to the organization and can greatly help the process by effectively communicating required actions, and ensuring a suitable resources allocation.

This article says there are 6 things your CIO needs to know to help him in his role of requirements change advocate.

Path to success

Ask yourself the question: “Is the business predictably successful in technology endeavors?”

If the answer is anything other than an unqualified “yes”, chances are there is an issue in requirements definition and management maturity that must be addressed and resolved. The issues involved in achieving this goal are by no means simple.

You cannot simply hire a few people, or throw a few training dollars in the direction of improvement. Improving requirements definition and management maturity requires changing a broad cross-section of competencies. Combine the above challenge with the amount of effort needed to bring stakeholders on-board with the initiative, and it’ easy to see why many organizations fail in efforts to make improvement.

The CIO is accountable for being the bridge between business and IT and is focused on more predictably delivering solutions. This results in an inherent focus on maturing requirements definition and management.