ISOM 472: Project in IS

Fall 2026/2027

Dr. Mohammad AlMarzouq — Week 1 · Course Launch

ISOM 472: Project in IS — Kuwait University

You will build a working system

Someone outside this room will use it.

ISOM 472: Project in IS — Kuwait University

What counts as real

A real client

Someone outside this room who wants the problem solved

A real database

Information that is still there tomorrow

A real address

Anyone can open it. No laptop demonstration on the final day.

Real use

Your client uses it before the end of the semester

ISOM 472: Project in IS — Kuwait University

It must be worth building

Business value

Someone is measurably better off: money saved, time saved, or a better decision.

A plausible next life

It could be sold to a business or adopted by a public organisation.

If nobody would pay for it and no public body would adopt it, select a different problem.

ISOM 472: Project in IS — Kuwait University

Two examples of a finished project

A bakery in Khaldiya

Orders arrive on WhatsApp and are lost in the chat.

By the end of the semester: staff enter an order, today's orders on one screen, a report of what sells and when.

A student society

Event sign-ups are collected on a paper sheet at the door.

By the end of the semester: members register, organisers see everyone, members see only themselves.

Small enough to finish. Substantial enough to matter. Distinct enough that no two teams build the same system.

ISOM 472: Project in IS — Kuwait University

The stack is decided

Plan in Gemini Enterprise

Requirements, personas, the schema, the HTML prototype.

Build in Antigravity

Code, tests, commits.

GitHub — your team's files, its history, and the record of who did what

Supabase — your database and your logins

ISOM 472: Project in IS — Kuwait University

Why the work splits that way

Gemini Enterprise lives in a browser

It cannot reach your files. Everything that crosses into your project crosses because you carried it there.

Antigravity runs on your laptop

It reads and writes your files, and it can drive GitHub and the database itself.

Antigravity can take those steps without asking you first. That is what autonomous means here — and it is why the two tools are given different work.

ISOM 472: Project in IS — Kuwait University

Which account belongs to whom

KU account

Per student. Signs you in to Gemini Enterprise and Antigravity.

GitHub account

Per student. Your own, for the whole semester.

Supabase account

Per team. One account, shared by the team.

One Supabase account per team; one GitHub account per student. This is the distinction most often confused.

ISOM 472: Project in IS — Kuwait University

What a sprint means here

  • A fixed stretch of work — in this course, two weeks
  • It ends with something that actually runs
  • You present it to the room
  • The next sprint then begins

Not a plan for later. Working software, every two weeks, six times.

ISOM 472: Project in IS — Kuwait University

Six phases, and every deadline is already fixed

Phase Delivered
1 Team, environment, and an accepted proposal the end of week 2
2 Design sprint — stories, contracts, the split the end of week 4
3 Sprint 1 the end of week 6
4 Sprint 2 the end of week 8
5 Sprint 3 the end of week 10
6 Final sprint · then demonstrations the final week of the semester

Exact dates are announced in class and on the course site.

ISOM 472: Project in IS — Kuwait University

How the marks are distributed

Phase Weight
1 Team, environment, proposal 5
2 Design sprint 10
3 Sprint 1 15
4 Sprint 2 15
5 Sprint 3 15
6 Final sprint and demonstration 40

65 group · 35 individual. No final examination.

ISOM 472: Project in IS — Kuwait University

What the individual mark draws on

Delivered work

Stories carrying your name, in the repository.

In-class checks

Pop-up quizzes. Repository activity is read and assessed.

Review

Peer review by your teammates on whether you carried your share.

Your answers in the Q&A at the final demonstration also contribute to your individual mark.

ISOM 472: Project in IS — Kuwait University

AI use is expected

You must be able to explain your own work.

ISOM 472: Project in IS — Kuwait University

The repository is the evidence

  • One repository per team, created by me. There is no individual repository
  • Every story is labelled with its owner, and the branch names it
  • Nobody merges their own work. A teammate reviews and records what was checked
  • Every pull request declares AI use: the tool, its output, your changes

Activity that is not visible in the repository did not happen.

ISOM 472: Project in IS — Kuwait University

Tokens are a real constraint

  • Every request to an AI model spends tokens, and tokens cost money
  • A team that spends them carelessly runs short before the end of the semester
  • Managing that is part of managing the project

How this is tracked, and how it is assessed, comes later in the semester.

ISOM 472: Project in IS — Kuwait University

Phase 1 — due at the end of week 2

A formed team, a verified environment, and a proposal I accept. 5 marks.

  • The full checklist, with the resubmission rules, is on the course site

Exact dates are announced in class and on the course site.

ISOM 472: Project in IS — Kuwait University

Teams — you form them, by next class

4 to 6 people per team. No more than six teams in total.

  • Settle this before next class
  • If you cannot find a team, tell me and I will place you
  • Once formed, the team fills in the team roster workbook

Six teams is the ceiling. Organise early rather than being the last group of three still looking.

ISOM 472: Project in IS — Kuwait University

How your team gets its repository

  1. Every student creates a GitHub account — your own, for the semester
  2. The team fills in the roster workbook — one row per member
  3. The Phase 1 Lead emails the workbook to me at mo.almarzouq@ku.edu.kw
  4. I create the repository and give the team access — all work happens there

Filled in and emailed before you leave next class.

Workbook: https://malmarz.github.io/isom472/forms/isom472-team-roster.xlsx

Instructions: https://malmarz.github.io/isom472/setup/

ISOM 472: Project in IS — Kuwait University

Standing roles — every team has these four

Role Owns Artifact
Client Lead The client relationship, and what the system must do The backlog of user stories with acceptance criteria
Design Lead What it looks like and how it flows The HTML prototype and the screen list
Data Lead The data and its structure The schema and seed data in Supabase
Build Lead That it actually runs The deployed system at its public address, plus release notes each sprint

A team of four holds exactly these four.

ISOM 472: Project in IS — Kuwait University

Two more roles, as the team grows

Role Owns Artifact
FinOps Lead What the AI work costs, and what the team changed as a result The Sprint FinOps Ledger
Quality Lead Finding defects in the running application Bug issues filed in the repository, tracked to a disposition

Five members

One Quality and FinOps Lead holds both responsibilities.

Six members

That role splits into a FinOps Lead and a Quality Lead.

ISOM 472: Project in IS — Kuwait University

The Phase Lead rotates

One named person per phase

Six phases. A team of six: everyone leads once. Five: one person leads twice. Four: two do.

What the Phase Lead does

Runs the phase, keeps the board current, lands the delivery on time, and is my point of contact for it.

Artifact: the phase delivery note — what was delivered, who did what, links to the stories.

Whatever your role: every member delivers stories end to end, and every member reviews teammates' pull requests — nobody approves their own.

Teams choose their own roles and their rotation, and record both on the roster workbook.

ISOM 472: Project in IS — Kuwait University

The first four weeks are taught — tentative

Session What we do
1 Week 1 · today What you build, and how it is assessed
2 Week 1 · next class Setup verified in class · teams · roles · the stack
3 Week 2 · first class Selecting a project · repository rules
4 Week 2 · second class Phase 1 delivered
5–7 Weeks 3–4 Requirements · data · cost · last lecture
8+ From the end of week 4 You deliver to the whole class, every team in the room

From week 5 the room is yours. I ask questions and score; you do the work.

ISOM 472: Project in IS — Kuwait University

Before next class

08:00, Room 1001

ISOM 472: Project in IS — Kuwait University

Install before next class

  • Antigravity — the entry named Antigravity 2.0, not the older "Antigravity IDE"
  • GitHub Desktop — installed alongside it

Every step, for Windows and for macOS, is on the course setup page: https://malmarz.github.io/isom472/setup/

Download at home. The files are large and the classroom connection is shared.

ISOM 472: Project in IS — Kuwait University

Accounts to create before next class

  • KU account — already yours. Signs you in to Gemini Enterprise and Antigravity
  • GitHub — one per student. Create yours, then give your username to your team
  • Supabase — one per team, shared. Free, works in Kuwait, no payment card
  • Your GitHub username goes on the team roster workbook — that is how I create the repository

Sign-up links and every step: https://malmarz.github.io/isom472/setup/

ISOM 472: Project in IS — Kuwait University

Bring to next class

  • Your laptop, charged, and its charger — the room is short of outlets
  • Antigravity signed in with your KU account, GitHub Desktop with your GitHub account
  • Your GitHub username, and logins reachable from that laptop
  • Some free disk space

Every installation is verified in class. If yours failed, bring the laptop — fixing it is planned, not an interruption.

ISOM 472: Project in IS — Kuwait University