1/53
Requirements, Quality, Change, Risk, Issue
Functional vs non-functional requirement?
Functional says what the system does; non-functional says how well it performs or constrains it.
What is the requirements process?
Gather, Analyse, Justify, Baseline. Memory: Grumpy Aunties Judge Babies.
What happens in Gather?
Identify stakeholder needs using interviews, workshops and other techniques.
What happens in Analyse (requirement process)?
Check completeness, feasibility, conflicts and dependencies.
What happens in Justify (requirement process)?
Test value and necessity, prioritise and agree trade-offs.
What happens in Baseline (requirement process)?
Formally agree and record requirements as a controlled reference.
What does MoSCoW mean?
Must Have, Should Have, Could Have, Won't Have this time.
Why baseline requirements?
To check acceptance and manage later changes against an agreed reference.
What is the quality-management memory sequence?
Plan, Control, Assure, Improve. Memory: Penguins Can't Act Innocent.
What is quality planning?
Define standards, metrics, responsibilities, methods and acceptance criteria.
What is quality control?
Inspect and test outputs against quality requirements.
What is quality assurance?
Check that processes for achieving quality are suitable and followed.
Quality assurance vs quality control?
QA examines processes; QC examines outputs.
What is continuous improvement?
Use findings and lessons to prevent recurring defects and improve processes.
What is a fishbone diagram for?
Organising possible root causes of a defect; ask WHY it happened.
What is a Pareto chart for?
Prioritising the defect categories contributing most to a problem.
What is a check sheet for?
Recording frequency or occurrences of defects.
What is a histogram for?
Showing frequency distribution of measured values.
What is a scatter diagram for?
Exploring a possible relationship between two variables.
What to do when a component fails testing?
Isolate it, investigate causes, correct or replace, retest and record findings.
What is the change-control sequence?
Record, Evaluate, Recommend, Authorise, Update, Implement. Memory: Rude Elephants Really Appreciate Ugly Iguanas.
What is the first step for a change request?
Record its description, requester and justification in the change log.
What is evaluated before approval?
Impact on scope, schedule, costs, quality, benefits, resources and risk.
Who authorises a major change?
Sponsor or designated change authority when beyond PM delegation.
What happens after approval?
Update baselines and plans, implement, verify and record the change.
Linear vs iterative change?
Linear controls changes to established baseline; iterative reprioritises backlog with appropriate governance.
What is scope creep?
Uncontrolled expansion of scope without appropriate assessment or approval.
What is configuration management?
Identification, control and tracking of approved product components and versions.
What is the configuration process?
Plan, Identify, Control, Status accounting, Verify. Memory: Purple Iguanas Can't Stop Vomiting.
What is configuration identification?
Define items and unique identifiers, versions and relationships.
What is configuration control?
Authorise and control changes to configuration items.
What is configuration status accounting?
Record and report current versions, states and change histories.
What is configuration verification/audit?
Check actual items match approved records and specifications.
Change control vs configuration management?
Change control decides whether a change is authorised; configuration tracks affected items and versions.
Risk vs issue?
Risk is uncertain future event; issue is a current problem requiring action.
What is the risk-management process?
Initiate, Identify, Assess, Respond, Monitor, Close. Memory: Icy Iguanas Always Ride Motorcycles Carefully.
What are the three common risk assessment dimensions?
Probability, impact and proximity.
What is risk proximity?
How soon a risk might materialise.
What is a risk register?
Record of risks, owners, assessments, responses and status.
What are threat responses?
Avoid, Reduce, Transfer, Accept. Memory: Angry Rhinos Throw Apples.
What does Avoid mean (threat response)?
Eliminate the threat, e.g. remove the risky activity.
What does Reduce mean (threat response)?
Lower probability or impact, e.g. add testing or contingency arrangements.
What does Transfer mean (threat response)?
Shift some consequences to another party, e.g. insurance; risk may remain.
What does Accept mean (threat response)?
Consciously tolerate the risk, monitor and prepare contingency if needed.
What are opportunity responses?
Exploit, Enhance, Share, Reject. Memory: Excited Elephants Share Rewards.
What does Exploit mean (oppertunity response)?
Take action to ensure the opportunity is realised.
What does Enhance mean (oppertunity response)?
Increase the probability or scale of the opportunity.
What does Share mean (oppertunity response)?
Partner with another party to realise the opportunity and share benefits.
What does Reject mean (oppertunity response)?
Decide not to pursue the opportunity.
What is the issue-management sequence?
Log, assess, identify options, agree action/escalate, implement, monitor and close.
When escalate an issue?
If it breaches PM authority/tolerances or threatens viability or key objectives.
How respond to a supplier delivery already missed?
Record an issue, assess impact, agree recovery, escalate if needed and monitor.
How respond to possible specialist departure?
Reduce risk via cross-training, knowledge transfer and succession planning.
How respond to a cost-saving technology opportunity?
Assess feasibility, then exploit or enhance it where justified.