FIT5120 Industry experience studio project
The Complete Study & Assessment Guide · S2 2026FIT5120 Overview
- Faculty of Information Technology
- Semester 2, 2026
- a postgraduate studio unit
- 12 credit points
- an industry-experience studio project
FIT5120 develops discovery, design thinking, iteration planning, quality assurance, governance, deployment, handover and reflective professional practice in an industry project. It is taught within Faculty of Information Technology. It is a postgraduate studio unit. It carries 12 credit points.
- Evidence precedes backlog A stakeholder statement becomes useful when the team traces it into a need, risk or acceptance condition.
- Done has layers Code completion, user acceptance, security, deployment and handover are separate readiness claims.
- Team work needs a trail Decisions, owners and contributions should be recoverable after the meeting ends.
- Studio assessment Assessment centres on the 75% project stream, individual reflection and a knowledge quiz.
How FIT5120 is assessed
| Component | Weight | Format |
|---|---|---|
| Work Integrated Project deliverables | 75% | Team-based deliverables across onboarding, iterations, go-live and handover |
| Written reflection | 15% | Individual learning-journey reflection |
| Content knowledge quiz/test | 10% | Individual assessment |
Current assessment is 75% team-based Work Integrated Project deliverables, a 15% individual reflection and a 10% individual content-knowledge quiz/test; live task pages control operation.
Current FIT5120 dates
| Date | Item | Control |
|---|---|---|
| Semester 2, 2026 | Studio delivery | Current week-by-week schedule controls deliverables and studio checkpoints. |
| Week 11 | Go-live handover package | Operational close-out evidence is scheduled here. |
| Week 12 | Expo and learning journey | Live Moodle controls presentation and submission operation. |
Current-offering dates captured in the course materials. Confirm changes and exact submission settings in the live LMS.
What FIT5120 covers
The sequence opens at Onboarding, Team Governance and Project Evidence, develops its central analytical shift in Quality Assurance and Verifiable Iterations, and closes with Handover, Expo and the Learning Journey.
Onboarding, Team Governance and Project Evidence
team charter · governance portfolio · definition of done · establish roles, evidence and escalation before delivery begins02Design Thinking and Inclusive Discovery
problem framing · stakeholder interview · inclusive design · turn stakeholder and user evidence into a testable studio problem03Product Discovery and Iteration Planning
product hypothesis · backlog · acceptance criterion · translate discovery into prioritised work with observable acceptance04Stakeholder Research, Mentoring and Proposal Quality
stakeholder analysis · mentor review · proposal · use research and mentor critique to align scope with stakeholder value05Quality Assurance and Verifiable Iterations
quality attribute · test oracle · traceability · design QA evidence around risks and acceptance rather than end-stage inspection06Effort Estimation, Capacity and Delivery Forecasts
effort estimate · team capacity · forecast · estimate iteration scope and revise it using throughput and dependency evidence07Continuous Improvement and Retrospective Action
retrospective · root cause · improvement experiment · turn retrospective evidence into one owned change and follow-up measure08Go-Live Readiness, Cybersecurity and Inclusive Operation
go-live criterion · threat model · operational accessibility · combine security, accessibility, deployment and support evidence before release09Handover, Expo and the Learning Journey
handover package · learning journey · project legacy · close the project with maintainable artefacts and individually attributable reflectionIt is positioned as an industry-experience studio project.
Three-quarters of the mark is earned through team project evidence, but individual reflection and knowledge remain separately assessed.
Assessment in fit5120 is distributed as follows: 75% team project deliverables, a 15% individual written reflection and a 10% individual content-knowledge quiz/test
The operational assessment conditions matter here.
The studio culminates in go-live, handover, expo and an individual learning-journey reflection.
What makes fit5120 demanding is concrete: showing that an attractive demonstration is backed by discovery evidence, acceptance criteria, operational readiness and attributable team decisions
The ordinary unit pass standard applies across the project, reflection and knowledge task; current Moodle instructions control operation.
For enrolment planning, Consult the current official enrolment and eligibility controls for this offering.
The sequence opens at Onboarding, Team Governance and Project Evidence, develops its central analytical shift in Quality Assurance and Verifiable Iterations, and closes with Handover, Expo and the Learning Journey.
Reject a demo-only release
- 1Separate feature demonstration from release evidence.
- 1List missing acceptance and operational controls.
- 1Assign owners and minimum exit criteria.
- 1Design a limited release or defer decision.
- 1Record evidence needed for the next checkpoint.
Key terms
- team charter
- Agreed record of roles, working norms, decision rights and escalation routes. This chapter uses the concept when students establish roles, evidence and escalation before delivery begins.
- governance portfolio
- Maintained evidence of decisions, responsibilities, risks and project controls. It helps explain the reasoning required to establish roles, evidence and escalation before delivery begins.
- definition of done
- Shared criteria that an increment must satisfy before the team treats it as complete. Its limit matters because a role list without decision rights and follow-up evidence does not govern work.
- problem framing
- Evidence-led statement of the need, affected users, context and consequence without assuming a solution. This chapter uses the concept when students turn stakeholder and user evidence into a testable studio problem.
- stakeholder interview
- Structured conversation used to learn goals, workflows, constraints and meanings from an affected person. It helps explain the reasoning required to turn stakeholder and user evidence into a testable studio problem.
- inclusive design
- Design that anticipates human diversity and removes avoidable barriers through participation and testing. Its limit matters because one sponsor voice cannot represent all users or prove a preferred solution.
- product hypothesis
- Testable belief that a change will create a defined user or stakeholder outcome. This chapter uses the concept when students translate discovery into prioritised work with observable acceptance.
- backlog
- Prioritised set of work items carrying value, evidence and delivery information. It helps explain the reasoning required to translate discovery into prioritised work with observable acceptance.
- acceptance criterion
- Observable condition used to decide whether an item satisfies its intended requirement. Its limit matters because story points and task count do not demonstrate user value.
- stakeholder analysis
- Systematic identification of affected actors, interests, influence and evidence needs. This chapter uses the concept when students use research and mentor critique to align scope with stakeholder value.
- mentor review
- Structured challenge from an industry practitioner used to expose assumptions and feasibility gaps. It helps explain the reasoning required to use research and mentor critique to align scope with stakeholder value.
- proposal
- Evidence-backed commitment describing problem, approach, scope, value, delivery and risk. Its limit matters because agreement in a presentation does not resolve hidden authority, dependency or feasibility gaps.
- quality attribute
- Observable non-functional property such as reliability, usability, security or maintainability. This chapter uses the concept when students design QA evidence around risks and acceptance rather than end-stage inspection.
FIT5120 FAQ
Where is the hardest reasoning in Industry experience studio project?
Showing that an attractive demonstration is backed by discovery evidence, acceptance criteria, operational readiness and attributable team decisions. FIT5120 develops discovery, design thinking, iteration planning, quality assurance, governance, deployment, handover and reflective professional practice in an industry project.
How does assessment work in Industry experience studio project?
75% team project deliverables, a 15% individual written reflection and a 10% individual content-knowledge quiz/test. The studio culminates in go-live, handover, expo and an individual learning-journey reflection.
What form does the final assessed task take in Industry experience studio project?
The studio culminates in go-live, handover, expo and an individual learning-journey reflection. 75% team project deliverables, a 15% individual written reflection and a 10% individual content-knowledge quiz/test.
Which pass conditions apply in Industry experience studio project?
The ordinary unit pass standard applies across the project, reflection and knowledge task; current Moodle instructions control operation. 75% team project deliverables, a 15% individual written reflection and a 10% individual content-knowledge quiz/test.
Which teaching period does this Industry experience studio project resource cover?
It is aligned to Semester 2, 2026; confirm your enrolled class and timetable in the current institutional system. Studio delivery: Semester 2, 2026; Go-live handover package: Week 11; Expo and learning journey: Week 12.
What should a student check before enrolling in Industry experience studio project?
Consult the current official enrolment and eligibility controls for this offering. This resource covers Semester 2, 2026. FIT5120 develops discovery, design thinking, iteration planning, quality assurance, governance, deployment, handover and reflective professional practice in an industry project.
Who controls the official rules for Industry experience studio project?
The university does. This is an independent fit5120 study resource; current institutional instructions remain authoritative for assessment operation. FIT5120 develops discovery, design thinking, iteration planning, quality assurance, governance, deployment, handover and reflective professional practice in an industry project.
How to prepare for the assessments
Retrieve the course map, practise the recurring method—turn stakeholder evidence into prioritised iteration work, assign accountable ownership, verify each increment against users and quality criteria, and leave an auditable handover plus individual reflection—on changed scenarios, and verify every operational assessment detail in the live institutional system.
Your AI IT Professional Practice tutor for FIT5120
Stuck on a hard FIT5120 question? Sia is AskSia’s AI IT Professional Practice tutor — ask any FIT5120 Industry experience studio project question and get a clear, step-by-step explanation grounded in how the course is actually taught and assessed. Read this whole study guide free, then take your hardest questions to Sia.
FIT5122 Professional Practice · FIT9136 Introduction to Python Programming
