Software Metrics: Best Practices for Successful IT Management

8.7 PRESENTING THE RESULTS

Having gathered all this information and knowledge we now need to make use of it to get authority to proceed. The information needs to be presented, at the very least, to someone with the necessary authority to sanction the future work, possibly to a group of senior managers. This is where the customer authority can help immensely. Get access to the most senior manager you can and present the feasibility report. The more senior the recipient of this report the briefer it should be but it should contain:

• Identification of the problems associated with software development in the organization. Refer to the triggers identified earlier.

• A statement of the business priorities of the organization.

• A definition of Software Metrics and a brief description of the scope of the subject.

• A mapping of Software Metrics to the business priorities and the problems of software development. This states what high level requirements it is planned be addressed.

• A strategy for implementing a Software Metrics program. This can be based on the following chapters of this section.

• A request for authority to proceed.

It is also a good idea to make a personal presentation to management. This presentation should summarize the report and it may be that the presentation is the vehicle for getting the necessary authority. Spend time on this to make it as professional as possible. Make sure that you know your audience. Make sure it relates to the business needs of the organization. By all means include examples from other organizations but be aware that you will only convince people, fully, when you can demonstrate success within your own organization. Make it brief!