Activities: Role-Performed Units of Work
An activity is a well-defined unit of work carried out by a specific role. Activities are the building blocks of daily work, transforming input artifacts (like user requirements) into output artifacts (like verified code and test reports). Every activity has clear entry criteria, step-by-step guidance, and exit verification gates, ensuring work is repeatable, measurable, and auditable.
The Anatomy of a Regulated Activity
In NUP, an activity is not an informal calendar meeting or a generic to-do item. It is a formalized, role-performed process step that transforms defined inputs into verified outputs. Every activity consists of four essential components:
1. Responsible Role
A qualified individual or team (e.g. Solutions Architect, QA Engineer) accountable for performing the work.
2. Input Artifacts
The prerequisite baseline documents, user stories, or design specifications required before work starts.
3. Structured Steps
A repeatable, documented procedure following verified engineering or compliance recipes.
4. Output & Verification
Newly produced or updated version-controlled artifacts, validated against formal quality gates.
Activity Breakdown Structure (ABS)
Activities decompose high-level engineering disciplines into granular, assignable work units. For example, within the Software Design & Architecture discipline, activities break down as follows:
Generate a step-by-step activity breakdown for regulated pull request reviews.
Community Discussion & Feedback
Attributed peer feedback and official Netspective architecture notes.