Document: 07-development-workflow.md
Version: 1.0.0

Purpose

This document defines the standard development workflow followed by Rundown for all web development projects.

A consistent workflow ensures that projects progress through the same stages, reduces miscommunication, improves quality, and provides predictable outcomes for both the engineering team and clients.

This workflow applies to all project types unless otherwise specified.

Project Lifecycle

Every project should progress through the following stages:

Discovery
    ↓
Planning
    ↓
Design
    ↓
Development
    ↓
Quality Assurance
    ↓
Client Review
    ↓
Deployment
    ↓
Post Launch Support
    ↓
Maintenance

Each stage should be completed before progressing to the next.

Stage 1 — Discovery

Objective

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

Deliverables

• Project Brief

• Feature List

• Business Goals

• Technical Requirements

• Project Type Classification

No development should begin before the discovery phase is complete.

Stage 2 — Planning

Objective

Define the technical approach.

Activities

• Select project architecture.

• Define CMS requirements.

• Plan database structure.

• Identify third-party integrations.

• Create project milestones.

• Estimate development effort.

Deliverables

• Technical Plan

• Timeline

• Feature Scope

Stage 3 — Design

Objective

Create the user interface and user experience.

Activities

• Wireframes

• High-fidelity UI Design

• Responsive Design

• Design Review

• Client Approval

Engineering should begin only after design approval unless otherwise agreed.

Stage 4 — Development

Objective

Implement the approved design.

Activities

• Create feature branches.

• Build reusable components.

• Implement CMS.

• Configure database.

• Integrate APIs.

• Optimize performance.

• Test continuously during development.

Developers should commit small, focused changes throughout the project.

Stage 5 — Quality Assurance

Objective

Verify that the application functions correctly.

Verification

• Responsive layouts

• Forms

• CMS

• Navigation

• Performance

• Accessibility

• Browser compatibility

• SEO

• Error handling

Critical issues must be resolved before client review.

Stage 6 — Client Review

Objective

Allow the client to review the completed work.

Activities

• Demonstrate completed functionality.

• Collect feedback.

• Record requested revisions.

• Confirm feature completion.

Only agreed project scope should be revised during this stage.

Stage 7 — Deployment

Objective

Release the application to production.

Checklist

• Production build successful

• Environment variables configured

• Domain connected

• SSL enabled

• Analytics configured

• Backups verified

• Monitoring enabled

Deployment should follow the standards defined in the Infrastructure section of Rundown OS.

Stage 8 — Post Launch Support

Objective

Ensure a stable launch.

Typical activities include:

• Bug fixes

• Performance monitoring

• Error resolution

• Client assistance

This period focuses on stabilizing the production environment.

Stage 9 — Maintenance

Objective

Provide ongoing improvements and operational support.

Typical activities include:

• Dependency updates

• Security updates

• Content support

• Performance improvements

• Feature enhancements

• Backup verification

Maintenance requirements should be defined in the client agreement.

Development Rules

Every project should follow these principles:

• Build reusable components whenever practical.

• Avoid unnecessary dependencies.

• Commit frequently.

• Test continuously.

• Keep documentation up to date.

• Follow Rundown coding standards.

• Raise technical concerns early.

Project Completion Criteria

A project is considered complete when:

• All agreed features have been delivered.

• Client approval has been received.

• Production deployment is complete.

• Documentation has been updated.

• Repository is organized.

• Backups are configured.

• Monitoring is active.

Best Practices

• Complete one stage before beginning the next.

• Keep communication transparent.

• Record important technical decisions.

• Avoid scope changes during development whenever possible.

• Prioritize maintainability over short-term speed.

Summary

Following a consistent development workflow ensures every Rundown project progresses through a structured, repeatable process.

The objective is to reduce uncertainty, improve quality, and provide a predictable experience for both the engineering team and clients.

Related Documents

• README.md

• 01-engineering-philosophy.md

• 02-tech-stack.md

• 03-project-types.md

• 04-development-environment.md

• 05-project-structure.md

• 06-git-workflow.md

Related ADRs

• ADR-001: Repository Structure

• ADR-002: Git Workflow