Chapter 12: Validating and Managing Requirements (5%) Flashcards
steps in formal requirements validation
review group (representatives from key stakeholder groups)
collating review comments
review outcomes (3 possible outcomes:
- needs significant rework
- needs amendment
- confirmed as satisfactory)
2 stages to Agile requirements validation
- when initiating project:
outline solution confirmed, backlog established - when maintaining backlog:
work items refined until ‘ready’ for development
activities in Agile requirements validation process
- ensure individual requirements align with models developed to represent a solution
- produce initial prototypes
- develop use case or user stories
- build models to represent workflow/ specific task (e.g. swimlane, activity diagram)
- define acceptance criteria
elements in requirements management [6]
requirements identification
cross-referencing
origin + ownership
configuration management (2 key areas: config identification + config control)
change control
software support
3 possibilities for baselining prototypes during Agile software developing
baselining:
- every prototype before demo
- daily
- at end of timebox
stages of a change control process
- documenting the proposed change
- analyse proposed change
- consult stakeholders
- decide on change