Week 8 + 9: Final session β IP, Demo Day prep, peer evaluation
Team check-in β first 5 minutes
Honest answers. Immediate feedback on where your team stands.
Your session
Dev Log 20% of grade
Validation sessions run 10% of grade Β· 5+ needed
Technical Documentation 15% of grade Β· due Week 11
Demo Day story 40% of grade Β· Week 10 (May 6β8)
Your team's picture β Week 8
| # | Mission | Time |
|---|---|---|
| 0 | π IP Strategy sprint | 30 min |
| 1 | π£οΈ Standup + sprint planning | 20 min |
| 2 | π¬ Validation β closing lap | Self-paced |
| 3 | βοΈ Build sprint β Demo Day as the constraint | Remaining time |
| 4 | π€ Peer Evaluation β how it works | 15 min |
| 5 | π Assessment overview + Demo Day briefing | 10 min |
| 6 | π Teaching quality survey | 10 min |
Mission 0 β IP Strategy sprint
Section titled βMission 0 β IP Strategy sprintβ30 minutes. One page in your Technical Documentation. Assessed on strategic thinking β not legal accuracy.
Three types of protection exist. One or more can apply to your project at the same time:
| Type | δΈζ | You already have it? |
|---|---|---|
| Copyright (ηζ) | ηζ | Yes β automatically. Your code is yours the moment you write it. |
| Patent (δΈε©) | δΈε© | No β you must apply, pay fees, and wait 1β3 years. |
| Trade secret (εδΈη§ε―) | εδΈη§ε― | Yes β if you keep it private and do not publish it. |
Your task β 30 minutes:
- Watch the video above.
- Discuss as a team: which of the three protections apply to your project? More than one can apply.
- Open the IP Strategy section of your Technical Documentation template and write one paragraph explaining which protection(s) you recommend and why. Use AI to help you draft it β but the reasoning must be yours.
Template: β¬ Technical Documentation β open Section 4 (IP Strategy) and fill it in today.
Want to do a prior art search or need more detail? The full AI research workflow, patent database links, and comparison tables are on the deep-dive page:
Mission 1 β Standup + sprint planning
Section titled βMission 1 β Standup + sprint planningβThree questions each, two minutes per person:
- What did I do since the last session?
- What will I do in this session?
- Any blockers?
After standup β update Kanban:
- Move completed tasks to Done
- Every developer has one task In Progress with their name on it
- Sprint goal: is everything you are building this week something you will demo on Demo Day?
Mission 2 β Validation β closing lap
Section titled βMission 2 β Validation β closing lapβ| Sessions run | What to do now |
|---|---|
| 0β1 | Run two sessions today. A paper sketch is enough. |
| 2β3 | Run one session today, one more before Week 10. You can reach the minimum. |
| 4 | One more session. You are close. |
| 5+ | Write up any undocumented sessions. Make sure you have one iteration documented: finding β change β test again. |
One strong before/after finding is worth more than five sessions with no changes.
Quick session (20 minutes):
- Opening (2 min): βWe are testing the product, not you. Think out loud.β
- Task: βImagine you want to [goal]. Show me what you would do.β β then stop talking.
- Observe (15 min): Where do they pause? What do they try first?
- Debrief (3 min): βWas anything surprising?β
- Write it up (10 min): Who Β· what you showed Β· what they did Β· one change you will make.
See the Validation Guide for the full template.
Mission 3 β Build sprint β Demo Day as the constraint
Section titled βMission 3 β Build sprint β Demo Day as the constraintβWeek 8 is the last instructional session. Week 9 is open rehearsal β use it to practise, not to build features you have not started yet.
One question for every Kanban task: Will this appear in the demo?
| Situation | What to do |
|---|---|
| Nice-to-have, not in the demo | Cut it. The demo is 2.5 minutes. |
| Core use case not working | This is the only priority. Everything else waits. |
| Demo works but feels rough | Polish the demo flow only β no new features. |
| Demo-ready | Practise it. Time it. Then work on documentation. |
Test this today: Give your laptop to someone outside your team. Ask them to complete the core task without guidance. If they cannot do it, that is your sprint goal.
Commit standard:
feat: user can complete [core task] without errorsfix: [specific issue] no longer blocks the demo flowdocs: IP Strategy section added to Technical DocumentationMission 4 β Peer Evaluation β how it works
Section titled βMission 4 β Peer Evaluation β how it worksβPeer Evaluation is part of your individual grade (30%). It is separate from Demo Day and separate from your pathfinderβs assessment. Your teammates rate you β you rate them.
What you are rated on:
| Category | What assessors look at |
|---|---|
| Reliability | Did you complete your tasks? Meet deadlines? Communicate blockers early? |
| Quality | Did your work meet the standard? Did you put in real effort? |
| Initiative | Did you help proactively? Did you solve problems without being asked? |
| Communication | Were you responsive? Did you attend meetings and check-ins? |
How the score converts to your grade:
- Each category is rated by your teammates
- Ratings are averaged across your team
- The result converts to 0β15 points added to your final grade
- A strong individual rating can lift your personal grade above your teamβs group score
Ratings are confidential. Your teammates will not see what you wrote about them. Your pathfinder sees the results.
Rate honestly β not generously. If a teammate did not contribute, rating them high does not help them. It makes the evaluation useless. Be fair.
When and where:
- Due: Week 11, Sunday May 15, 23:59
- Where: Download the form from LMO, complete it, submit via LMO
- Who fills it in: Every team member independently
/ completed — progress saved in your browser
Mission 5 β Assessment overview + Demo Day briefing
Section titled βMission 5 β Assessment overview + Demo Day briefingββ Stefanβs briefing β Demo Day is Week 10 (May 6β8)
Demo Day is 40% of your grade. Here is what assessors look for:
| Element | Weight | What scores well |
|---|---|---|
| Prototype Demo | 15% | Core use case works end-to-end Β· handles the expected flow |
| User Validation Evidence | 10% | Real sessions shown Β· before/after iteration |
| Presentation Quality | 10% | Clear story Β· exactly 6 min Β· professional slides |
| Technical Q&A | 5% | Can explain choices Β· understands trade-offs |
Validation Evidence (10%) is worth double Q&A (5%). A simple product with strong evidence of learning outscores a polished prototype with no evidence of user testing.
Uncomfortable truths score higher than glossy prototypes. βUsers couldnβt find X, so we moved it β here is the before and afterβ is a stronger Demo Day moment than five positive quotes.
Your 6 minutes:
| Section | Time |
|---|---|
| The problem β who has it, one real user quote | 1 min |
| What you built β one sentence | 30 sec |
| Live demo β core use case only, show donβt explain | 2.5 min |
| What users told you β two findings, one before/after | 1 min |
| What comes next β one honest limitation | 1 min |
Before you leave, agree as a team:
/ completed — progress saved in your browser
β Full Demo Day guide with rubric and Q&A tips Β· β Assessment Overview
Live Q&A β open the queue now:
- Open the Live Q&A page in a new tab.
- Upvote any question your team also has.
- Add a new question if something is unclear. Stefan answers live in Hour 3.
Team question β answer out loud before moving on:
βIf Demo Day were next week β what is the one thing we are most embarrassed by?β
That answer is your priority for Week 9.
Mission 6 β Teaching quality survey
Section titled βMission 6 β Teaching quality surveyβ
Scan or open mymq.xjtlu.edu.cn β log in with your XJTLU account, then select ENT208TC Industry Readiness.
Ten minutes. Your feedback directly shapes how this module runs.
Before you leave
Section titled βBefore you leaveβ/ completed — progress saved in your browser
Was this page helpful?