Archive for the ‘Project Management’ Category

Who should report status against projects, and how often?

Monday, July 27th, 2009

Many project managers, department leaders, and process owners tend to take on the role of reporting status. They collect information from all the employees involved, merge, rewrite, update, put voice to that information, and publish it. It is time consuming work that has limited final value. By the time they are complete, it is often old news, and the intended audience has little interest. In fact, often, by the time the report is published, it is time to begin collecting information for the next report. The role of the manager becomes more about collecting and reporting status than managing the effort!

It can be argued that it is valuable work for the manager to collect this information. Employees will be challenged to take a look at what is going on in their area and the manager will have focused attention on that portion of their whole portfolio of work.
However, there are other ways to collect this information and ensure focus. We recommend that the manager hold their employees responsible to report status using a collaborative on-line location. If properly done, the employee written status will not have to be revised by the manager, can be visited by anyone that has the need and interest, and yet accomplishes the goal of focusing attention on the review effort.
In AccomplishTS, every project has the ability to have periodic status reports (weekly, monthly, quarterly) and more in-depth notes attached. Every employee involved in the project can provide entries. Each entry is dated and reports can easily be generated and saved for future reference – and they can printed in several formats such as rich text or spreadsheet. However, many of our clients tell us that keeping the information on-line and thus accessible on-demand by interested parties eliminates the need for printed reports.

Status report reminders can also automatically be sent, as well as an automatic capture of the status information for all projects in the system, giving an easy way to provide critical information to those that need it without a lot of tedious administrative tasks.
We recommend managers delegate to each employee in charge of important aspects of projects the job of providing weekly or monthly status updates. For instance, weekly status reporting could be required before the end of the day each Friday for critical projects, while lest critical projects would only require reporting monthly, such as before the end of the first workday of each month.

Weekly status updates are intended to be short and consist of bulleted statements concentrating on the following:
- what new was started,
- what was ended (completed or stopped),
- what redirection was decided,
- a prediction about future cost and schedule

Monthly status updates dig deeper into any mitigation or corrective action work planned to ensure the initiative is completed as planned, as well as a description of any changes to the original plan, including the reason for the changes and the impact expected. Monthly reports are intended to be a few paragraphs long – NOT pages.

Notes associated with a project status report can be of any length and the expectation is that they will be updated as needed. Additional documents can also be referenced or even attached to help build a complete record all in one location.

All levels of the organization are invited to review the status information. Managers, in particular, are expected to keep aware of status changes and hold conversations with their employees if there are questions. As much as possible, everyone’s time should be focused on understanding what current plans and actions are without extensive writing. Managers can thus manage, while employees doing the work can thus do the work!

Project Forms

Monday, June 15th, 2009

Over the last couple of years I have had the opportunity to work with Portland Metro (an organization led by an elected board to manage the development of the Portland, Oregon  metropolitan area).  Through Portland State University, I have taught almost every member of management the subject of tools for project management.  This includes a standard set of forms that help guide every phase of projects.

I was delighted to find recently that the Metro staff has taken ownership over their internal use of the toolset by modifying many of the forms to fit their particular needs.  In fact, they have moved beyond using the tools just for project management and have extended into using some of the forms for process management.  (They refer to processes as programs).

The tools they have adopted include the following:

  • Project Complexity Assessment…is a checksheet and form that allows the project sponsor to evaluate how rigorous the project management approach should be.  Some projects are fast and easy, requiring very little approval or oversight.  Other projects are large, complex, and/or politically important enough to require the careful guideance of the elected officials.
  • Project Proposal…this form outlines everything a typical project should have specified before starting, including specification, cost, timing, and responsibilities.
  • Council Project Proposal…this is a special form of the Project Proposal that adds certain information important if the Metro Council of elected officials approval and guidance will be required.
  • Stakeholder analysis…in the very public arena of Metro, it is important that all stakeholders have the opportunity to participate in projects.  This tool not only identifies who the stakeholders are, but encourages the development of a communications plan to ensure participation at the right times and in well designed forums.
  • Responsibility matrix…outlines who does what on the project.  Metro decided to use the PARIS format to determine roles (Participant, Accountable, Review Required, Input Required, and Sign-off Required).  The form encourages not only project team member responsibiities to be identified, but also key stakeholders.  It relates responsibility to each task.  For project that involve elected officials or other high profile individuals, an alternative Responsibility matrix using RAPID rather than PARIS was developed.  The RAPID approach (Recommend, Agree, Perform, Input, Decide) provides more distinction between those who decide and those who agree.
  • Risk assessment… provides a way to list all major risks, assess them into red, yellow or green levels of concern, and establishes a methodology for ongoing monitoring and reporting.
  • Project status reports…focus on budget, schedule and approval of deliverables, using a red, yellow, green at a glance approach supported by more indepth data.  The report includes a listing of issues and concerns, as well as next action items for the project team, senior management, and the Metro Council.
  • Program status reports…are very similar to project status reports, except they focus on processes.  Any appropriate set of metrics replaces the budget, schedule and approval of deadlines used in the project status report.  This form uses the same red, yellow, green at a glance approach supported by more indepth data to track the performance metrics.  Besides listing issues and concerns and next actions included inthe project status report, it also includes and area for the analysis of risks and opportunities.
  • Scope change form…provides a way to request and receive approval for changes to a project or program.  It is supported by a detailed log providing a complete history of changes.
  • Project Evaluation guide…provides a review of the entire project from aspects including framing, work plan, personnel, analysis, communications, tools, and outcomes.

The Metro tool set is a great example of an organization proactively adapting generic tools to meet their individual needs.  Each of these forms is used by the project team and managed by the project manager and sponsor.

In AccomplishTS, forms like these are placed in the document library in each work area associated with each project or program.  All team members, project sponsor, and authorized stakeholders participate in continuously keeping the forms updated and current.  Tied to the built in metrics and structure of AccomplishTS, a powerful, fully customized solution evolves, leading to powerful results.

The lessons I have learned from Portland Metro have stimulated me to begin to expand the chapters on project management and process management in my book, Action with Traction.  It is clear to me that a second edition is not far off!