Skip to content
ENT208TC Industry Readiness

ENT208TC Weekly Structure Reference

Purpose: This document maps weekly topics and activities from the official assessment brief. It serves as a reference for AI assistants to validate that guide content aligns with course requirements.

Note: Assessment percentages, rubrics, and grading details are intentionally excluded. The single source of truth for assessment is the official Assessment Brief PDF.

Module Overview

Section titled “Module Overview”

Module: ENT208TC - Industry Readiness Credits: 5 Structure: Two distinct phases

  • Phase 1 (Weeks 1-2): Universal skill-building exercise
  • Phase 2 (Weeks 3-10): Self-directed product development

Weekly Breakdown

Section titled “Weekly Breakdown”

Week 1-2: Smart Product Challenge (Foundation Phase)

Section titled “Week 1-2: Smart Product Challenge (Foundation Phase)”

Learning Focus: Hardware-software integration basics

What Students Build: Simple connected device using M5Stack StickS3

  • Examples: Smart lamp, temperature monitor, motion sensor
  • Tool: UIFlow (visual programming) + basic MicroPython
  • Hardware: M5Stack StickS3 with standard sensors

Key Activities:

  • Hands-on tutorial with IoT kit
  • Connect hardware to software (sensor → display/app)
  • Team collaboration on single device
  • Video demonstration recording

Skills Developed:

  • Understanding hardware-software connection points
  • Using visual programming tools
  • Basic sensor integration
  • Team coordination on technical task

Deliverable: 3-4 minute video demonstration showing:

  • Device functioning
  • Each team member explaining their contribution

Week 3: Project Selection & Planning

Section titled “Week 3: Project Selection & Planning”

Learning Focus: Scoping and project approval

What Students Do:

  • Select Product Studio project type from allowed options:
    • IoT/Hardware (connected devices)
    • Mobile Apps (iOS/Android)
    • Web Platforms (browser-based applications)
    • Games (interactive entertainment/educational)
    • AI/Data Products (ML-powered tools)
    • Consultancy + Prototype (strategy with working proof-of-concept)
  • Submit Project Brief for pathfinder approval
  • Begin Development Log (shared document)

Key Activities:

  • Team decision-making on project direction
  • Problem identification and user research planning
  • Technical feasibility assessment
  • Scope management (choosing achievable features)

Deliverable: Project Brief (2 pages) covering:

  • Problem statement
  • Target users
  • Proposed solution
  • Success metrics

Week 3-9: Product Studio Development

Section titled “Week 3-9: Product Studio Development”

Learning Focus: Iterative development with structured validation

What Students Do:

  • Build functional prototype of chosen product
  • Conduct user research and testing
  • Document decisions and iterations weekly
  • Engage with pathfinder for process coaching
  • Apply professional development methodologies

Key Activities:

  • Weekly Development Log entries (Weeks 3-9)
  • User interviews and testing sessions
  • Iterative prototyping based on feedback
  • Technical implementation
  • Documentation of decision-making process

Frameworks Applied:

  • Lean Startup: MVP testing, iteration cycles
  • Design Thinking: User empathy, problem definition
  • Agile Development: Sprint planning, continuous feedback
  • IP Strategy: Novelty analysis, protection decisions

Process Emphasis:

  • Did you talk to real users before building?
  • Did you iterate based on evidence?
  • Can you document decisions professionally?
  • Did you work effectively as a team?

Week 10: Demo Day

Section titled “Week 10: Demo Day”

Learning Focus: Professional presentation and stakeholder communication

What Students Do:

  • Present validated product to audience
  • Demonstrate working prototype
  • Show evidence of user validation
  • Answer technical questions
  • Complete Group Reflection in Development Log

Format:

  • 6-minute live presentation
  • 4-minute Q&A
  • Presentation slides + prototype demo

Assessment Focus:

  • Presentation quality and narrative structure
  • Prototype functionality demonstration
  • User validation evidence shown
  • Technical understanding (Q&A responses)

Week 11: Portfolio Submission

Section titled “Week 11: Portfolio Submission”

Learning Focus: Professional documentation completion

What Students Do:

  • Finalize and submit Portfolio documents
  • Complete peer evaluation process
  • Submit final Development Log with Group Reflection

Deliverables:

  1. Technical Documentation (6-9 pages):

    • System architecture
    • Technology justification
    • Deployment guide
    • IP Strategy section
    • Limitations & future work

  2. Validation Report (4-6 pages):

    • Research methodology
    • User findings (with quotes/data)
    • Iteration history (before/after)
    • Evidence appendix

  3. Group Reflection & Development Log:

    • 7 weekly entries (Weeks 3-9)
    • Group Reflection (150-250 words)
    • Evidence links throughout

  4. Peer Evaluation Form:

    • Individual contribution ratings
    • Four categories: Reliability, Quality, Initiative, Communication

Key Principles Across All Weeks

Section titled “Key Principles Across All Weeks”

Process Over Technology

Section titled “Process Over Technology”
  • Methodology and validation matter more than technical sophistication
  • Simple product with excellent validation > Complex product without user testing
  • Professional documentation is essential

Scope Management

Section titled “Scope Management”
  • Choose features you know you can deliver
  • Module leaders provide process coaching, not technical debugging
  • Project approval required before proceeding (Week 3)

Individual Accountability

Section titled “Individual Accountability”
  • Development Log documents individual contributions
  • Peer and pathfinder ratings assess engagement
  • Final grade = Team performance (70%) + Individual contribution (30%)

Support Structure

Section titled “Support Structure”
  • Pathfinders: Process coaching, feedback sessions, individual assessment
  • Module Leaders: Framework guidance, scope management, final grading
  • Team: Collaboration, peer learning, mutual support

Common Pitfalls to Avoid

Section titled “Common Pitfalls to Avoid”
  1. Overambitious Scope: Selecting technically complex projects that prevent focus on process
  2. Ignoring Users: Building without user research or validation
  3. Weak Documentation: Generic statements without evidence or links
  4. Inconsistent Engagement: Sporadic Development Log entries or missing evidence
  5. Copy-Paste AI: Using AI tools without understanding or ability to explain

Success Indicators

Section titled “Success Indicators”

Students succeed when they:

  • ✅ Complete structured user research before building
  • ✅ Document decisions with clear rationale
  • ✅ Iterate prototype based on testing feedback
  • ✅ Maintain consistent weekly Development Log entries
  • ✅ Submit professional-quality documentation
  • ✅ Demonstrate individual contributions throughout

This reference document is derived from ENT208TC Group Assessment Brief, Academic Year 2025-2026. For official assessment criteria and rubrics, refer to the Assessment Brief PDF.

Current page
🤖