This is six class periods of steady progress. You are not expected to finish the whole CBA 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 __

Write today's one-line aim now, then reopen your files and start.

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 Strand 2 website piece and add a short reflection"). Teams agree who is on build, test, and evidence this period. Reopen your files.

During the period

1. Build or curate the next real piece of work against your milestones.
2. 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).
3. When something fails, use the debug questions on the board strip.
4. Leave evidence after each solid chunk:
   Date: __ / Did: __ / Tested: __ / Result: pass or fail / Decision: __ because __

End of each period

Show one test to a teammate or neighbour. Rewrite your one-line aim if it changed. Teams rotate build / test / evidence roles. Save everything the class way.

You are not expected to finish the whole CBA 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.

Same loop as before: aim, build or curate, test, evidence, save. Use the board strip and the evidence frame you already know.

Done for this period:

• critical piece moved forward
• one visitor-test note (what confused them)
• evidence frame filled for each solid chunk
• work saved and opens from the shared place
• tomorrow's aim in one line

Start of each period

Reopen files. Write today's one-line aim (chase the critical piece first). Teams rotate roles.

During the period

1. Chase the critical piece that unblocks everything else.
2. Visitor test (once in this stretch). Swap devices with another pair or a portfolio student for about five minutes. Watch where they hesitate. Note one confusion and one change you will make because of it.
3. Keep the trail on the usual frame. If you used allowed AI help, note what it did and what you checked yourself.

End of each period

Show one test (or one improved portfolio note) to a neighbour. Save and confirm the file opens from the shared place. Leave tomorrow's aim in one line.

End of this whole block

One decision I changed because of a test (about three minutes): each team or portfolio student names one decision out loud to a neighbour or in a quick whip-around.

You are not expected to finish the whole CBA in these periods. Steady, tested progress you can explain is the goal.