Each stage must leave a useful record.
Hazina's five-stage software development process covers discovery, system design, incremental delivery, launch and responsible operation.
Before implementation
Make the real workflow visible.
Discovery is not a waiting room for development. It is where the current records, handoffs, exceptions and decision owners become an explicit model that everyone can challenge.
- 1
Defined after scoping
Frame the real problem
Map the work, the risks and the decision software must improve.
Owner: Hazina and the operational owner
Inputs
- • Current workflow
- • People and responsibilities
- • Failure points
Outputs
- • Workflow map
- • Risk register
- • Success definition
Decision gateBuild, change the scope, or do not build
- 2
Defined after scoping
Model the system
Define roles, states, domain boundaries and data responsibilities.
Owner: Hazina with domain reviewers
Inputs
- • Approved workflow map
- • Existing records
- • Policy constraints
Outputs
- • Domain model
- • Role map
- • State and record definitions
Decision gateAgree the system boundary
- 3
Defined after scoping
Prototype critical paths
Make the highest-risk flows reviewable before production implementation.
Owner: Hazina with representative users
Inputs
- • Domain model
- • Priority journeys
- • Acceptance risks
Outputs
- • Reviewable flows
- • Interaction decisions
- • Revised acceptance criteria
Decision gateApprove the critical paths
- 4
Defined after scoping
Build in reviewed slices
Deliver working increments against visible acceptance criteria.
Owner: Hazina engineering and product
Inputs
- • Approved flows
- • Prioritized backlog
- • Technical boundaries
Outputs
- • Working slices
- • Review notes
- • Updated delivery backlog
Decision gateAccept, revise, or hold each slice
- 5
Defined after scoping
Verify and secure
Test function, access, performance, accessibility and failure paths.
Owner: Hazina with accountable client reviewers
Inputs
- • Release candidate
- • Permissions model
- • Acceptance criteria
Outputs
- • Verification record
- • Resolved release blockers
- • Release decision
Decision gateReady to release or return to build
- 6
Defined after scoping
Launch and operate
Release with ownership, support boundaries and a controlled improvement backlog.
Owner: Hazina and the product owner
Inputs
- • Approved release
- • Support expectations
- • Change priorities
Outputs
- • Release plan
- • Operating backlog
- • Support boundary
Decision gateOperate, measure and prioritize the next change
Next record
Start with the workflow, not a guessed deadline.
A useful first conversation identifies the current work, the accountable reviewers and the decision the system must improve.