Breadth & depth of information provided

Needs of stkhldrs

Reuse:

repository accessible to other BAs

Attributes to describe requirements

Giv

Item trakcing / problem tracking

Record

Escalation matrix

Metrics

number of items, Cycle time

Approver / Reviewer

Rigour: high, medium and low

Criteria: cost

Predictive-formal approvals

Adaptive-approval of iteration

Governance-decision making

Organisational mdlin'

Functionally-oriented

Market-oriented

Matrix Mdl: China reporting to china regional ldr as well as global head.

Identify informal lines of authority, clout, and communication

stkhldr list, map / personas

onion diagram

Core:

affected organisational: help desk

affected external:

Power-interest grid

RACI matrix Accountable (Only One)

Personas

fictional

change strategy-stkhldr related initiative strategy

stkhldr Level of clout

Thorough stkhldr analysis-not once for all

Regulator-organisational rules

Sponsor-approval

Plan-output (specific backlog)

Approach

Top-down:

based on former experience

Bottom-up:

Elaboration, more accuracy

More information needed

Parametric:

Use case

ROM:

Rough, +-50% accuracy

Rolling Wave:

Delphi:

Mutiple elicitation and rounds to reach concensus, not really via a vis-a-vis meeting

PERT:

3 points estimation (O+P+ML)/3

(O+P+4ML)/6

SOI

Analogous situation

Archive

Usage consideration:

rationale

Lessons learned

Retro fixed term

Event-driven

variances can be positive or negative > Root cause analysis

Usage consideration:

Trying to assign blame X

Assessment-successive improvement

Deliverable / Work product

Domain knowledge

Allocated time

Approach reviewed and agreed upon by key stkhldrs

Predictive:

step by step

formal change application

defined ahead of implementation

risk low

Formal documentation

Adaptive:

risk high

iterations

User stories

Informal

I. Predictive approaches

Pro:

mitigate uncertainty

Con:

Time-consuming

Rendering of value, not necessarily

II. Adaptive approaches

Pro:

iterative deliverance

The waterfall model: typically predictive

The spiral model: iterative develop

The unified process

Elaboration-bringing more details

Scrum-Agile

Artifact

Sprint (Duration: 1-4 weeks)

Backlog

Product increment

Sprint review & retrospective

The Agile Manifesto

Documentation

Responding to change

Verifiy-quality check

Validate-assurance of value, affirmation of sme, scope

Input requirements / designs

Tester-QC

Stakeholder identification

笔记123 

Requirement Life cycle Management (Pg 42)

           All about requirements/design

• 5.1 input Trace Requirement

Output  Traced Requirement, Link to 7.5 Define Design Output.

• 5.2 Input Maintain Requirement 

Output  Maintained Requirements/ Design

• 5.3 Prioritize Requirements

Output Prioritised Requirements/ Design, Link to 6.3 Assess Risks

• 5.4 Assess Requirements Change, Might also involve proposed change

Output Assessment of Requirements and Design Change

• 5.5 Approve Requirement

​​​​​​​Output Approved Requirements/ Designs