Week 7: Frequently Asked Questions
Assessment
Section titled “Assessment”How do I do well in ENT208TC?
Section titled “How do I do well in ENT208TC?”💬 “How to get 100 in ENT?” ▲11
Show your thinking, not just your output. The pattern is the same across every deliverable: say what you did, and say why.
Some deliverables are group work — your team writes one shared Validation Report and one Technical Documentation. The quality of the reasoning in those documents reflects the whole team.
Some deliverables are individual — your Dev Log entry is yours alone. Write what you personally did this week. One paragraph, in your own words. If two people worked on the same task, describe your specific part — not the task itself.
Validation Report: Describe what happened in your sessions. “We moved the button after three users could not find it — in the next session they found it immediately” is stronger than “users found it easy to use.”
Technical Documentation: Explain why you chose each tool. “We chose Supabase because it generates a full API from our database — the frontend can read and write data directly from the browser without any server code” is stronger than “we chose Supabase because it is a modern backend.”
Demo Day: Be ready to explain every decision you made — not just what you built.
My product is not finished. Can I still present at Demo Day?
Section titled “My product is not finished. Can I still present at Demo Day?”💬 “Can I demonstrate partial functionality at Demo Day?” ▲1
Yes. Your validation evidence and Dev Log matter as much as the live demo. A product that is honest about what is missing — with clear reasoning — is a strong presentation.
When one part cannot be demonstrated live:
Some components may not be ready in time. A water pump that is not yet connected. Data from an external system like Learning Mall that you cannot access during the demo. You do not have to skip that part entirely.
Instead, you can simulate the component (this is called a mockup) — show how it would work using stand-in data or an alternative demonstration. The key condition: the rest of the product must still work end-to-end. You are substituting one specific part, not replacing the whole demo with slides.
Examples of acceptable simulation:
- Data you cannot access: Hardcode realistic sample data in your app so the interface works from start to finish — the user can see exactly what would happen with real data.
- Hardware that is not yet connected: Demonstrate the component working in isolation (the motor turns, the sensor gives a reading), then explain live how it fits into the full system.
This requires Pathfinder approval.
What counts as an acceptable substitution depends on your specific product and assessment criteria. Discuss your plan with your Pathfinder before Demo Day. If your Pathfinder is unsure, your group and Pathfinder should approach the Module Leader together.
View the assessment brief on Learning Mall →
Dev Log
Section titled “Dev Log”We shared tasks this week. How do we each write a Dev Log entry?
Section titled “We shared tasks this week. How do we each write a Dev Log entry?”💬 “Our tasks were shared across roles — how do we write individual Dev Log entries?” ▲2
The Dev Log has two parts. The group summary is written by your group leader — one entry for the whole team. Your individual entry is yours alone.
Write what you personally did — not what the team did. If you ran a session, write about that. If you designed a screen, write about that. If two people worked on the same task, describe your specific part. One paragraph, in your own words.
Kanban and GitHub
Section titled “Kanban and GitHub”Is Kanban graded? Do GitHub commits count?
Section titled “Is Kanban graded? Do GitHub commits count?”💬 “Is Kanban mandatory? Is GitHub in the final score?” ▲5
Neither is a separate graded item. Your pathfinder checks your Kanban board at Checkpoint 1 (Week 6) and Checkpoint 2 (Week 9) to understand how your team is working. What you put on your board should match what you describe in your Dev Log.
Your Dev Log should show your contribution. A commit link, session note, design file, or document update all count — use whichever fits your role. For developers, commits are the clearest record of what you built.
Design and prototyping
Section titled “Design and prototyping”How does design work count as a task?
Section titled “How does design work count as a task?”💬 “How to get a valid task from one Figma mockup?”
The task is the work that produces a design — not the design itself. Create one Kanban card per screen or user flow. In your Dev Log, describe what you made and why the layout choices match your user story.
A design is enough to run a Stage 2 Concept Testing session — show it to one person outside your team and watch what they do without explaining it. Any tool works: Pixcso, Gemdesign, Figma, or a hand-drawn sketch.
Was this page helpful?