Notes on Reporting Progress (ii)
These short notes are expanded from the previous blog article. The project progress report may present concise information such as –
Information may be presented on a presentation deck or a simple single page i.e. pdf. The % completion may be on schedule completion or cost completion, or computed in a method agreeable by all parties. A reliable tool is usually adopted for the purpose.
For impact, include a calendar to highlight visually the workload of the project, e.g. |
User Acceptance Tests (documentation)
Categories:
Risk Management
Categories: Risk Management
This article continues from my notes on acceptance testing in my region. The acceptance report or UAT Report as is typically known, is outlined here — A UAT Report may be progressive such that it presents the summary of acceptance tests that are in progress at any time a report is needed, or a summary of concluded acceptance tests. It records the aggregation and or finality of test results, observations, discrepancies/deviations from the RTM, and resolutions if any that were made during the course of testing. 💯 The report may include out of scope testing such as tests or retests brought forward from a previous UAT regime. Or mention of (significant) outcomes from testing beyond formal test cases. The final report is usually signed-off by the parties involved. The document may serve as a binding document that the planned tests are conducted, and present plans i.e agreement for completing whatever else that may be outstanding after the tests. A UAT Report may comprise contents e.g.
A UAT Report in essence-
How do we create an acceptable UAT Report?
References & past notes on the same topic:
. |
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 –
|