Week 6: Iteration 1 readiness and review#

Studio abstract#

In this studio, your team will review its Iteration 1 project record as a coherent evidence trail, identify and resolve gaps, prepare individual reflections, and confirm the point-in-time repository ZIP for Blackboard. Legends will assess the repository and its history; Blackboard keeps the ZIP as UQ’s submission record.

The Iteration 1 submission is due for both COMP1100 and COMP7110 at 4:00 pm on Friday 4 September 2026.

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

  • a coherent account of its customer-discovery findings;

  • traceable links from hypotheses to evidence, learning and decisions;

  • a repository that follows the supplied structure and contains no restricted interview material;

  • visible, meaningful contributions from every team member;

  • an honest individual self-assessment and a plan for the required reflection;

  • a small set of assigned tasks for any remaining gaps; and

  • rehearsed the process for creating the Blackboard repository ZIP.

What is submitted and what is assessed#

Iteration 1 has two components:

  1. Team project record: the team’s first-iteration customer-discovery findings and supporting project evidence.

  2. Individual reflection: a short reflection completed by each student using the instructions in Blackboard.

The team repository is the working and assessment record. Legends will use its files, history, pull requests and each student’s discussion of the work when reviewing contribution. The team also uploads a ZIP of the repository to Blackboard as a point-in-time UQ audit record.

Raw recordings, consent records and identifiable transcripts remain in the team’s approved secure Microsoft Teams storage. They are not committed to GitHub and are not included in the repository ZIP.

Readiness check 1: Tell the customer-discovery story#

⏱️ 25 minutes — team

Without opening the repository, agree on a short answer to each question:

  1. What problem area did the team investigate?

  2. Which customer segments did the team investigate, and why?

  3. What were the most important original hypotheses?

  4. How did the team test them?

  5. What did the evidence support, refute or leave unclear?

  6. What themes, contradictions and limitations did the team find?

  7. What did the team retain, refine, reject or decide to investigate next?

Now open the repository. A reader should be able to recover the same story from the project records without relying on undocumented verbal explanation. Record any missing or contradictory part as a GitHub Project task.

Readiness check 2: Audit the evidence chain#

⏱️ 35 minutes — pairs within the team

Split into pairs and trace the team’s most important hypotheses through the repository:

Business model assumption
  -> hypothesis and test card
  -> deidentified evidence records
  -> cross-interview synthesis
  -> learning card
  -> decision
  -> current business model canvas

Check that:

  • hypotheses are specific and testable;

  • tests and interview questions address the hypothesis;

  • claims are traceable to real evidence records;

  • evidence, observations and interpretation remain distinct;

  • learning cards represent supporting, refuting and uncertain evidence fairly;

  • decisions follow from the evidence and acknowledge limitations;

  • the current BMC distinguishes evidence-supported findings from assumptions; and

  • links work in GitHub’s rendered Markdown.

Do not fill gaps by inventing evidence or rewriting participant material. If the evidence remains inconclusive, say so and describe the next useful test.

Readiness check 3: Privacy, security and AI assistance#

⏱️ 20 minutes — team

Search the repository, including open branches and pull requests, for material that should not be in Git. Confirm that it contains no:

  • participant names, contact details or identifiers;

  • consent forms or consent-record images;

  • raw recordings or direct recording links;

  • identifiable transcripts;

  • precise private locations or sensitive account information; or

  • credentials, access tokens or private keys.

Confirm that participant codes are non-identifying and that secure source references do not expose private URLs.

For agent-assisted work, check that:

  • only safely deidentified material was supplied;

  • material assistance is disclosed;

  • a team member checked the output against the source;

  • unsupported claims and invented detail have been removed; and

  • the team can explain and defend every submitted decision.

Using a repository skill does not transfer responsibility to the tool. Human judgement and review are required for every pathway, including manual work.

Take a break#

⏱️ 10 minutes

Contribution and collaboration review#

⏱️ 25 minutes — individual and team

Each person reviews their contribution evidence:

  • meaningful commits made under their own account;

  • branches and pull requests they created or reviewed;

  • interview, analysis, documentation or planning work visible in the repository;

  • GitHub Project tasks they owned and completed; and

  • team decisions, meetings and studio activities in which they participated.

Large last-minute commits do not explain the development process as clearly as regular, focused contributions. If work was completed outside the repository, record the legitimate project outcome now, but do not falsify dates, authorship or history.

As a team, check that the repository represents shared work and that every member understands the overall customer-discovery story, not only the files they edited.

Individual self-assessment and reflection preparation#

⏱️ 30 minutes — individual

Review the current competency criteria in the course notes and the individual-reflection instructions in Blackboard. For each relevant competency, write brief notes answering:

  1. What did I do?

  2. Where is the evidence of that contribution?

  3. What did I learn?

  4. What would I do differently?

  5. What specific action will I take in Iteration 2?

Use a specific experience rather than a general claim such as “I communicated well”. A strong reflection connects the experience, its effect on the team or project, what you learnt, and a realistic action plan.

This self-assessment is preparation. Follow the Blackboard instructions for the actual individual reflection.

Plan and complete the remaining work#

⏱️ 30 minutes — team

Open the Iteration 1 view in GitHub Projects. For every remaining gap:

  • create or update a measurable task;

  • assign one accountable person;

  • give it a specific due date and time;

  • identify the file, review or submission outcome that will demonstrate completion; and

  • include peer review where appropriate.

Use the remaining studio time to complete the highest-priority tasks while your legend is available. Merge only reviewed work and leave enough time before the deadline to inspect the combined repository.

Rehearse the point-in-time submission#

⏱️ 15 minutes — team

Before the deadline, the team will:

  1. confirm that the intended submission version is pushed to the team repository;

  2. confirm that all required work has been reviewed and is visible to the legend;

  3. check that the repository contains no restricted or sensitive material;

  4. create a ZIP of that same repository version;

  5. inspect the ZIP contents before uploading; and

  6. upload the ZIP to the correct Blackboard assessment item before 4:00 pm Friday 4 September 2026.

The ZIP is the point-in-time audit record. Legends will use the repository and its history for assessment.

Exit ticket#

Show your legend:

  1. the team’s coherent customer-discovery story;

  2. one complete evidence chain from hypothesis to BMC decision;

  3. the completed privacy and AI-assistance audit;

  4. each person’s contribution evidence and reflection plan; and

  5. the assigned tasks and timetable for resolving every remaining gap.