Group Project Skill

Do not use this skill if the lesson is mainly about:

• launching the unit
• teaching a new accounting principle
• teaching a new Excel tool for the first time
• using the same teacher data for every group

Use project-rehearsal when the whole class works from the same teacher-controlled dataset before the real project begins.

Core Writing Rules

• Each group gets its own assigned dataset or starter workbook.
• The workbook structure must match the rehearsal lesson exactly unless the lesson explicitly names a project-wide extension.
• Do not invent a new workbook architecture for the project.
• Keep the teacher and student language focused on milestone progress and evidence.
• Require teams to cite numbers from their own workbook, not generic claims.
• Treat peer feedback as revision input, not a formality.
• Keep authentic audience expectations visible.

Structural Rule

Project lessons in this repo are milestone-style lessons. Default to a single structured milestone page rather than a six-phase lesson unless the unit already establishes a different project format.

That page should still include:

• context
• objectives
• workflow
• acceptance criteria
• checklist or rubric
• reflection or handoff

Non-Negotiable Workbook Rule

Each group's workbook should use the same sheet structure, evidence chain, and dashboard logic as the rehearsal workbook.

What changes:

• the group's dataset
• the group's business scenario
• the team's recommendation and evidence

What does not change:

• workbook architecture
• expected sheets or evidence blocks
• Definition of Done
• communication standard

Milestone Arc

Across lessons 8-10, the project arc should usually be:

1. kickoff and workbook setup
2. completion, testing, recommendation, and rehearsal
3. final presentation, submission, and reflection

Milestone Contract

Lesson 8: Kickoff and Workbook Setup

Purpose: Move teams from rehearsal into their own assigned scenario without changing the workbook structure.

Requirements:

• assign each group its specific dataset or starter workbook
• explain the business scenario, constraints, and target outcome
• require teams to rename, save, and organize the correct workbook
• start the first required sheets or sections
• define milestone 1 acceptance criteria

Evidence to require:

• correct workbook opened and named
• early sheets or setup blocks completed
• one draft claim or early direction statement

Lesson 9: Completion and Rehearsal

Purpose: Finish the core analysis, test the recommendation, and rehearse the explanation.

Requirements:

• continue the same workbook from lesson 8
• complete the remaining sheets or evidence blocks
• require scenario testing, checks, and dashboard completion
• require a short recommendation structure using claim, evidence, and risk
• include peer critique and revision
• define milestone 2 acceptance criteria

Evidence to require:

• complete workbook
• final recommendation draft
• cited workbook numbers
• peer feedback notes

Lesson 10: Final Presentation and Submission

Purpose: Present the final recommendation, submit the artifact, and reflect on the project.

Requirements:

• require final polish of workbook and presentation notes
• make the audience, presentation standard, and submission standard explicit
• include final checklist and timing guidance
• require reflection after presentation or submission

Evidence to require:

• final workbook
• final recommendation or presentation artifact
• submission confirmation
• reflection

Required Page Sections For A Milestone Lesson

A strong group-project milestone page should usually include:

• project context
• business objectives
• workbook or technical objectives
• group dataset or workbook access instructions
• workbook map or milestone build target
• workflow or timeboxing
• acceptance criteria
• submission checklist
• rubric or evaluation standard
• reflection or next-step handoff

Dataset and Workbook Assignment Rules

• List each group's dataset or starter workbook clearly.
• Instruct groups to use only their assigned file.
• Require teams to continue the same workbook across milestone lessons.
• If a workbook is missing, provide a recovery path such as re-downloading the assigned starter workbook and rebuilding from notes.
• Make file naming conventions explicit.

Workbook Structure Rules

Project workbooks should:

• preserve the rehearsal workbook structure exactly
• preserve the same evidence chain from setup to dashboard
• preserve the same logic expectations across sheets
• change only the business data and resulting analysis

Do not:

• rename core tabs casually
• remove evidence sheets just because the dashboard exists
• let groups create inconsistent workbook structures that break comparison or grading

Recommendation Rules

Every group-project lesson after kickoff should keep pushing teams toward:

• one clear recommendation
• at least three cited numbers from the workbook
• one risk, downside, or limitation
• one explanation of why the recommendation still makes sense

Peer Feedback Rules

Peer critique should:

• be tied to explicit criteria
• focus on model accuracy, evidence, clarity, and readiness
• require at least one concrete strength and one concrete revision target
• lead to visible revision before the final presentation when possible

Component Rules

Prefer components that:

• support checklist-driven progress
• support peer critique
• support reflection
• help students access the correct group files
• help students understand milestone expectations quickly

Use SpreadsheetWrapper for:

• workbook map previews
• example dashboard or evidence-chain snapshots
• structural reminders from the rehearsal model

Do not use SpreadsheetWrapper as a substitute for the actual group workbook.

What Not To Standardize From Weak Project Lessons

• project pages that feel disconnected from the rehearsal workbook
• workbook expectations that change by group structure instead of by data only
• vague milestone directions with no acceptance criteria
• peer critique with no required revision move
• presentation lessons that ask for a recommendation without requiring workbook evidence

Success Test

A strong group-project lesson should leave teams able to answer:

• What milestone are we completing today?
• Which dataset or workbook belongs to our group?
• How does our workbook structure match the rehearsal model?
• What exact evidence must we produce before class ends?
• What is our current recommendation, and what numbers support it?
• What do we still need to revise before the next milestone or final presentation?