Skip to content

Code the Dream Agile Process

Jump to bottom
Tom Rau edited this page Aug 14, 2020 · 11 revisions

CtD Agile Process

Project Board

Team:

  • Rod (Product Owner/PM)
  • Tom (co-product owner)
  • Brian (TypeScript)
  • Tony (Rail)

Sprints:

1 Week Cadence: Monday 5pm end of previous sprint. Tuesday after Planning is beginning of new sprint.

Ceremonies:

  • Standup - 10am M, W, Th, Friday
  • Backlog Pre-refinement - 10:15am (as needed)
  • Backlog Refinement - Monday 11:00am-12pm
  • Sprint Planning - Tuesday 10:45am - 11:15am
  • Sprint Review - Monday 4:45pm
  • Retros - Tuesday Morning. 10am-10:45

PR Process

Generally speaking PRs should be made for each ticket and be linked to issue and mention in the name.

Communication

CtD Slack Channel is primarily for communication with product owners/PM. Will schedule slack calls with devs as needed for clarification, etc and discussions on tickets but final ticket requirements and implementation should always live on the github ticket

Epics

Epics are special tickets that have their own column and their own column for done. They can consist of groups of tasks, stories, and spikes, and will reference groups of tickets within them by #. They describe larger functionality. "As a user i want to have a favorites list." This would/cound consist of multiple tickets: "#111 as a user i want to add a study to my favorites list from a study page so that i can view my favorites later. #112 as a user i want to be able to view and edit my favorites list via my profie page., etc"

How we write tickets

types of tickets

*stories - User focused. "as a user i need this so i can do this." *tasks - Non-user focused. Usually more backend focused. "add a row to the database, change schema, create reusable component. Add X to nesting" *bugs - this feature is broken and needs to be fixed (Screenshots and how to reproduce if possible) *spike - developer needs x amount of time to decide best way to do X.

Tickets consist of

  • Type
  • Story Points
  • Description
  • Acceptance Criteria
  • Assigned To

Action Items before full implementation

  • Discuss how to run ceremonies (Tom/Ramiro/Mike)
  • Update Github Projects (make sure labeling is correct, make sure we differentiate between epics and stories)
  • Discuss how we will write tickets. Includes story points, defining epics/stories/spikes/bugs (team)
  • Finalize value slicing and social contract and DoD artifacts (team)
  • Finalize how requirements are passed from client to Tickets (Rod/Tom/Mike)
Clone this wiki locally