Early in my career I was volunteered, (I know that’s an oxymoron, but most of us have experienced “being volunteered”), to join a quality circle. We met on a regular schedule, discussed problems and identified solutions. Our managers kept stressing how important our quality circle was. It was interesting for a while. Nothing much came from it.
Perhaps nothing came from it because “being volunteered” was the wrong starting point. I think it did not work because the expectation of what our quality circles were going to achieve was out of proportion.
Project reporting is an important aspect of project delivery. There are many reasons to develop regular project reports. Project reports create a focal point for clarifying the precise status of a project and for providing information which helps key stakeholders to perform necessary supporting actions as well as manage customer expectations.
There is a common tendency in business nowadays for project managers to produce a “plan on a page”. This document is often created as 1 PowerPoint slide. It provides, at a glance, an overview of the key activities of the project, the overall timescale, and sometimes a very high level view of the dependency between key activities.
A few weeks ago I posted an article here ( “Methodology: Guidance or Rules?”) with some views on the development of delivery methodologies. I want to build on that today with some simple tips for anyone involved in designing or implementing new project or change management approaches.
The development of standardised approaches, the capturing of best practice and the creation of project management accreditation have moved the project management profession on significantly over the past few decades. Arguably, it is only since we have these things that we can really call ourselves a profession rather than just a loose affiliation of people with a relatively similar role to perform.
Prioritisation is crucial for effective project management in organisations. It is prioritisation that gains access to those resources required to get the project done. Without prioritisation there can be a continuous fight for resources and projects drag on and on.