ISYS90050 · It Project and Change Management
Development Methodologies & Communications
The Week 7 guest lecture — fully examinable — contrasts the Waterfall SDLC with iterative Agile delivery and covers communications management: who needs what information, when and how, and why communication breakdown is a recurring project risk. Expect a compare-and-contrast short answer on methodologies and a communication-channels calculation or plan question.
What this chapter covers
- 01Waterfall SDLC: sequential phases (requirements -> design -> implementation/unit test -> integration/system test -> operation/maintenance); each phase completes first
- 02Agile: iterative and incremental; deliver minimum viable value early and repeatedly
- 03Agile Manifesto values (individuals/interactions, working software, customer collaboration, responding to change)
- 04Choosing a methodology by complexity/size, constraints, client expectations, industry practice
- 05Communications management: generate, collect, distribute, store and dispose of project information
- 06PMBOK communication processes: plan, manage, monitor communications
- 07Communication channels formula: n(n - 1) / 2 for n stakeholders
- 08Methods: interactive (meetings/calls), push (email/reports), pull (intranet/repositories); breakdown as a project risk
Communication channels as a team grows
- +1Apply n(n - 1)/2 with n = 6. Channels = 6 x 5 / 2 = 30 / 2 = 15 two-way links.
- +1Apply the same formula with n = 10. Channels = 10 x 9 / 2 = 90 / 2 = 45 two-way links.
- +1Comment. Adding 4 people (a 67% increase in headcount) triples the channels from 15 to 45, because links grow with the square of team size. The implication is that communication overhead rises far faster than headcount, so a larger team needs a deliberate communications plan (roles, channels, cadence) rather than everyone talking to everyone — unmanaged, this breakdown becomes a project risk.
Key terms
- Waterfall SDLC
- A sequential development lifecycle — requirements, design, implementation and unit testing, integration and system testing, then operation and maintenance — where each phase completes before the next. Suits stable, well-understood requirements.
- Agile
- An iterative, incremental delivery approach that ships minimum viable value early and repeatedly, valuing individuals and interactions, working software, customer collaboration and responding to change (the Agile Manifesto).
- Communications management
- The processes ensuring timely and appropriate generation, collection, distribution, storage and disposal of project information — planned, managed and monitored per the PMBOK.
- Communication channels formula
- n(n - 1) / 2, where n is the number of stakeholders — the count of unique two-way communication links. It grows with the square of team size.
- Interactive / push / pull communication
- Interactive = real-time exchange (meetings, calls); push = sent to recipients (email, memos, reports); pull = accessed on demand (intranet, knowledge repositories). Match the method to the message and audience.
- Communication breakdown
- A recurring project risk in which information fails to reach the right people at the right time — a leading cause of misaligned requirements and stakeholder conflict, guarded against by a communications plan.
Development Methodologies & Communications FAQ
When is Waterfall better than Agile?
Waterfall suits projects with stable, well-understood requirements where each phase can be completed and signed off before the next — its sequential structure gives clear documentation and control. Agile suits projects where requirements are uncertain or evolving and delivering value early and adapting to change matters more than a fixed up-front plan. The choice depends on complexity, constraints, client expectations and industry practice.
Why does communication get harder as a team grows?
Because two-way communication links grow with the square of team size: n(n - 1)/2. Doubling a team roughly quadruples the channels, so overhead outpaces headcount. That is why larger projects need a deliberate communications plan — defined roles, channels and cadence — rather than relying on everyone talking to everyone.
What is the difference between push and pull communication?
Push communication is sent directly to recipients whether or not they asked for it now (email, memos, status reports); pull communication is placed where recipients retrieve it on demand (an intranet or knowledge repository). Interactive communication is real-time, two-way exchange like meetings and calls. Effective PMs match the method to the message and the audience.
Can AI help me with methodologies and communications in ISYS90050?
Yes, as a study aid. Sia can drill Waterfall-versus-Agile comparisons, work the channels formula, and help you draft a communications-plan matrix. Use it to rehearse; it does not do your graded assessment, and University of Melbourne academic-integrity rules apply — confirm details on Canvas.
Exam move
Treat the Week 7 guest lecture as fully examinable. Be able to lay out the Waterfall phases in order and contrast them point-by-point with Agile's iterative delivery and the four Manifesto values, then say when each suits a project. Memorise the channels formula n(n - 1)/2 and practise it, because the quadratic growth is a favourite short-answer point that motivates communications planning. Keep the push/pull/interactive distinction and the plan-manage-monitor processes ready, and be able to name communication breakdown as a recurring project risk. Rehearse a compact compare-and-contrast answer for the closed-book exam.
Working through Development Methodologies & Communications in ISYS90050? Sia is AskSia’s AI IT Project Management tutor — ask any ISYS90050 Development Methodologies & Communications question and get a clear, step-by-step explanation grounded in how ISYS90050 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
