Skip to content

Lifecycle

PMP-003 uses a repeatable delivery lifecycle so that a new PotatoLabs product can move consistently from idea to operation.

Standard flow

  1. Idea
  2. Requirements
  3. Architecture
  4. Project Initialization
  5. Development
  6. Integration
  7. Testing
  8. Release Candidate
  9. Release
  10. Deployment
  11. Operations
  12. Maintenance or iteration

Delivery mechanics

The canonical source-code and release mechanics are:

Developer branch -> Development -> Commit -> Push -> CI validation -> Review / Merge -> Integration into target branch -> Build -> Test / validation -> Release Candidate -> Release -> Deploy

Distinctions

  • Development work implements approved requirements
  • Integration work merges source changes into the target branch or target line of work
  • Validation proves the change meets the intended criteria
  • A release candidate is a candidate for production release, not the release itself
  • Production release is the controlled promotion of a release candidate
  • Deployment places the release into a target environment
  • Operational monitoring confirms the product remains healthy after deployment

Required gate behavior

Each transition should be gated by clear evidence, review, or approval appropriate to the phase.