Software Development: Managing a Team Software Project: Unit Review

Iterative (agile): working versions are delivered every sprint, so she can try them and change her mind; waterfall fixes requirements at the start.

For each task or deliverable, who is responsible for it, so that every task has exactly one owner. (Larger teams often also record who approves it and who must be consulted or informed.)

Any three: the project goal, each member's role, meeting times, how the team communicates, how decisions are made, what happens when a deadline is missed, how work will be assessed.

Non-functional (performance): it describes how well the system works, not what it does.

Example: "As a front-desk volunteer, I want to mark an item as returned so that the next member can borrow it."

Scope creep is requirements growing without control during the project. The signed scope document (with change control) protects against it: anything not in it needs a change request.

E = (2 + 4 × 4 + 12) ÷ 6 = 30 ÷ 6 = 5 h; σ = (12 − 2) ÷ 6 ≈ 1.7 h.

They do 4 hours a day together, so 12 ÷ 4 = 3 days. Effort is work hours; duration is calendar time.

Examples: keep all work in the shared repository daily, pair people so two know each module, keep a schedule buffer.

A: 0 to 3; B: 3 to 5; C: 3 to 8; D starts at the later of 5 and 8, so 8 to 9. Length 9 days; critical path A-C-D.

Backward pass: D's latest start is 8, so B's latest finish is 8 and latest start 6. Slack = 6 − 3 = 3 days.

It caps how many tasks can be in progress at once, so the team finishes work before starting more.

It links each requirement to the design, code and tests that cover it, so no requirement is missed and every test has a reason.

The function's name, its two parameters (both dates) and that it returns a float (the fee in dollars), without needing to read the body.

Team members can then build and test their modules in parallel, and the modules fit together when integrated.

git add (stage the file) and then git commit -m "message".

git restore throws away uncommitted changes to a file; git revert makes a new commit that undoes an earlier commit, keeping history intact.

To stop Git tracking files that should not be shared, such as __pycache__ folders, personal settings or data files with private information.

When main has no new commits since the branch was made, so Git just moves main forward to the branch's last commit.

Open the file, find the lines between <<<<<<<, ======= and >>>>>>>, decide (with your teammate) what the correct code is, delete the markers, run the tests, then git add and git commit.

A teammate reviews the change (and tests run) before it reaches main, which catches bugs and spreads knowledge of the code.

6 days late × $0.25 = $1.50: self.assertAlmostEqual(late_fee(date(2026, 11, 20), date(2026, 11, 26)), 1.50).

The boundary: 2 items out (may borrow), 3 out (may not), and 0 as a normal case.

Red (write a failing test), green (write just enough code to pass), refactor (tidy the code, tests still passing).

A stub stands in for a module that is called but not yet written; a driver is test code that calls a module that has no caller yet.

That is regression testing: it catches changes that break something that used to work.

The client (or users), against the acceptance criteria in the scope document.

SPI = 30 ÷ 40 = 0.75 (behind schedule); CPI = 30 ÷ 50 = 0.6 (each hour of work earns only 0.6 h of planned value: over budget).

More work remains than planned: the team is behind.

Log it, estimate its impact (hours, schedule, risk), let the client decide (accept, defer or reject), and if accepted update the baseline and plan.

Important, not urgent: schedule it into a project block now, before it becomes urgent.

5 × 1.4 = 7 hours.

Treat it as a blocker: say so at the next stand-up (or message the team) and ask for help early, instead of losing days on it alone.

(a) 1.0.1 (patch); (b) 1.1.0 (minor).

The user guide is for the people who use the program (staff); the README is mainly for people who install, run or develop it.

The few most common tasks in short numbered steps, the keys or menu choices for them, and where to get help, on one page.

(a) corrective; (b) perfective; (c) adaptive.

The client formally accepts that the deliverables meet the agreed requirements, so the project can close.

Who gives support, how to contact them, how fast they respond, and how long support lasts (also: how fixes are released).

Fri, Mon, Tue, Wed, Thu: +5 working days.

(75 − 60) ÷ 60 = +25%.

Example: "Testing started only after all the code was finished, so it piled up at the end. Next time, test each module as soon as it is merged."