Document: 32-project-lifecycle.md
Version: 1.0.0

Purpose

This document defines the standard lifecycle followed by every Rundown project.

A consistent project lifecycle ensures that all engagements progress through predictable stages, enabling clear communication, repeatable delivery, and high-quality outcomes regardless of project size or complexity.

This lifecycle serves as the operational framework for all engineering and client-facing activities.

Project Philosophy

Every project should follow a structured lifecycle.

Moving through clearly defined phases reduces uncertainty, improves planning, and establishes consistent expectations for both the engineering team and the client.

Projects should progress deliberately rather than reactively.

Lifecycle Overview

Every Rundown project follows the same high-level lifecycle.

Discovery

↓

Planning

↓

Design

↓

Development

↓

Quality Assurance

↓

Deployment

↓

Handover

↓

Maintenance

↓

Continuous Improvement

Each phase has defined objectives, deliverables, and exit criteria.

Discovery

Purpose

Understand the client's business, goals, users, and technical requirements.

Activities

• Initial consultation

• Business analysis

• Scope definition

• Technical feasibility

• Requirement gathering

Deliverables

• Discovery notes

• Initial scope

• Project proposal

Planning

Purpose

Transform requirements into an executable project plan.

Activities

• Technical architecture

• Timeline estimation

• Resource allocation

• Risk assessment

• Milestone planning

Deliverables

• Project roadmap

• Architecture decisions

• Implementation plan

Design

Purpose

Define the user experience and visual direction.

Activities

• Wireframes

• UI design

• Design system

• Client review

Deliverables

• Approved designs

• Design assets

• Component specifications

Development

Purpose

Implement the approved solution.

Activities

• Feature development

• CMS configuration

• Testing during development

• Documentation

Deliverables

• Working application

• Technical documentation

• Feature completion

Quality Assurance

Purpose

Verify that the application satisfies functional and technical requirements.

Activities

• Manual testing

• Responsive testing

• Performance review

• Accessibility verification

• Client acceptance testing

Deliverables

• QA report

• Resolved issues

• Release approval

Deployment

Purpose

Release the application into production.

Activities

• Production deployment

• Verification

• Monitoring activation

• Final validation

Deliverables

• Production release

• Deployment record

• Operational monitoring

Handover

Purpose

Transfer ownership and operational knowledge to the client.

Activities

• CMS training

• Documentation delivery

• Credential transfer

• Maintenance discussion

Deliverables

• Handover package

• Client documentation

• Training completion

Maintenance

Purpose

Maintain the reliability, security, and relevance of the application.

Activities

• Updates

• Bug fixes

• Monitoring

• Performance improvements

• Security patches

Deliverables

• Maintenance reports

• Release notes

• Support history

Continuous Improvement

Purpose

Use operational insights to improve both the application and Rundown's engineering practices.

Activities

• Performance reviews

• Incident reviews

• Process improvements

• Handbook updates

Deliverables

• Improvement backlog

• Lessons learned

• Rundown OS updates

Phase Gates

A project should not progress to the next phase until the current phase satisfies its exit criteria.

Every phase should conclude with:

• Completed deliverables

• Stakeholder approval (where applicable)

• Updated documentation

Engineering Decision

Standard Project Lifecycle

Status: Accepted

Decision

Every Rundown project follows a standardized lifecycle from discovery through continuous improvement.

Reasoning

A consistent lifecycle:

• Improves predictability.

• Reduces delivery risk.

• Simplifies communication.

• Supports operational excellence.

• Enables continuous refinement of engineering practices.

Lifecycle Checklist

Before progressing between phases, verify:

• Phase objectives achieved.

• Deliverables completed.

• Documentation updated.

• Stakeholder approvals received.

• Risks reviewed.

• Next phase prepared.

Summary

The project lifecycle provides the operational backbone for every Rundown engagement.

By following a consistent lifecycle, Rundown delivers projects through repeatable, disciplined engineering processes while creating opportunities for continuous improvement across both client work and internal operations.

Related Documents

• 27-deployment-workflow.md

• 33-client-onboarding.md

• 34-project-management.md

• 35-quality-assurance.md

• 36-client-handover.md

Related ADRs

• ADR-003: Documentation Information Architecture