← Module 4: Software Engineering Project

NSWSoftware EngineeringSyllabus dot point

Inquiry Question 1: How are large-scale software solutions developed and managed?

Use project management tools to plan, track and communicate work across a software team, including issue trackers, Kanban boards and Gantt charts

A focused answer to the HSC Software Engineering Module 4 dot point on project management tools. Issue trackers (GitHub Issues, Jira), Kanban boards, Gantt charts, the worked example, and the traps markers look for.

Generated by Claude OpusReviewed by Better Tuition Academy4 min answerUpdated 2026-05-20

Have a quick question? Jump to the Q&A page

What this dot point is asking

NESA wants you to identify the standard project management tools used in software teams and describe what each is for. You should know issue trackers, Kanban boards and Gantt charts at minimum.

The answer

Issue trackers

The central list of work. Each issue captures one task, bug, or piece of work. Common fields:

Title: a short summary.
Description: details, acceptance criteria, links to specifications.
Assignee: who is doing it.
Labels or tags: categorisation (bug, feature, security, documentation).
Priority: how urgent.
Milestone or release: when it ships.
Discussion thread: comments from team members.
Status: open, in progress, in review, closed.

Examples: GitHub Issues, GitLab Issues, Jira, Linear, Asana.

Issues form the source of truth for "what needs doing". They link to commits, pull requests, design documents and customer reports.

Kanban boards

A visual board with columns (typically: Backlog, To do, In progress, In review, Done). Each card on the board is an issue. The board shows the workflow at a glance:

Backlog (12)  | To do (3)     | In progress (2) | In review (1) | Done (8)
--------------|---------------|-----------------|---------------|---------
login form    | search bar    | password reset  | dashboard     | signup form
forgot-pass   | dark mode     | profile page    |               | nav menu
delete-account|               |                 |               | logout
              |               |                 |               | ...

Benefits:

Everyone sees what is happening.
Bottlenecks (a pile-up in "In review") are visible.
Work-in-progress (WIP) limits prevent overload (no more than 3 items in "In progress" per person).

Most issue trackers (GitHub Projects, Jira, Trello) include a Kanban view.

Gantt charts

A chart with tasks as rows, time on the horizontal axis, bars showing duration. Dependencies between tasks are drawn as arrows.

Task        | Week 1 | Week 2 | Week 3 | Week 4
Requirements  ####
Design              ####
Build                        ##########
Test                                ####
Deploy                                  ##

Useful for:

Time-based planning (when does each task happen).
Dependency tracking (Task B cannot start until Task A finishes).
Communicating schedules to non-technical stakeholders.
Identifying the critical path - the longest chain of dependent tasks that determines the earliest possible end date.

Tools: Microsoft Project, GanttPRO, ProjectLibre, even spreadsheets.

When to use each

Question	Tool
What is left to do?	Issue tracker
What is happening right now?	Kanban board
When will the project finish?	Gantt chart
Who is working on what?	Issue tracker (assignee)
Where is the bottleneck?	Kanban board
What is the critical path?	Gantt chart

Combining the tools

A typical small team setup:

GitHub Issues as the issue tracker. Every bug, feature and task is an issue.
GitHub Projects as the Kanban board. Issues are automatically added as cards and move through columns as PRs open and close.
A Gantt chart in spreadsheet form, updated weekly, for the project plan reported to the teacher or stakeholder.

A larger team setup:

Jira for issues with custom workflows.
Confluence for documentation linked from Jira tickets.
Slack or Microsoft Teams for real-time communication.
Microsoft Project for the high-level Gantt chart.

Other tools

Wiki / documentation: Confluence, Notion, GitHub wiki. The team's institutional memory.
Communication: Slack, Teams, Discord. Synchronous chat.
Roadmap: a higher-level plan than a sprint backlog, typically quarterly.
Burn-down chart: progress through a sprint, showing remaining work over time.
Velocity chart: how much work the team completes per sprint, used for forecasting.

Worked: a four-person team

A four-person Software Engineering Project group:

GitHub Issues: every task captured. Issues labelled by module (backend, frontend, database, ML).
GitHub Projects board: To do, In progress, In review, Done columns. Each member moves their own cards.
A Gantt chart in Google Sheets, owned by the project leader, updated weekly. Shows the seven major milestones (planning, design, build, test, deploy, demo, write-up) and inter-task dependencies.
Daily 10-minute stand-up to talk through any blockers visible on the board.
A shared Google Doc for design notes, decisions and meeting minutes.

The teacher reviews the Gantt chart in fortnightly check-ins. The team uses the board day to day.

Worked example

A team of three Year 12 students is six weeks from their Major Project submission. They are running over schedule. List four ways the project management tools they use can help them recover.

Issue tracker: re-prioritise the backlog. Move "nice to have" features to a "next release" milestone. Focus on the core acceptance criteria.
Kanban board: enforce a strict WIP limit (one item in progress per person). Cards piling up in "In review" signal that reviews are the bottleneck; pair on reviews to clear them.
Gantt chart: shorten or remove the non-critical-path tasks. Identify the critical path and pour effort there. Move parallel work to free hands.
Stand-up minutes / shared doc: surface blockers daily. If one team member is stuck, surface it on day 1, not day 4. Reallocate responsibilities so no one is the sole owner of a critical task.

Past exam questions, worked

Real questions from past NESA papers on this dot point, with our answer explainer.

2025 HSC4 marksDescribe the role of an issue tracker, a Kanban board and a Gantt chart in managing a software project. Identify which tool you would use to communicate progress to a non-technical stakeholder.

Show worked answer →

An issue tracker (GitHub Issues, Jira, Linear) is the central list of all work items. Each issue captures one task or bug, with a title, description, assignee, labels, priority, and discussion thread. It is the canonical source of "what needs doing".

A Kanban board is a visual representation of the issues moving through states (To do, In progress, In review, Done). It shows the team's workflow at a glance, exposes bottlenecks, and enforces work-in-progress limits. Built into GitHub Projects, Jira and Trello.

A Gantt chart plots tasks against time, showing start dates, end dates, durations and dependencies. Best for projects with fixed deadlines and inter-task dependencies. Used in waterfall and hybrid projects to visualise the schedule.

For a non-technical stakeholder (a school principal, a client, a parent), the Gantt chart is usually the right tool. It answers their questions: when does the project finish? what is happening this month? what is at risk? The issue tracker is too detailed; the Kanban board lacks the time dimension.

Markers reward correct definitions of all three tools, the role each plays, and a defensible recommendation with reasoning (Gantt for time-based stakeholder reporting is the standard answer).