Notes on Reporting Progress
Categories: Agile Communications, Communications Management
No matter how we hard we try to keep information short and simple, there is still the minimal bits of information we should capture for keepsake. Here are some brief notes on reporting on progress - your approach likely, will be different.
The progress report would comprise minimally, the following elements:
Use a table for each of the above. Information which normally accompany the above, briefly:
Additional information for presentation in the report or for the progress meeting, may include:
Leaving it to you for the format of the report. Click here for an example of a project progress report.
Categories: Agile, Agile Communications
My project involves the deployment of reliant systems for aviation safety. The project was called, tendered, & awarded as waterfall. At the start of the project, there were unprecedented, IMO irrational new requirements with a mandated condition of urgency to complete the project ahead of schedule.
With unanticipated new requirements, there was a sense the project will need a different approach to management if the team were to keep to the proposed timelines. It didn't happen. Because interestingly nobody could agree nor willing to deep dive into project management methods!
So the project continues with negotiated mindless commitment to accommodate to needs, wading through waterfall demands that are difficult to compromise. Our upside of commitment is cohesive customer-vendor collaboration; developed through working in proximity. But it could easily go the other way.
This brief presents the lessons learned in introducing & adapting Agile in a contracted waterfall project. The introduction which was unintended & unplanned for. Where Agile is informally practiced.
The project eventually settled into a regime that emphasizes meeting deadlines on essential deliverables. And communicating developments particularly issues verbally & in a timely manner. Compromises were made on:
Now in its final stages, the project runs & feels like an Agile project. Where communication is key to keeping everyone updated on progress & ready to resolve problems, if any arises. It is informally Agile with prescribed waterfall submissions, minus the embellishments typical of Agile methodologies.
Our Lessons Learned
Thus far, we applied with intent the following:
My take on our success, in addition to the above lessons:
The project team continues to maintain & prescribe project management functions e.g. QA, risk assessment on work packages. Work now runs on a fast track. Yet without compromising on essential tasks e.g. audits.
Stakeholders simplified communicating project performance & progress, both formally & informally primarily to:
Tip! - Keep reporting on progress & performance to a minimum but at an acceptable level or standard. Check with the customer regularly for feedback on communications & clarity.