description |
---|
A team who manages, analyze and resolve issues in resource assignment and daily log practice. |
Traffic is the term we use for managing resources in development state. Here are the responsibilities
Responsibility | Day to day activity | Note |
---|---|---|
Resource allocation forecast | To forecast resource allocation up to 1 or 2 months onwards (including pandora too) | Assisted by Hokage |
Resource allocation planning |
|
Assisted by Hokage |
Resource allocation monitoring |
|
Based on daily log vs estimation & plan |
Resolve and clarify resource issues | Analyze and resolve resource issues in daily basis for both PM and coaster's point of view | Issues like below:
|
You can check the guideline below regarding how to do resource assignment for both Traffic/Development and Pandora.
Resource Assignment - What & How
Pandora is a term we use in managing project in pandora project. Pandora is a status when a project is still in a pitching state. So, it's not deal with RGB yet. But we still need to prepare the resources if the it finally deal.
Responsibility | Day to day activity | Note |
---|---|---|
Manage pandora execution process | Manage task ticketing via Proofhub (BA, design, PgM) | |
Resource allocation forecasting | Create a resource allocation planning for pandora if the pandora deal. |
Test
Responsibility | Day to day activity | Note |
---|---|---|
Daily log monitoring |
|
Settle any issues that can be settled directly (by the daily log manager) and report to the traffic team. |
Recap and analyze the daily log | Recap and report weekly mandays usage or based on the cycle (via Data Studio) | |
Resource allocation monitoring | Monitor and control the daily resource allocation based on the plan | e.g make a report or a list about which resources are idle in the previous week. |
Daily log format check | Ensure daily log format that written by every coaster is correct |
|
Assessment support | Comparing mandays usage with result delivered, quality, and the pace |