Week 3: Resources & Links

Product Development Vocabulary

The Product Studio (Weeks 3–10) uses professional product management language. Learn the terms before you need them — it makes pathfinder feedback and assessment criteria much easier to follow.

Glossary	What’s in it
Product Development Glossary	Agile, MVP, sprint, Kanban, MoSCoW, user story, Dev Log, validation — all terms used in ENT208TC
Tech Glossary	Hardware, sensors, connectivity terms (mainly Weeks 1–2)

How to use the glossary

When your pathfinder uses a term you don’t recognise — look it up in the glossary first. Each entry has a short AI prompt you can use to go deeper.

---

Design Thinking

Your Week 3 session uses Design Thinking — a method for solving real problems that starts with the person, not the product. It was developed by IDEO and Stanford d.school and is used across consulting, tech, and entrepreneurship.

Read first (2 min)

Future Ready: A Foresight Playbook for Innovators — Bogdan Marculescu. Chapter 1 introduces Signals — the method behind Mission 1, Step A. A short excerpt (2 case studies) is available as a PDF on this site: /FutureReady-2CaseStudies.pdf

Watch (~5 min)

Platform	What to search
YouTube	IDEO Design Thinking — the 5-minute explainer is widely used
Bilibili	设计思维 Stanford or 设计思维 IDEO for Chinese-language introductions

The five stages (you use the first three in Week 3)

Stage	What you do	When
Empathise	Understand a real person’s situation	Mission 1
Define	Write one clear problem statement	Mission 2
Ideate	Generate solution ideas, vote on one	Mission 2
Prototype	Build a working version	Weeks 4–6
Test	Try it with real users and iterate	Weeks 5–8

---

Tools You Will Use in Week 3

Tool	What for	Link
XJTLU SharePoint	Create and host your Development Log	xjtlums-my.sharepoint.com
GitHub	Version control and team collaboration	github.com
LMO	Submit Project Brief via Turnitin	Log in through your XJTLU portal

New to GitHub?

Ask any AI: “Explain GitHub to someone who has never used version control. What are the 3 most important things a new team needs to know to start collaborating on a project?”

---

Assessment Criteria

Product Studio is 90% of your module grade. Understanding what is assessed before you choose a project is time well spent.

Component	Weight	What it assesses
Demo Day (Week 10)	40%	Working product + user validation evidence + presentation
Development Log (Weeks 3–9)	20%	Weekly progress, individual contributions, evidence links
Portfolio (Week 11)	30%	Technical Documentation + Validation Report + Project Brief
Individual contribution	multiplier	Peer score + pathfinder score (can raise your grade above the team’s)

Full assessment criteria and rubrics →

---

Project Inspiration

Not sure what to build? Two sources of validated project ideas:

Syntegrative Project list on LMO — challenges from industry partners and university stakeholders. These are real problems with real users already identified. The same list from ENT207TC.

Your own experience — the best projects in previous cohorts came from a team member describing a daily frustration to the group. Start with Mission 1 before looking at lists.

---

Frameworks You Will Apply This Semester

From the assessment brief — these are the five frameworks ENT208TC explicitly teaches:

Framework	Created by	Where it appears in your work
Design Thinking	IDEO / Stanford d.school	Project Brief (problem definition), Validation Report
Lean Startup	Eric Ries	Development Log (iteration cycles), Validation Report
Agile Development	Software industry	Development Log (weekly sprints), pathfinder checkpoints
IP Strategy	Business / patent law	Technical Documentation (IP Strategy section)
Hardware-Software Integration	IoT / embedded systems	Weeks 1–2 foundation, Technical Documentation

You do not need to memorise these. You will encounter each one when you need it. This table shows why the module is designed the way it is.