A Practical Approach for IT Governance

The New Management Paradigm

with 2 comments

Archer holds the bow that represents project management triangle.In the past we have constantly used project scope, quality, schedule and cost as drivers for selecting and managing our technology initiatives.  We subscribed to the SDLC model where we attempted to incorporate these drivers in our planning and execution phase.  We recognized quickly that risk was an important aspect of our decision making and added that as a critical component of our management and decision frameworks.

While these models still have relevance, life cycles are shrinking.  It took over a decade to bring new products to market.  Today it is less than a few years.  Take a look at Uber and its phenomenal success in just a couple of years.  Enterprises need to be nimble – yet, it is not easy to ignore cost, quality, time or the scope/features of the technology initiative.  Is there a better paradigm?

Factors Affecting Projects

Agile models have relied on developing technology aligned to user needs and budgets, but have failed to provide a decision framework to choose between alternative technology initiatives.

In the new paradigm, I propose to reuse some of the soft factors that were not explicitly used in managing technology initiatives.  The four suggested factors are: constraints (as opposed to time), budget (as opposed to cost), value (as opposed to scope) and satisfaction (as opposed to quality).  Traditional schedules are difficult to adhere to as there will always be change.  Constraints can help with time lines and schedules within a project. Budget is a realistic way to manage a project.  Traditional SDLC models required “budgeting the design”.  Estimation was not easy leading to significant variances.  Managing to a budget helps keep an eye on the project scope providing a balance between value delivered and costs expended. Value also provides a measure of how to manage scope creep.  Using satisfaction provides a user driven measure of quality.

The proposed drivers: constraints, budget, value and satisfaction provides a new paradigm for measuring and managing projects.  However, it requires a different set of measures including subjective and qualitative data.  Traditional tools are not equipped to handle these drivers.  Another challenge is managing the change – acceptance of new drivers will require commitment from all stake holders: management, technical staff and the leadership team to be effective.

Written by Subbu Murthy

November 2, 2014 at 1:59 am

2 Responses

Subscribe to comments with RSS.

  1. IT professionals should always be challenging ourselves on how to look at things differently — this suggested framework helps bridge the old to new — thanks Subbu for challenging me.

    Jon Grunzweig

    November 2, 2014 at 10:48 am

    • Jon,

      I have always valued your inputs and feedback. Appreciate your kind sentiments.


      Subbu Murthy

      November 2, 2014 at 11:37 am

Leave a Reply to Jon Grunzweig Cancel reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: