CivilCode Playbook
  • The CivilCode Playbook
  • Method
    • Engagement
      • Qualification
      • Introductory Meeting
    • Onboarding
      • Roles and responsibilities
      • Product Owner Role
    • Discovery
    • Iteration Zero
      • Kickoff
    • Development
      • Develop an Object Model
      • Build a Feature List
  • Guides
    • Operations
      • Setup the VPN
      • Developer Setup Guide
      • Maintain Virtual Machine
    • Practices
      • Pair Programming Practice
      • Friday Practice
      • Project Retrospective
      • Daily Practices
  • Education
    • Trails
      • Elixir
      • Domain-Driven Design and CQRS/ES
      • Event Storming
      • Feature-Driven Development
      • Functional Programming
      • GraphQL
      • Object Design
      • Object Modeling
      • Specification by Example
      • Story Mapping
      • Testing
      • Type Classes
Powered by GitBook
On this page
  • Stages
  • Practices
  • Templates

Method

PreviousThe CivilCode PlaybookNextEngagement

Last updated 5 years ago

The CivilCode Method is a description of our way-of-working. The method is a set of practices and tools used by our team to guide and support our work. "A practice is a repeatable approach to doing something with a specific objective in mind."

The terminology used to describe our method is based on the from the SEMAT (Software Engineering Method and Theory) initiative.

Stages

Practices

The key practices we use (linked to education trails):

  • (Business-driven Discovery)

  • (User-driven Discovery)

Templates

.

All quotes from

Essence Kernel and Language
Engagement
Onboarding
Discovery
Iteration Zero
Development
Domain-Driven Design
Event Storming
Feature-Driven Development
Object Modeling
Pair Programming
Specification by Example
Story Mapping
Testing
Tracking Tool
http://semat.org/documents/20181/57862/formal-18-10-02.pdf/866c80c0-cdc8-488b-bcf8-0c67cb60b5d7