project management

Project Updates and Status Reports

The Report

No matter what size or type of project you are involved in in or managing, there is inevitably a status report required and update or steering meeting planned regularly.

There are numerous sources and recommendations of format, content and process of project status reports but these.
All organizations have their own preferences when it comes to style and format but the essentials don’t really differ from company to company.

The project status report must have a purpose. The first question to as is “Why?”
Some PMO (Project management Offices) in organizations sleep walk with their various templates and formats for these reports but ideally, they should be reviewed regularly.
The project status report is an essential element of Project Governance and control. Typical contents can include but is not limited to:

Current Status against Plan
Recent Activity
Planned Activity
Budget Performance
Resource allocation
Risks & Challenges

Within these headings all areas of the project can be discussed.

In addition to a communication of status this is also an opportunity to high-light any areas of concern and seek guidance, advice or support in the resolution of issues.

This may seem obvious but these meetings work best when a policy of openness and honesty is adopted.
Regular status reporting is necessary to be an effective means of communicating on all aspects of the project. It helps to maintain traction and visibility for the project. The frequency of reporting is often a function of the duration of a project and its importance to an organization. For projects with a short duration (i.e. less than six months), it is better to have weekly reporting so that issues are raised and dealt with sooner. For projects with a longer duration, bi-weekly or monthly reporting may be more suitable or desirable. As the project nears and end or a period of high activity the frequency may increase somewhat as required to manage that activity.

Project Report Content

When preparing the content, think for a minute before just blindly filling in the detail. Look for the reasons why the stakeholders may want certain information included in a report.
What is the next significant milestone?
Are there any blockers in the way to achieving the milestone?
Is the process to achieve the milestone fully understood?
Where there any contentious issues at the previous meeting – have they been resolved?

Remember that a project has been set initiated by a business to assist the business in achieving objectives or to reduce risk or resolve an issue. Always try to gear the project update into how close you are to making those business objectives a reality. This would by “Why” the project was initiated in the first instance.

Is there any important factor that needs to be discussed that is not included in the regular format of the project update meeting?
Be sure to raise it. If you are going to raise an issue it is always a good idea to have a solution or proposed way forward to present for the stakeholders to approve.

Delivery of the Project Status Report

The delivery of the Project status report is generally in the form of a meeting. These can be face to face meetings or web based meetings. Both have their advantages and drawbacks.
Face to face meetings are a great way to engage and build strong relationships. You can read the facial responses and body language and adjust your presentation to suit.
Web meetings force people to stick to an agenda and provide each participant with a specifc time slot – but talking over each other can have a negative impact on the meeting.
It is important to be clear and concise on all points to which you are presenting. Don’t say anymore that you must on any point. You may have someone in the audience who is out to impress and you or a project you are working on could be their target.
Limit your answers to yes or no and keep the detail to a minimum.
If you have some items you are uncomfortable discussing – then start with these and prepare a position on each of them. i.e. – What would you not like to be asked?

Format of the Project Status Report

Typically most organizations will utilise a format or a template whereby it is required to complete certain fields weekly for presentation to a steering team. In a new organization, it will always take a bit of time to get used to company jargon and pinch points. Don’t consume yourself too much with the template being used. This is unlikely to change in the short term so make your content suit the fields in the template. Too often I see Project managers complaining and wasting time on the report template when it is fixed and not changeable. Focus more on the facts of your project. You can always add in a comment verbally at the end of your presentation if needed. If you are asked to create a format then let the facts shape the format, do not let the aesthetics of a neat format guide your update.

In Summary – Project Updates

1. Preparation is Key.
2. Ensure your Finances, Risk Log and Activity Records are Up to Date.
3. If needed – speak to one or two of the stakeholders in advance of the update to float any potential sticky items past them.
4. Rehearse your Update in Advance (if you are expecting to deliver bad news – rehearse with a colleague)
5. Be Frank, Open and Honest.
6. Address any questions with short closed precise answers.
7. Don’t be afraid to ask for advice and Support.
8. Remember as soon as a project issue is identified – you can commence to work towards a solution!

Need help?

If you are struggling to come to terms with repetitive project issues and you need some advice or support, contact us by email: info@systeme.ie with some background on your particular issue and we’ll be in touch.

Download our Project Rescue Guide here Project Rescue Guide

CONSULTING

The Impact of Pharmaceutical Serialization in Your Organization

Pharmaceutical Serialization

Serialization in the pharmaceutical industry requires the individual identification of each individual saleable unit. i.e. each vial or syringe or pack of tablets must have an individual serial number identifying the pack back to source, date and time of manufacture providing full traceability.
Previously legislation only required products to be identifiable to a manufactured batch which can consists of thousands of units. The imminent Serialisation legislation will require new capabilities to be implemented across many different functions of a typical company resulting in a wide reaching programme of business change.
The objectives of Serialization are:
To Prevent the introduction, distribution and use of counterfeit medicines in the global market
To facilitate the detection of counterfeit medicines
To Provide accountability for the movement of products by the supply chain participants
To improve the efficiency and effectiveness of recalls

Business Areas Impacted by Serialization

There is a significant impact on Packaging operations where serialisation data will have to be applied to product packaging at one or more levels. In the more complex serialisation models, this operational impact will extend into the distribution operations in central and/or local markets, where information on individual sale and shipment transactions needs to be gathered and added to the serialisation information. Particularly in the more complex track and trace models, significant IT capabilities will be required to manage serial numbers and track information related to the product and its movement.

Other impacted business areas include:

Commercial
Supply chain
Quality assurance and control
Procurement
Training
Legal
Regulatory affairs
Corporate

All these impacted areas need to be assessed for adoption of serialization and the appropriate solutions put in place. Given that these impacts affect many different functions and third parties, there is a high risk that solutions will not work well together unless the design of the overall solution is carefully managed and governed.

Managing Implementation of Serialization

Establish a programme of activity to build organisational and extended supply chain capability.
Be realistic about the emerging nature of these capabilities and build in adequate time and resource to effectively test and iterate solutions.
Design serialisation activities to closely couple related actions to minimise the possibility for errors due to abnormal events.
Design both the normal processes and the regularly occurring non-standard events to avoid product supply quickly grinding to a halt.
Ensure cross-functional teams are established to carefully design the interfaces between departmental and organisational boundaries.
Ensure adequate time is allowed for packaging design changes to be made to accommodate serialisation features required.

Ownership

As with any other key element of the business. There should be a local senior level sponsor that will take complete ownership for Serialization on site or within the organization. A common misconception here is that it needs to be an IT or a Software discipline that should own Serialization. Serialization is a supply chain solution and function but the means of delivery is via Software and Technology. The ownership should be with the Supply Chain team. One could argue that all departments are in the supply Chain in some capacity. Serialization is a key differentiator in the Pharmaceutical industry and is only in its infancy. The spread and impact of Serialization will continue to grow. A dedicated team will be needed to both implement sand run Serialization as part of the daily work on each site.

Summary

Deliver Serialization into your organization with an eye on the market for the next 5-10 years not just to get a system in place.

Assign a senior level owner for Serialization.

Build a cross functional Team with the capability to manage and expand the footprint on Serialization within the business.

Ensure the Success of Serialization in the business forms part of the indivdual and collective goals and objectives for the team.

Respond swiftly and decisively to Regulatory requirements

Implement and practice the same level of control that is in place with other site systems.

For more Information and Guidance on the Implementation of Serialization please email is at info@systeme.ie

Download our Project Kickstart Guide Here