PMI - CAPM

Stakeholder Requirements

User stories help capture these. To construct it, focus on what the need is, not how to deliver it.

solution requirements - functional

The solution’s specific behaviors from the system’s perspective

Non-functional requirements

the environmental conditions or qualities for the product to be effective.

Transition requirements

Describe how the solution will be deployed and released into production. Temporary!

Business Rules Catalog

type of rule model - a table of business rules and related attributes. You can create it and update it when you identify business rules

The definition of ready

a series of conditions that the entire team agrees to complete before a user story is considered understood and work so that the work can begin to construct

product backlog

a list of all items, typically user stories, requirements, or features, that need to be delivered for a solution. most often, written as user stories

use case

a process model that uses textual narrative to describe the system-user interactions to achieve a successful completion of a goal. frequently used to identify and elaborate requirements

R - Responsible

the person who owns the project, task, or work

A - Accountable

The person who will sign off on the work, judging its completion and how it meets quality standards

C - Consulted

People who have the ability or knowledge needed to complete the work

I - Informed

Must stay informed of the work but are not necessarily consulted

Predictive approach

there is structured sequential progression among well-defined phases.

Feasability - needs assessment

Analysis planning - requirements definition

Design - facilitate solution

Build Construct Solution - Trace and monitor requirements

Test evaluate solution - plan for deployment

Adaptive or agile approach

activities repeat