It’s said that a mechanic should never work on his own car, a doctor never diagnose himself and a builder never gets around to fixing his own house. But when it comes to business analysts analysing their own methods we often stumble blindly into the same traps that we attempt to protect our customers from, blissfully unaware that we are ignoring our own best practices and forgetting to open our own tool box.

Then, after inspired beginnings, one year down the track we wonder why, in hindsight, we have made little more progress than an updated template or two.

So here’s a pragmatic five step approach designed to support rapid implementation of an analysis framework, as a stepping stone towards creating a centre of excellence in your organisation.

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. CIOs 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. There are 6 things your CIO needs to know to help him/her in their role of requirements change advocate.