1. Story and practice background

After launching the service, the team members gathered together. The representative says: ‘You worked really hard for 10 days. Now we need a result report to show to investors and an improvement plan for the next version.' The final task is to objectively organize the 9-day development process and clearly document what went well, what was disappointing, and how we can do better next time. Codex quickly creates a draft report upon receiving the project outline.

2. Learning objectives

• You can summarize the entire project process and create a results report that stakeholders can easily understand.
• You can learn the Keep/Problem/Try retrospective method to analyze what went well and what needs to be improved in a balanced manner.
• Using AI, you can learn how to logically organize the Version 2.0 improvement roadmap with MoSCoW priorities.

3. Codex AI prompt card

Copy and paste the prompt below into Codex Client and receive the results.

Based on the project progress and results, write a project results report that can be delivered to investors and stakeholders. Include sections for background, goals, key features, accomplishments, and areas for improvement.

When you look back on this project, please analyze the three best aspects and three most disappointing aspects. For each item, include a specific reason and how it can be improved next time.

Please create a Version 2.0 development roadmap based on the features not completed in this project and user feedback. Organize it with the MoSCoW (Must/Should/Could/Won't) priority methodology.