INFO6007 Chap.2 Lifecycles, Methodologies and Requirements
Lifecycles, Methodologies and Requirements
The unit uses initiation, planning, execution, monitoring and controlling, and closure as lifecycle phases. Methodology choice should follow uncertainty, feedback, compliance and delivery conditions. This chapter develops Five lifecycle phases, Waterfall, Agile values and principles, Scrum, Kanban, DevOps, Requirements gathering, Project charter, Hybrid selection.
Each idea is framed as a management decision: what evidence is needed, who owns the decision, which baseline or service outcome changes, and how the result is communicated.
Stabilise what must be fixed, shorten feedback where learning has value, and trace every requirement to an objective and acceptance condition. The method is deliberately connective.
Scope choices affect dependencies and estimates; resource choices affect schedule and cost; governance choices affect escalation and benefit ownership; service choices affect operating value. A strong answer names those links rather than reproducing an isolated framework.
Agile is not absence of planning, Waterfall is not automatically wrong, and a backlog does not replace project authorisation.
The chapter uses direction checks, boundary cases and original scenarios to make those errors visible. Where a supplied figure is reproduced third-party material, the guide rebuilds it on new dimensions.
Where an answer is independently computed from a published table, it is labelled AskSia-authored rather than attributed to the University.
For assessment, start with a one-sentence definition, apply it to the stated facts, explain the consequence for objectives or constraints, and finish with the controlled action. Quantitative work must show the formula, substituted values, result, direction and management meaning.
Qualitative work must identify the decision owner and the evidence that would change the recommendation.
Study this chapter through retrieval. Rebuild the central artefact from a blank page, test it against a changed assumption, then check it against one neighbouring plan or practice.
That routine prepares for explanations, comparisons, scenarios and calculations without inventing a past-paper format or per-question mark scheme.
What this chapter covers
- 01
Five lifecycle phases
- 02
Waterfall
- 03
Agile values and principles
- 04
Scrum
- 05
Kanban
- 06
DevOps
- 07
Requirements gathering
- 08
Project charter
- 09
Hybrid selection
Free worked application: Lifecycles, Methodologies and Requirements
- FrameIdentify the objective, decision owner and evidence available at the decision point.
- MethodApply the chapter rule and keep assumptions, units and direction words explicit.
- IntegrateTrace effects into at least one connected plan, baseline, stakeholder or service outcome.
- ActState the recommendation and the change, control or communication action that follows.
- VerifyCheck the result against the chapter trap and explain why the conclusion is reproducible.
Key terms
- Five lifecycle phases
- A chapter concept used to make the relevant scope, flow, responsibility, measure or outcome explicit. Interpret it in the scenario rather than from its label alone.
- Waterfall
- A chapter concept used to connect evidence to a controlled project or service decision. Interpret it in the scenario rather than from its label alone.
- Agile values and principles
- A chapter concept used to make the relevant scope, flow, responsibility, measure or outcome explicit. Interpret it in the scenario rather than from its label alone.
- Scrum
- A chapter concept used to connect evidence to a controlled project or service decision. Interpret it in the scenario rather than from its label alone.
- Kanban
- A chapter concept used to make the relevant scope, flow, responsibility, measure or outcome explicit. Interpret it in the scenario rather than from its label alone.
- DevOps
- A chapter concept used to connect evidence to a controlled project or service decision. Interpret it in the scenario rather than from its label alone.
Lifecycles, Methodologies and Requirements FAQ
When should INFO6007 use a hybrid approach?
Use a hybrid when different parts of the same project have materially different uncertainty, compliance or feedback needs, and explain how their controls remain integrated.
What is the main decision rule for Lifecycles, Methodologies and Requirements?
Stabilise what must be fixed, shorten feedback where learning has value, and trace every requirement to an objective and acceptance condition.
What is the most common trap in Lifecycles, Methodologies and Requirements?
Agile is not absence of planning, Waterfall is not automatically wrong, and a backlog does not replace project authorisation.
How should I structure a written answer on Lifecycles, Methodologies and Requirements?
Define the concept, apply it to specific facts, explain the effect on an objective or constraint, identify the decision owner, and state the next controlled action.
Are the worked scenarios for Lifecycles, Methodologies and Requirements official answers?
No. They are AskSia-authored learning examples derived independently from the concepts and stated inputs. They are not official questions, marking schemes or university solutions.
Exam move
Begin with the chapter map: Five lifecycle phases, Waterfall, Agile values and principles, Scrum, Kanban, DevOps, Requirements gathering, Project charter, Hybrid selection. Write the purpose of each item in your own words and connect it to a decision, an artefact and an owner. Then rebuild the worked application without looking at the answer.
Use this governing rule: Stabilise what must be fixed, shorten feedback where learning has value, and trace every requirement to an objective and acceptance condition. Create two variations by changing one assumption, dependency, rating, probability, duration or stakeholder priority. Explain what changes and what remains stable. Keep an error ledger headed direction, boundary, authority, precision and integration.
The chapter's highest-risk mistake is: Agile is not absence of planning, Waterfall is not automatically wrong, and a backlog does not replace project authorisation. For quantitative work, write symbols and units before arithmetic, keep intermediate precision visible and translate the result into under/over, ahead/behind, faster/cheaper or selected/not selected as appropriate.
For qualitative work, write claim, scenario evidence, causal reasoning and controlled action. Finish by checking one neighbouring plan or practice. Review operational assessment details on Canvas; this learning chapter does not invent dates, a viva rubric, past-paper questions or a per-question university mark scheme.
Working through Lifecycles, Methodologies and Requirements in INFO6007? Sia is AskSia’s AI Project Management tutor — ask any INFO6007 Lifecycles, Methodologies and Requirements question and get a clear, step-by-step explanation grounded in how INFO6007 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
