-
Notifications
You must be signed in to change notification settings - Fork 51
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add how to conduct delivery report (#90)
* add how to conduct delivery report * fix: add quote to title
- Loading branch information
1 parent
0005b06
commit 7cb0f4d
Showing
2 changed files
with
57 additions
and
0 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
--- | ||
tags: | ||
- delivery | ||
- reporting | ||
title: 'How to conduct delivery reports' | ||
date: 2024-08-01 | ||
description: How we conduct insightful delivery reports that ensure transparency, improve team performance, and enhance client relationships | ||
authors: | ||
- thanh | ||
--- | ||
|
||
Our goal is to allocate resources efficiently, assign the right staff to the right tasks, and address issues appropriately. At a high level, our delivery report will answer three key questions: | ||
|
||
1. **Did we help the client achieve their targets?** | ||
2. How did the team perform? | ||
3. Are there any problems that need to be resolved? | ||
|
||
Below is the process that our delivery team follows to answer these questions effectively: | ||
|
||
### Data Gathering | ||
|
||
#### Artifact Collection | ||
|
||
Collect the proof of work each project team delivered during the month. This includes: | ||
|
||
- Demo materials (videos, screenshots) | ||
- Updated project charters, documents, diagrams, and source code | ||
- Logs of roadblocks, issues, and technical debts | ||
|
||
From this process, we also observe and gather potential problems, both technical and managerial. | ||
|
||
#### Team Performance | ||
|
||
Evaluate the team's performance based on the following criteria: | ||
|
||
- Do account managers advocate for and ensure the interests of the client? | ||
- Do tech leads/project managers consult with the client on development matters? | ||
- Do tech leads/project managers ensure delivery quality and effective team management? | ||
- Assess each team member's performance and workload (to be discussed with team leads). | ||
|
||
#### Project Priority | ||
|
||
Assess the importance of each project based on factors such as: | ||
|
||
- Deal size | ||
- Potential to open new opportunities | ||
- Strategic partnerships | ||
|
||
### Conducting the Report | ||
|
||
Once all data is collected, we compile it into a report with highlights for the following items: | ||
|
||
- **Project Sorting by Importance:** Rank projects based on their priority and significance to our overall goals. | ||
- **Client Happiness and Performance Ratings:** Rate client satisfaction, lead performance, and account performance on a scale of 1 to 5. | ||
- **Issues and Resolutions Logs:** Document any issues encountered and the resolutions implemented. | ||
|
||
![](./assets/delivery-report-sample.png) |