Start Right
A project manager confided she was distressed by complaints from her project teammates and customers; and being bogged down with increasing workloads. Her peers complained about how people on the project relate to one another, and customers throwing tantrums at her and the team without regards for courtesy. Because she engages people on their gripes, she has realized that she dealt with people issues more than in clearing her own work. How should she recover and move forward? TBH, I tend to think there isn’t a generic answer. I’d say she should have Started off on the right foot at the start of the project. That's harsh :-P .. There should be experience from running projects and lessons learned from past projects – if not by herself, from others on and outside her project team. (In this KA, in assessing stakeholders at the start of a project). Regardless, she is already in the situation. A way forward could be to Ease off from the noise. Gradually change her approach or style in managing her project. There are many resources and professional help, out there to maybe resolve or deal with the specifics of her predicaments; I’d suggest to –
It is a commendable principle and practice, by and large, to be attentive, to listen more and acknowledge what was said. In the context of work and that of a project, perhaps conversations ought to weigh in more on what the time is meant for → work lah. While it is virtuous to be human, it can be said there is a right time for the right conversation. Be firm, suggest a time and place for casual chats (if you can, make the time). I find it helpful, to steer clear from –
|
Documents Supplied for Post-HOTO
Categories:
Communications Management
Categories: Communications Management
Notes on Documenting Acceptance Tests
This blog extends my previous notes on what may constitute a document for acceptance tests. The points are brief, and may not reflect what is practiced in your region or project. Typical information required:
The acceptance test document may include appendices to conclude the test:
There was an incident where the external auditor of the customer, questioned the unfilled frames and scribbles outside of fill-in frames on hardcopy test forms. This occurred despite the testers having been briefed on protocols. The problem here is that incomplete filling and off-witted remarks on a formal test document can cast doubt or uncertainty on the test outcome. As such I would emphasize the inclusion of a chapter or section on procedures for completing test cases, i.e. specifically on executing specified tests and filling-up test case forms. Regardless of whether the forms are hardcopies or digital (such as using a purpose driven app on a tablet). I would place this as the first section of the test procedures. It should define information e.g. as follows –
See also my notes for training on –
|
Notes on Handling Over & Taking Over
The Handover and Takeover process (HOTO as is known affectionately in my circles) i.e. handling-over and taking-over of works affects all of us. These are notes on HOTO for my team newbies :-P HOTO happens when:
IMO the most problematic aspect of HOTO is taking over a project; for that matter even taking over an ongoing project activity. The reason being the outgoing incumbent is in the know, whereas the incoming manager is in the unknown. And is unlikely that everything will be made known. The brief below, focuses on the taking over process. The following steps generalize what should occur when taking over a project, particularly:
Similarly, when handling over a project, work with whoever is coming onboard to agree on the status of project, complete all outstanding tasks, and update all project documents. That way you’ll mitigate whatever work you have done in the past from coming back to haunt you. As with all guidelines, you will have to adapt recommendations of best practices, past experiences, and lessons learned to craft your own processes and procedures. The table below exemplifies common tasks which should be completed throughout the HOTO period:
Exemplify typical tasks before, during, after HOTO When a project transitions to operations, the project team may have to supply operations or supporting documents (click here) to facilitate smooth operations. |
Notes on Reporting Progress
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.
|