Project Reporting


The final step in the project management model is the reporting of the status of the project at a summary level to the project sponsor, project steering committee, and stakeholders (see Figure 17.4).

Figure 17.4. Project reporting

graphics/17fig04.gif

The proactive nature of the project sponsor and project steering committee was introduced in early parts of this book. Rather than the rubber stamping and passive behavior that many steering committees were relegated to in traditional project management, eXtreme project management actively involves these executives in:

  • The selection and initiation of projects;

  • The monitoring and review of projects;

  • Providing assistance to projects when required; and

  • Active resolution of project conflicts.

The selection and initiation of projects was covered in Chapter 5 of this book. In this chapter, we explore the other key functions of steering committees and project sponsors.

As also discussed in earlier chapters, it is important that the senior management take responsibility and accountability for the projects they are sponsoring. Your role, as a project manager, is critical in assisting senior management (who are generally from the process culture and are generally not sure of their role in projects) in both gaining access to the right information regarding their project and the right decisions to make.

Project Management and Technical Deliverable Reviews

As discussed in Chapters 3 and 5, projects involve the interrelationship between the managerial aspects (business case) and the technical aspects (system or product development deliverables). Review of the quality of the various technical deliverables such as system data, function requirements, designs, and so on, is best achieved through quality assurance processes such as walkthroughs and inspections, covered earlier.

The same distinction between technical reviews and project management reviews applies to the role of steering committees and project sponsors. The project sponsor and steering committee reporting and reviewing roles are to focus on the business case and whether there is any variation in the agreed-on business case.

Should the project manager wish to use either the project sponsor or members of his or her steering committee to provide technical input or to review detailed technical issues, this should be done outside the normal sponsor and steering committee reviews. It is common for project sponsors and members of the steering committee to be experts in areas of knowledge relevant to the project. For example, the general manager of marketing might be one of the most experienced people in the marketing issues relevant to a new retail banking system. This person is also on the project steering committee. As a result, you should separate the two roles that the general manager of marketing has on his or her project.

High Risk, High Feedback

There is a very simple principle here. The higher the project risk, the higher the level and frequency of executive feedback and governance.

The governance of the business case is a steering committee role and the detailed technical input role regarding marketing issues is a technical review role and should be handled as part of the system development process. In our example, if the project manager wishes to alter the scope and objectives of the project based on new information gathered during the system development process, this is a decision that must be made by the steering committee. If there are some detailed issues on the impact of the new system design on marketing strategy, this is a technical issue and would be resolved as part of a quality assurance review or systems analysis.

The Project Reporting and Review Process

The format and timing of project reporting will vary in each organization and will also depend on the size and risk of the project.

No Surprises

You should always prebrief your sponsor and steering committee members before the meeting. You need decisions, not surprises in a steering committee meeting.

For small projects, there is normally only a project sponsor and because small projects are generally less than three months in duration, a project review with the sponsor should occur either weekly or biweekly. For medium projects, there would normally be a steering committee and meetings would normally be monthly. For larger projects, there may be a project steering committee and an IT steering committee, so meetings might be monthly or quarterly. High-risk and extreme projects are subject to more change and turbulence and, as a result, the project reporting and review process may be more frequent and demand driven. In large, high-risk projects, it would be normal for the steering committee to delegate the demand-driven reporting role to the project sponsor or a subcommittee, as it often is too difficult to convene the steering committee on short notice.

As discussed earlier, the following information is the core of the project reporting and review process:

  • The state of the project; that is, is it still proceeding to plan or not?

  • If not, what is the revised situation and what are the causes for the variation?

  • What actions have been taken by the team to solve any problems?

  • What alternative scenarios are available?

  • What actions can be taken by senior management?

  • What is the revised or updated business case for review and approval?

graphics/extool.gif

Figure 17.5 provides a sample form that can be used for smaller projects, highlighting the essential information required by project sponsors and steering committees.

Figure 17.5. Project report

graphics/17fig05.gif

In addition, project reporting would typically involve a summary of the project tracking information such as costs, effort and schedule progress, and variations.

As detailed in the sidebar, there should be adequate information and time for the project sponsor and steering committee to understand the issues and be able to make informed decisions.

Really Radical Reports

An extremely radical model implemented by one of our clients based the project reporting process on the success sliders introduced in Chapter 7. This approach is shown in Figure 17.6.

Figure 17.6. A really radical report

graphics/17fig06.jpg

This approach recognizes that senior management are only interested in those success criteria that really matter to them. For example, if quality really mattered ("on") and budget was "off," why would you report on budget?

Assistance to Projects

As detailed in earlier chapters and later in Chapter 20, the key role of the project sponsor and steering committee is to "add value" to the project and to the project management process. This requires the members of these groups to focus on proactive problem resolution of changes before they are implemented rather than the traditional reactive approval of changes after they have happened .

Resolution of Project Conflicts

Also, as discussed in Chapter 5, a common form of assistance that the project sponsor and steering committee members will be required to provide is in the area of stakeholder management.

Process Cultures Again!

The concept of regular steering committee meetings is a reflection of the "mechanical" model of the process culture. You need to be able to quickly get to your sponsor whenever serious issues arise in your project. Unfortunately, these do not happen on a regular (e.g., monthly-to-monthly) basis. Make sure that you can arrange to see your sponsor on a demand basis, if possible.

Given the number of different stakeholders in most projects, you will inevitably experience conflict between yourself and key stakeholders (and their managers) and conflict between stakeholders themselves .

For example, a project manager may find a stakeholder, who is organizationally more senior than the project manager, not prepared to release a key person to assist in the project. Alternatively, a project manager may find two key stakeholders not agreeing on scope, objectives, or quality. In these and similar cases, it is legitimate for the project manager to raise the problems with either the project sponsor or project steering committee for assistance and resolution.

Project Steering Committee Meeting Structure

The structure and agenda of project steering committee/sponsor meetings will vary, but all project steering committee/sponsor meetings should focus on the following topics or agenda items:

  • The status of the project ”has the business case altered since the last meeting?

  • If so, what changes are there to:

    • the scope of the project?

    • objectives?

    • the priority of the objectives?

    • the project development strategy?

    • risks?

    • benefits or returns?

    • costs?

    • project plans or schedules?

    • quality agreement?

    • staffing agreements?

  • What actions has the project manager or team taken to resolve the issues?

  • Who can assist in resolving the issues?

  • Who is responsible for follow-up?

  • What caused the changes?

  • Are there any future or expected issues?

  • Other items as required.

Reporting to Stakeholders

It is essential that the same processes and information be both gathered from and distributed to the project's stakeholders.

Meeting the Enemy

While any attempt by the business groups to change the business case in your project will be relatively easy to determine and manage, you should watch your back. In our experience, the most common form of change is internal ”from your team.

For critical stakeholders, the project reports should be actively reviewed via stakeholder meetings or one-on-one sessions. For nonkey stakeholders, it would be adequate for them to receive copies of all project tracking summaries and project reports.

Ideally, an executive from each of the key stakeholder areas would be on the project steering committee as well.



Radical Project Management
Radical Project Management
ISBN: 0130094862
EAN: 2147483647
Year: 2002
Pages: 136
Authors: Rob Thomsett

Similar book on Amazon

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net