It depends on the situation. However, I believe there should be a report on a regular basis.
Abolfazi,
A predetermined basis, sound interesting. Could the period change over the course of the project? Saving Changes...
Suneel Kumar NadellaDirector (Self Employed)| Manasai Services Pvt Ltd (Self Employed)Solihull, West Midlands, United Kingdom
Nov 29, 2019 10:58 AM
Replying to Vincent Guerard
...
Suneel,
Thanks for sharing, your experience in the absence o monthly reports.
The average duration of projects/programmes I have worked are always over 18 months and in some cases spanning across 5-year regulatory cycles. I have established a span control of at least 3 or more delegates who used to gather and compile the report and share the same to all stakeholders. We were reasonably compliant with this process(95%). I guess that is the best you can do in any project situation. As I mostly worked in the regulatory Industries over the last 20 years, we had an additional onus of closing every project formally for regulatory requirements of respective countries. I won't score myself very highly than 55% to 60% compliance though.
Lessons learned, yes we haven't learned yet to do them!
They're an important source to refer back to. Each organisation has lessons learned specific to only their organisation in addition to the general ones experienced across all organisations. So, it would be worthwhile implementing these, as they will assist future projects and project teams.
...
1 reply by Vincent Guerard
Nov 30, 2019 7:19 PM
Vincent Guerard
...
Sante,
I can't agree more
Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Nov 29, 2019 11:02 AM
Replying to Vincent Guerard
...
Luis,
That is if online project performance is available and sufficient. Then you have a realtime report.
Dear Vincente
We walked there at large steps.
So that everything is in the cloud Saving Changes...
Our governance structure requires PMs to report at least once on an annual basis, but our projects run 10 yrs plus. While with another Omni-bus type project we had monthly meetings, which I found useful in way, but not in other ways, as some info never changed month to month.
As I mentioned in the other thread, we are seeing a real increase in automated reporting via our SAP/ ERP system, as senior management likes the idea of being able to run their own reports whenever they wish to do so. In fact, so much so, that PMs and their staff are being asked to update project contained in the ERP system every two weeks.
...
1 reply by Vincent Guerard
Nov 30, 2019 7:21 PM
Vincent Guerard
...
Steve,
Your project needs to report once a year, a lot can happen in that time.
Monthly meetings are documented or just verbal?
Saving Changes...
Ahmed Adel SolimanRegional Sr Sales Manager| HoneywellCairo, Maadi, Egypt
Nov 29, 2019 3:44 AM
Replying to Ahmed Adel Soliman
...
I think that PM need to report the progress on monthly basis and also per quarter. The difference between both will be what the kind of reports and information that need to be reported in this frequent.
Some issues should be reported and presented as soon as possible to avoid happening of any fatal problem because of the too late reporting.
By the same, another kind of issues no need to be reported and presented on monthly basis and only enough to be highlighted and reported per quarter or half year (if the project duration more than a year) and this to for follow up and being updated with the progress and the project performance.
May be
- information or a chart comparing the quarter costing with the overall project cost.
- Graph showing the total of the cost saving over the period
- Graph showing the employees turnover ratio, percentage of injuries...etc
- chart showing overall project progress UTD.
something like these examples and not going into deep details as the months reports already include details about the period progress and achievement. Saving Changes...
The average duration of projects/programmes I have worked are always over 18 months and in some cases spanning across 5-year regulatory cycles. I have established a span control of at least 3 or more delegates who used to gather and compile the report and share the same to all stakeholders. We were reasonably compliant with this process(95%). I guess that is the best you can do in any project situation. As I mostly worked in the regulatory Industries over the last 20 years, we had an additional onus of closing every project formally for regulatory requirements of respective countries. I won't score myself very highly than 55% to 60% compliance though.
Suneel,
Sound very efficient, thanks for sharing here. Saving Changes...
They're an important source to refer back to. Each organisation has lessons learned specific to only their organisation in addition to the general ones experienced across all organisations. So, it would be worthwhile implementing these, as they will assist future projects and project teams.
Our governance structure requires PMs to report at least once on an annual basis, but our projects run 10 yrs plus. While with another Omni-bus type project we had monthly meetings, which I found useful in way, but not in other ways, as some info never changed month to month.
As I mentioned in the other thread, we are seeing a real increase in automated reporting via our SAP/ ERP system, as senior management likes the idea of being able to run their own reports whenever they wish to do so. In fact, so much so, that PMs and their staff are being asked to update project contained in the ERP system every two weeks.
Steve,
Your project needs to report once a year, a lot can happen in that time.
Monthly meetings are documented or just verbal? Saving Changes...