Week 9: Iteration 2 readiness and review#

Studio abstract#

In this studio, your team will inspect how its Iteration 2 work currently moves from an idea to a reviewed result. You will improve the team’s GitHub Project workflow, identify a repeated activity that could be documented as a repository skill, practise concise peer feedback and apply the improved workflow to current project work.

The activities total 140 minutes and begin after the 30-minute innovation seminar and a 10-minute transition.

By the end of the studio, your team should have:

  • made its current Iteration 2 work visible on its GitHub Project;

  • agreed when work is ready to begin and when it is genuinely done;

  • added an explicit review step to its workflow;

  • traced one task through the board and repository;

  • outlined one potentially useful repository skill;

  • practised giving short, behaviour-based peer feedback; and

  • advanced and reviewed its highest-priority Iteration 2 work.

From the seminar to your project#

The seminar introduced software development as a connected process of discovery, delivery, review and adaptation. A board is not the process by itself: it is a shared representation of how work is expected to move.

You created a GitHub Project in Week 4. Do not create another one. Work with the board, repository and Iteration 2 tasks your team already has.

1. Inspect the current workflow#

⏱️ 15 minutes — team

Open the team’s GitHub Project and repository. Begin with the familiar board:

Todo → In Progress → Done

Compare the board with what the team is actually doing. Identify:

  • work being done that is not visible on the board;

  • tasks that are too large or too vague to finish predictably;

  • tasks without one accountable owner or a specific deadline;

  • work that is blocked but does not appear blocked;

  • tasks marked done without review or evidence; and

  • too many tasks being attempted at the same time.

Choose the two most important workflow problems to address today.

2. Improve how work flows#

⏱️ 20 minutes — team

Expand the board to include a review step:

Todo → In Progress → Review → Done

Agree on simple movement rules:

  1. Ready for In Progress: the task has a small, observable outcome, one accountable owner and a credible deadline.

  2. Ready for Review: the intended change or evidence exists, is accessible and includes enough context for another person to check it.

  3. Ready for Done: the agreed review has occurred, required corrections are complete and the result is visible in the appropriate project record.

Limit how much work is in progress. Finishing and reviewing a small number of important tasks is more useful than starting many tasks that remain incomplete. Make blockers visible rather than quietly moving deadlines.

Choose one real Iteration 2 task and trace its intended workflow:

Project task → branch → focused change → pull request → review → merge → Done

The exact workflow can vary with the work. For example, an interview or prototype test may require evidence and privacy review rather than automated tests. Record the quality gate that applies to the selected task.

3. Identify a workflow that could become a skill#

⏱️ 20 minutes — team

The create-interview-record skill introduced earlier is a documented workflow. It has an intended purpose, known inputs, ordered steps, checks, an output and explicit boundaries. The same workflow can be followed through three pathways:

  • No AI: a person reads SKILL.md and follows the procedure manually.

  • Hosted AI: a hosted coding agent follows the skill using material that is safe to provide to that service.

  • Local AI: an agent with a model running locally follows the same skill, subject to the team’s tool and privacy checks.

The pathway may change; the intended output and human review expectations do not.

Do not begin by asking, “What AI skill should we make?” Begin with the team’s work:

  1. What do we repeat?

  2. Where do we commonly omit a step or make an avoidable mistake?

  3. What input and output should be consistent?

  4. What must always be checked before the result is accepted?

  5. Which judgement must remain with a person?

Select one promising activity. Outline—but do not yet implement—a possible skill:

Element

Team decision

Purpose

What useful outcome would the workflow support?

Inputs

What information or files may it use?

Steps

What sequence should be followed?

Checks

What must be verified, and by whom?

Output

What observable result should it produce?

Boundaries

What must it never receive, invent or decide?

A skill is not automatically useful because it uses AI. It is useful when documenting the workflow makes repeated work safer, clearer or more consistent.

Break#

⏱️ 10 minutes

4. Practise concise peer feedback#

⏱️ 20 minutes — introduction and pairs

Feedback is another short workflow: observe behaviour, explain its impact and support effective future behaviour.

Use this two-part peer-feedback model:

When you [observable behaviour], here is what happens [impact].

Keep feedback specific, brief and respectful. Describe behaviour that another person could observe rather than guessing attitude or intent. Give positive feedback regularly; do not save all feedback for when something has gone wrong.

In pairs within the team:

  1. each person gives one piece of positive feedback about a behaviour that has helped the project;

  2. each person identifies one workflow behaviour that would help the team during Iteration 2; and

  3. the pair checks that each statement describes observable behaviour and a concrete impact.

If a concern is serious, personal or connected to misconduct, do not force it into this short exercise. Speak privately with your legend or course coordinator.

5. Apply the workflow and review Iteration 2#

⏱️ 45 minutes — team project work and optional legend review

Use this time to advance the highest-priority prototype-testing or evidence task on the team’s board. Apply the workflow you agreed earlier:

  1. confirm the task’s observable outcome, accountable owner and deadline;

  2. make its review gate explicit;

  3. complete or substantially advance the work;

  4. ask another team member to review work that reaches the Review column; and

  5. move the task honestly and record any blocker or new task discovered.

Review the current Iteration 2 checklist before deciding that the submission is ready. Confirm that the competitor comparison covers 4–6 competitors plus the team’s own product. For COMP7110, also confirm that each team member has researched one competitor and documented its business model as a Business Model Canvas. The competitors used for those canvases can be among the team’s 4–6 competitors. Add an owned task for anything that remains incomplete.

Optional prototype review#

If time permits, ask your legend for a short formative check-in on where the prototype and solution testing are up to. Be ready to show:

  • the hypothesis and remaining uncertainty being tested;

  • the prototype and why its fidelity is appropriate;

  • any observations or evidence collected so far; and

  • the next test or change planned.

This is free project-working time and an optional progress review. It is not a presentation, an Iteration 2 requirement or a separate assessment.

Exit ticket and next steps#

⏱️ 10 minutes — team and legend

Show your legend:

  1. the updated board with Review represented explicitly;

  2. one Iteration 2 task with a clear owner, deadline and completion criteria;

  3. the quality gate that moves that task from Review to Done;

  4. the outline of one possible repository skill, including its human-review boundary; and

  5. the next project action agreed after reviewing the Iteration 2 submission, including any missing competitor-analysis work.

After the studio, keep the board aligned with the work actually being performed. Finish and review the prototype tests needed for Iteration 2, record the resulting evidence, and adapt the plan when the evidence changes what the team believes.