Tuesday, 22 July 2014

End of Day Reporting - Worked Example


Reporting the status of testing, at whatever stage, is critical to effective management and ensuring the business is confident about our ability to deliver. Reporting accurately, consistently and frequently are key. It would be great to have a tool that did all the reporting for us, but often we don't have a test management and reporting tool in place. In fact, sometimes the tools we get burdened with are more trouble than they're worth, being unable to produce the reporting we want. Either in the style we need or with the ease we'd like to see. In that case, Excel and Word along with a simple email become our best friends. If we do revert to this simpler approach, we still need to ensure accuracy and consistency.

When working as a member of a team or as a consultant, my preference is always to send an end of day report out.
The benefits of doing so include:

* Ensuring you have a think-through of what the status actually is, what you need to be doing and any issues that you need to raise
* Providing information to the line manager and stake-holder that they can take into their own meetings and reporting
* Creating a record that can be referred to in post implementation reviews, to help identify areas to be improved on

The main trick with these reports is to keep them short. My rule-of-thumb is that if it takes more than 5 to 10 minutes to complete, it's too long. The EoD update should be simply collating what you already know and information you already have, into an easily digestible email or post on some internal forum perhaps. There are many ways to structure these EoD updates, but here's what I'd typically expect to include, in the style I'd provide it.

The objective is to keep them informed at a high level. Imagine they're stopped by the project sponsor and asked "How are things going?", the below should be enough to answer the question. Remember, it's just a snapshot. If the audience for this wants more information they need to dig.

In the next post, we'll look in detail at a Excel Daily Status Tracker workbook that can be used for this.

Mark.

------------------------------------------------------------------------------------------------------
Example Project - EoD Update: Tuesday 22nd July, 2014

Current RAG: Amber
Planned Complete Date: Mon 21st July, 2014
Expected Complete Date: Thu 24th July, 2014

Summary
Due to environment downtime, caused by network outage, progress for execution is 10 Test Cases behind schedule. The issue was escalated and is now resolved. Expectation is delivery will be back on plan by Friday 25th.

Of 126 Test Cases in scope:
- Execution is 10 Test Cases behind plan
     - Total executed to date is 87 (+7) or 69% (+6%) , of which;
        - 65 (+6) Passed
        - 12 (-2) Failed
        - 10 (+3) Blocked

Comments
- 3 Test Cases Blocked due to test data being for transactions already expired. Will create new data tomorrow and execute as a priority
- 12 Cases in a Fail state with Development, 2 Fails retested and passed
- Team will conclude Feeds testing tomorrow and move onto Reporting and Transactions areas
- Pleas note: David is out of the office Thursday, therefore no Test Cases for Reconciliations will be executed


Daily Tracker Chart
 

----------------------------------------------------------------------------

Liked this post?


0 comments: