43 lines
2.6 KiB
Markdown
43 lines
2.6 KiB
Markdown
---
|
||
sidebar_position: 6
|
||
---
|
||
|
||
# Evaluation and Measurement
|
||
|
||
To determine whether the new workflow provides tangible benefits, it is essential to establish clear evaluation criteria. This will help measure success, identify areas for improvement, and provide data-driven justification for scaling the workflow to larger teams and projects.
|
||
|
||
## 📊 Evaluation Categories
|
||
|
||
The pilot project will be assessed across the following key areas:
|
||
|
||
| 📌 **Category** | 🔍 **Evaluation Focus** | 📈 **Measurement Method** |
|
||
|----------------|--------------------------|----------------------------|
|
||
| **Process Efficiency** | Was the new workflow easier to follow and maintain? | - Compare time spent in each phase vs. old projects<br></br>- Count handoff errors, missed steps, or unnecessary revisions |
|
||
| **Cross-Team Collaboration** | Did departments work together more effectively? | - Track the number and quality of cross-team syncs and feedback loops<br></br>- Survey team members on communication clarity |
|
||
| **Tool Adoption** | Were new tools (e.g., Gitea, Notion, Figma) effectively used? | - Review activity logs, usage frequency, and team feedback<br></br>- Identify which tools improved productivity |
|
||
| **Output Quality** | Did the project result in a more stable, polished product? | - Monitor bug count and severity at each phase<br></br>- Assess playtest feedback and visual/polish consistency |
|
||
| **Team Engagement** | Did the team feel more involved, empowered, and clear on responsibilities? | - Conduct anonymous surveys<br></br>- Use retrospective sessions to gather qualitative feedback |
|
||
| **Knowledge Retention & Documentation** | Was knowledge better preserved and shared across departments? | - Check completeness of GDD, art specs, test plans, and changelogs<br></br>- Evaluate how easily new members could understand the project state |
|
||
|
||
---
|
||
|
||
## 🧾 Reporting Structure
|
||
|
||
After the pilot project is completed:
|
||
|
||
1. **Internal Retrospective Meetings**
|
||
- Each team (GD, Art, DEV, QC) conducts a mini retrospective
|
||
- Identify what worked, what didn’t, and proposed changes
|
||
|
||
2. **Cross-Department Debrief**
|
||
- A full-team meeting to review interdepartmental collaboration and tool usage
|
||
|
||
3. **Final Evaluation Report**
|
||
- Compiled by the Project Lead
|
||
- Includes metrics, feedback, and recommendations
|
||
- Used to determine whether to scale, revise, or pause the new workflow
|
||
|
||
---
|
||
|
||
By combining **quantitative metrics** and **qualitative feedback**, we ensure that the evaluation reflects not only speed and output—but also long-term sustainability, team morale, and development quality.
|