Select a result to preview

Project Management

Document: 34-project-management.md
Version: 1.0.0

Purpose

This document defines the project management standards used across all Rundown projects.

Project management provides the operational structure required to plan, execute, monitor, and deliver projects consistently. Standardized project management improves visibility, communication, accountability, and delivery quality across the organization.

Project Management Philosophy

Projects should be managed through systems rather than memory.

Every project should provide a clear, real-time understanding of:

Operational visibility should exist independently of any individual team member.

Standard Project Management Platform

Rundown standardizes on:

ClickUp

All engineering, design, and operational work should be managed within the project management platform.

Project status should never rely on informal communication channels.

Responsibilities

Project management owns:

Non-Responsibilities

Project management should not own:

Project management coordinates work; it does not replace engineering systems.

Standard Project Structure

Every project should contain the following sections:

Project Information

↓

Backlog

↓

Sprint / Current Work

↓

In Review

↓

Ready for QA

↓

Completed

↓

Blocked

Projects may add additional sections where justified, but the core workflow should remain consistent.

Task Management

Every task should include:

Tasks should represent discrete units of work that can be completed independently.

Milestones

Major project phases should be represented as milestones.

Typical milestones include:

Milestones provide visibility into overall project progress.

Prioritization

Work should be prioritized based on:

  1. Business value

  2. Dependencies

  3. Delivery risk

  4. Client commitments

Priority should not be determined solely by request order.

Documentation

Every project should link to:

Project information should remain centralized.

Risk Management

Project risks should be documented and reviewed regularly.

Typical risks include:

Early identification enables proactive mitigation.

Change Requests

Requests outside the approved scope should follow a documented change request process.

Every change request should include:

Scope changes should never be implemented informally.

Meetings

Meetings should have:

Meetings should create progress rather than replace it.

Reporting

Project reporting should summarize:

Reports should communicate progress rather than activity.

Engineering Decision

System-Driven Project Management

Status: Accepted

Decision

All Rundown projects are managed through a centralized project management platform using standardized workflows.

Reasoning

A consistent project management system:

Project Management Checklist

Before beginning active development, verify:

Summary

Project management provides the operational framework that enables Rundown to deliver projects consistently and predictably.

By managing work through standardized systems rather than individual knowledge, Rundown improves collaboration, accountability, and delivery quality across every engagement.