Saturday, October 07, 2006

To be CIO Checklist [Part 2]

Lets review the resons why CIO's are hired -
  1. Leadership
  2. Business Skills
  3. Execution Ability
  4. Impact on board

CIOs are expected to bring in strong leadership skills and the ability to think and execute in the best interest of the organization. Their knowldege of the business domain and skills make them an important asset to the Company Board.

Having said that, it goes without saving - until CIO exhibits the three sailent features (Leadership, Business skill, execute) and make a impression on the board, they aren't being effective.


Take stock of priorities and eliminate the unnecessary. Don't feel into something with little payoff.



Thursday, September 07, 2006

Think - Speculate - Act

Establishing a successfully governance requires forming a board with leaders offering different perspective -

  1. Thought in the process
  2. Providing opinions
  3. Subject Matter Experts from each business unit of organization

Successful implementation of the governance requires balance participation from the leaders.

Leaders with thoughts bring in fresh perspective and functioning of the governance. Leaders with opinions bring help articulate thoughts and bring out ground realities in them. SME's bring in the required knowledge of the business processes to apply the thoughts.

Thus forming one complete cycle for "Think - Speculate - Act" to implement a successful governance.

Sunday, August 06, 2006

It Works If You Work It

To grow a plant into a flourishing tree, you need to make sure you water the plant and manure it on time. You need to parent your child in order to help them grow into better human beings. The point I am trying to reach is - "To make things work, you need to work on them"

Its the same with organizations. Just by working for an organization, you are not going to grow it. You will have to work on it, work on building the organizational values, constantly supporting the changing environment, and looking for break through opportunities ...

But is that sufficient?

Not really, isn't it! You need to articulate what you are planning for the orgination to its customers, key stakeholders and employees. You need to monitor the progress against the planned goals, as that's the only way you can get to know if you are heading in the right direction and making real progress. Monitor costs, achievements, failures and KPIs. And publish/ communicate the results, and cover the following in the communication -
  • Scope
  • Progress Update
  • Pending Items/ Next steps
  • Issues


Remember, if you want to be understood of what you are working on, make sure that it is marketed and plan/progress is communicated. And work towards achieving the stated goals with credibility.

Friday, August 04, 2006

Software Reuse

There has been tons and tons of books/articles on software re-use...But even then we still end my writing the software from scared when we can get similar modules (if not same) for much less effort and cost.

Reusing software would mean, you decide what are the key functionalities required, and what good to have can be compromised.

Best places to look for software reuse is your organization software factory or the open source software components. Open source not only provides with the basic key functionalities that brings up the whole software development on much faster grounds.

Also remember that if you can get an off the shelf software or component, which meets 90% of your requirement, then its worthy to buy it and ignore the other 10% of the requirement. Yes ofcourse it depends upon how critical the other 10% is!

Wednesday, February 16, 2005

To be CIO Checklist

Below are some of the key criteria for the awarding/ grading the CIO during one such. Answer the below questions and evaluate how you stand in to be awarded.

Scope of Responsibility
Is the person, in charge of a budget? If so, provide approximate budget amount
How many users does the person support?
How many IT employees report up to the person?

On-the-Job Accomplishments
Conceived and executed a major operational improvement within IT.
Conceived and executed a major operational improvement in the business.
Conceived and executed a new business product/service idea.
Led a significant enterprise-level project.
Negotiated important contracts or successfully managed relationships with outside suppliers or business partners.
Led or devised an effort to measure and prove IT value to the business, or managed the IT portfolio.
Leads or sits on a committee on the business side of the organization, or a committee composed of both IT and business leaders.
Has taken over duties temporarily or permanently from the CIO.
Turned around a troubled project or organization.
Started up a new IT team (such as for a new division, new market, etc).

Characteristics - please describe how this nominee exemplifies these characteristics:
Has a business sensibility
Change agent
Bold/risk taker
Technology innovator
Business innovator
Has learned from failure
Creates a positive work environment
Engenders loyalty and trust among IT staff
Is respected by business leaders in the organization
Communicates effectively with IT and business staff
Team builder/talent developer
Good at execution (getting projects done on-time/on-budget/on-quality)
Mentors younger or less experienced staffers
Is actively involved in community service (such as volunteering in a leadership role at a nonprofit, tutoring, etc.)

Does process really suck?

There is a very popular metaphore - "Too much is too bad". Same applies to the process. But how does one identify if they have hit too hard and moved to a higher extreme.

Look out for the following indications to keep a check if you/ organization has too much of unnecessary process -
  • Employee morale not upto the mark, when a new project/ activity is initiated (but there could be various other reasons, other than process for this)
  • People find work-arounds for the process, and make it a "thing" to be done, than use it to improve the quality of their deliverable.
  • ...

There are more such indicators, but managers must constantly review the "Process" and tailor it, before it goes out of hand. The key in the business in in CIP (Continious Improvement Process). It is just not the responbility of managers to identify the process improvement, every individual organization must contribute his/ her thoughts on the process. It is all about "help me to help you". We are here to excel, and excel we must as a team.

Monday, February 14, 2005

IT Governance and Outsourcing

The decision to outsource IT has become a part of strategic thinking process for a large number of organizations. Organizations across the globe are increasingly evulating what is core to their business and what isn't, and the non-critical functions (one such being IT) are being outsourced. Through outsourcing, organizations largely benefit from greater expertise, lower costs and higher quality; and also free up the management to focus on critical aspects of business rather than the support functions. The absence of good IT governance is leading to the outsourcing.

Role of IT governance
IT governance exists within the context of corporate governance, and the principles are essentially the same. IT governance is an accountability framework and management process that helps to define and communicate what must be done and provides the rigorous oversight to ensure that it is. It drives interactions and provides feedback mechanisms that encourage communication and desirable behaviors.

The accountability framework is typically made up of well-defined roles and responsibilities reflecting decision rights among the participants in the IT management process and is reinforced by effective reporting. Making sure decision rights are clearly defined is critical to resolving a myriad of issues around strategy, standards, monitoring and change introduction.

IT governance and the outsourcing contract
Because good IT governance is so essential to establishing an effective IT environment and even more essential to a successful outsourcing relationship, it should receive priority attention during the negotiation and contracting phase of an outsourcing deal. By focusing on governance in the negotiation stage of the relationship, both parties can clarify their respective roles and responsibilities to ensure the relationship's success. Incorporating an IT governance structure, responsibilities and reporting mechanisms into the contract increases the likelihood that the IT governance model will be implemented with the required discipline and rigor. Indeed, good IT governance should be viewed as a principle value of outsourcing. Contracted IT governance should cover three areas in particular:

  1. Roles and responsibilities
  2. Management structure
  3. Reporting

Roles & Responsibilities
At a high level, four stakeholders are involved in a good IT governance model and their decision rights should be clarified in the contract:

  1. Business unit or functional leadership
  2. Business executive leadership
  3. Senior IT leadership
  4. IT delivery leadership

Management Structure
Equally important to defining roles and responsibilities is contracting a management structure to support the execution of those roles and responsibilities. A forum must exist wherein requirements can be reviewed and approved and where execution can be monitored. Ideally, this type of structure would already exist within an organization. Too often, however, this is not the case and the contract is an ideal opportunity to create the necessary structure.
A three-level structure made up of the following committees can be built into the contract, ensuring that stakeholders participate and execute their roles and responsibilities:

  • User committees
  • Operation committee
  • Executive committee

User committees formed around business units, technology groupings or business processes are ideal forums in which to review emerging business needs and service delivery. By articulating the need for and the structure of such committees in the contract, the outsourcer establishes a forum for interaction with the client's user community.
The operation committee is generally composed of senior IT leadership and IT delivery leadership. Bringing together the IT leadership of the outsourcer and the client, the operation committee is charged with overseeing approved initiatives and service delivery. It is critical that the composition, agenda, frequency of meetings and deliverables of such a committee be contracted, as it is an essential factor for a successful outsourcing relationship.
The executive committee is the forum for approval of IT directions and initiatives, and the contract should specify the composition, agenda, frequency of meetings and deliverables of this committee as well.

Reporting
While outsourcing contracts typically require service level reporting to some extent, outsourcers are in an ideal position to introduce a broader scope of IT reporting and support the roles and responsibilities articulated in the contract. User committees would generally require progress reporting on approved projects, enhancement backlog reporting to monitor request status, and of course service level reports on critical processes. The operating committee would require similar reporting and, based on its responsibility for the execution of all IT services, supplemental financial information.
The executive committee reporting requirement would be highly summarized and may take the form of a balanced score card report, touching on four or five critical dimensions, such as business contribution, service quality, budget, user/client satisfaction and strategic direction.
The outsourcing contract should specify the reporting required to manage the relationship and services and, indeed, examples of required reporting should be included within the contract.

Conclusion
While companies are now treating IT as a key element of their business, they often fall short in the area of IT governance, especially when outsourcing their IT functions. By making good governance an essential part of the contract, outsourcers and clients can do a better job of setting expectations and increase significantly their chances of creating a win-win situation for all.

Thursday, January 20, 2005

Sarbanes-Oxley (SOX) and Corporate Governance

What is the Sarbox Act or Sarbanes-Oxley Act ?

Sarbanes-Oxley is a US law passed in 2002 to strengthen Corporate governance and restore investor confidence. Act was sponsored by US Senator Paul Sarbanes and US Representative Michael Oxley.

Sarbanes-Oxley law passed in response to a number of major corporate and accounting scandals involving prominent companies in the United States. These scandals resulted in a loss of public trust in accounting and reporting practices.

Legislation is wide ranging and establishes new or enhanced standards for all US public company Boards, Management, and public accounting firms.

Sarbanes-Oxley law contains 11 titles, or sections, ranging from additional Corporate Board responsibilities to criminal penalties. Requires Security and Exchange Commission (SEC) to implement rulings on requirements to comply with the new law.

What does Sarbanes Oxley Address?
  • Establishes new standards for Corporate Boards and Audit Committees
  • Establishes new accountability standards and criminal penalties for Corporate Management
  • Establishes new independence standards for External Auditors
  • Establishes a Public Company Accounting Oversight Board (PCAOB) under the Security and Exchange Commission (SEC) to oversee public accounting firms and issue accounting standards

Click here for more details on SOX Survial.