Day 10 Task 03 Results

Task 03. Sum Up Project Results

With Codex, finish a results report, a Keep/Problem/Try retro and a Version 2.0 roadmap with MoSCoW priorities.

Task 03 Project Results Lab Guide

📥 Lab input

  • • day10_project_summary.md

💾 Lab output

  • • day10_retrospective.md

1. Story and lab background

After the launch, the team gets together. The CEO says, "Great work over 10 days. Now we need a results report to show investors and an improvement plan for the next version." The last task is to objectively sum up the 9 days of development and clearly document what went well, what fell short and how to do better next time. Given a project overview, Codex quickly makes a draft results report.

2. Learning goals

  • Summarize the whole project into a results report stakeholders can easily understand.
  • Learn the Keep/Problem/Try retro method that analyzes strengths and improvements in balance.
  • Learn how to use AI to logically organize a Version 2.0 improvement roadmap with MoSCoW priorities.

3. Codex AI Prompt Card

Copy the prompts below, paste them into Codex Client and get the results.

Based on how the project went and its results, write a project results report for investors and stakeholders. Include background, goals, key features, results and improvement sections.
Looking back on this project, analyze the 3 things that went best and the 3 biggest regrets. For each, include specific reasons and how to improve next time.
Write a Version 2.0 development roadmap based on features we didn't finish and user feedback. Organize it with the MoSCoW (Must/Should/Could/Won't) priority method.
← Previous step Next step →