Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
Yes i think the reports are essential once a month to the Project Steering committee or Board as a project progress tracking mechanism and to enable the Board to make decisions if a project is set to exceed it's tolerances of Budget, Scope , Quality or Schedule .
The Reports also help highlight dependencies on other projects or activities.
And by Report , I don't mean just the documents but someone talking the Board and Steering committee through the actual project progress.
And some formal decisions like decisions on Change Requests are best tabled at a Steering committee and minuted appropriately and are best reflected through these project progress reports and the corresponding minutes.
The onus is on the PM to produce accurate, easy to understand and truthful account of the project in those reports. The Organization will miss out on key achievements , progress made by the project or blockers to the project success if those reports were not produced regularly.
...
1 reply by Vincent Guerard
Nov 28, 2019 4:47 PM
Vincent Guerard
...
DO you believe monthly is the only acceptable frequency? or once by semester could make sense in some cases?
Yes i think the reports are essential once a month to the Project Steering committee or Board as a project progress tracking mechanism and to enable the Board to make decisions if a project is set to exceed it's tolerances of Budget, Scope , Quality or Schedule .
The Reports also help highlight dependencies on other projects or activities.
And by Report , I don't mean just the documents but someone talking the Board and Steering committee through the actual project progress.
And some formal decisions like decisions on Change Requests are best tabled at a Steering committee and minuted appropriately and are best reflected through these project progress reports and the corresponding minutes.
The onus is on the PM to produce accurate, easy to understand and truthful account of the project in those reports. The Organization will miss out on key achievements , progress made by the project or blockers to the project success if those reports were not produced regularly.
DO you believe monthly is the only acceptable frequency? or once by semester could make sense in some cases?
...
1 reply by Deepesh Rammoorthy
Nov 28, 2019 5:07 PM
Deepesh Rammoorthy
...
Monthly is good just from my experience .
A lot tends to change in a month, especially where you are running Agile Projects . Two sprints tend to achieve significant progress.
Saving Changes...
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
Nov 28, 2019 4:47 PM
Replying to Vincent Guerard
...
DO you believe monthly is the only acceptable frequency? or once by semester could make sense in some cases?
Monthly is good just from my experience .
A lot tends to change in a month, especially where you are running Agile Projects . Two sprints tend to achieve significant progress.
...
1 reply by Vincent Guerard
Nov 28, 2019 6:25 PM
Vincent Guerard
...
Deepesh,
The pace of some other projects is really slow compared to an Agile Sprint.
If there is something the PM will communicate in the progress report which cannot be pulled by stakeholders from existing information radiators or repositories, I'm okay with that, but then the focus should be on minimal sufficiency as I've seen immense effort wasted in tuning & tweaking such reports to put the right "spin" on the current state of a project.
Kiron
...
1 reply by Vincent Guerard
Nov 28, 2019 6:19 PM
Vincent Guerard
...
Kiron,
Agree some reports take more than a week person to produce.
If information is not available otherwise the report must be produced.
If there is something the PM will communicate in the progress report which cannot be pulled by stakeholders from existing information radiators or repositories, I'm okay with that, but then the focus should be on minimal sufficiency as I've seen immense effort wasted in tuning & tweaking such reports to put the right "spin" on the current state of a project.
Kiron
Kiron,
Agree some reports take more than a week person to produce.
If information is not available otherwise the report must be produced. Saving Changes...
It depends on the audience. My program governance group meets and gets a status once a month. Other project working groups, it's once a week.
Sante,
Do the information is compiled some way or it is just verbal, then forget when people change? not leaving any record of some history on the project.
...
1 reply by Sante Delle-Vergini, PhD
Nov 28, 2019 9:44 PM
Sante Delle-Vergini, PhD
...
It depends on the organisation Vincent. I would say it's a mixture of verbal and "summary" presentations. History of projects and lessons learned are less common than progress reports, and to be honest, the former is done pretty rarely.
A lot tends to change in a month, especially where you are running Agile Projects . Two sprints tend to achieve significant progress.
Deepesh,
The pace of some other projects is really slow compared to an Agile Sprint.
Could the reporting period be longer? Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
I would recommend monthly at minimum. Ideally, live data available to anyone/anytime, but if a manually created report, monthly works. Depends on the audience, project, expectations, etc. Saving Changes...
Do the information is compiled some way or it is just verbal, then forget when people change? not leaving any record of some history on the project.
It depends on the organisation Vincent. I would say it's a mixture of verbal and "summary" presentations. History of projects and lessons learned are less common than progress reports, and to be honest, the former is done pretty rarely.
...
1 reply by Vincent Guerard
Nov 29, 2019 10:56 AM
Vincent Guerard
...
Sante,
Lessons learned, yes we haven't learned yet to do them!
