This is six class periods of steady progress. You are not expected to finish your whole project or portfolio here. Work continues between sessions and after this stretch.

Across these periods you will keep building or curating, test as you go, and leave a clear trail of what you decided and why.

Open the plan and milestones you set earlier, and open the project or portfolio pieces you already have. If something is missing, ask your teacher or rebuild the missing piece from your plan before you push on.

Your job across these periods:

• Build or curate against the milestones you already wrote.
• Test as you go, so problems show up early rather than at the end.
• Keep evidence of what you tried, what broke, what you changed, and why.

Use this evidence frame every time you stop a chunk of work (copy it into your notes):

Date: __ / Did: __ / Tested: __ / Result: pass or fail / Decision: __ because __

Start by writing today's aim in one line, so you know what finished looks like before you open anything, and then reopen your files and get going.

Done for this period:

• one thing works better than when you opened it
• one test result written (pass or fail)
• evidence note someone else could read
• work saved the class way

Start of each period

Write today's aim in one line at the top of your evidence notes, for example "get the login flow working" or "improve the website piece and add a short reflection". If you are in a team, agree who is on build, who is on test and who is on evidence this period before anyone opens a file, and then reopen your work.

During the period

• First, build or curate the next real piece of work against your milestones.
• Then test as you go. After each meaningful change, run or review it. Try the happy path, then try one way to break it (wrong input, missing file, empty list, or a classmate who does not know the controls).
• When something fails, use the debug questions on the board strip.
• After each solid chunk, leave evidence:
• Date: __ / Did: __ / Tested: __ / Result: pass or fail / Decision: __ because __

End of each period

Show one test to a teammate or neighbour so someone other than you has seen it work, and rewrite your one-line aim if the work moved somewhere you did not expect. Teams then rotate the build, test and evidence roles for next time, and everyone saves the class way.

You are not expected to finish the whole project or portfolio in these periods. Steady, tested progress is the goal.

Pause the build. Look only at your milestone sheet and your evidence notes.

• Which milestones are done, partly done, or not started?
• What did testing teach you that planning alone did not?
• What will you protect in the next block of time so the important piece actually moves?

Adjust the plan if you need to. A smaller, honest plan you can finish well beats a huge plan you abandon. Write the adjusted next aim before you go back to the work.