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
  • Discovery Session
  • Before
  • On the day
  • Development Plan Document
  • Contents
  • Other considerations
  • How we estimate
  1. Method

Discovery

A week long process to scope a project before developing a plan and recommending a budget.

Effort: 1-2 developer blocks (it's probably more than this but we want to keep it affordable).

  • Gather and review any related documents and review

    • manuals

    • forms

    • existing apps

  • Prepare discovery session

  • Conduct discovery session

  • Review discovery session

  • Develop plan and estimate budget

Discovery Session

Scheduled across two half-days, ideally Tuesday morning and a Wednesday morning. This allows the Monday for preparation.

Before

On the day

Development Plan Document

Contents

Other considerations

How we estimate

Abilities are identified as commands, queries and reports. Due to the complex nature of reports, these abilities also have the tasks identified to help with the estimation process.

There are also some additional overheads in developing an application which is represented as a percentage of the entire project, e.g. project management.

PreviousProduct Owner RoleNextIteration Zero

Last updated 4 years ago

An estimate of the required budget is made based on the . The feature list is divided in modules and abilities. The tasks for abilities are not identified in the discovery due to time constraints. Tasks are identified in the discovery of a module during the project.

Each ability is estimated in "ideal days" based on a comparison made against the archetype abilities. An archetype ability is a simple ability. The comparison involves two developers playing to determine if an ability is the same; one, two or more times complex than the archetype.

See .

Feature List
planning poker
the template for more details