...

• Channels where we receive input

• How we choose work to be done

• UX design

• UI design

• Jira

• Sprint planning

• …and everything else leading up to…

Development

After a developer is assigned a Jira task they begin work:

• Decide what the primary type of work is:

  • build: change in build system or dependencies

  • ci: change in continuous integration / deployment

  • docs: change to documentation

  • feat: a new feature is being added

  • fix: an existing bug or defect is being fixed

  • perf: change to improve performance

  • refactor: change to improve code quality

  • revert: reverts changes in a previous commit

  • style: change to code style/formatting

  • test: add missing tests or correct existing tests

• Ensure that the main branch in your cloned fork is up to date

• With the example Jira task FORMS-1234 that is a new feat, create a branch off your main with a name like: feat/1234-map-component (Note: you can name it anything you want, but the type/ format groups branches by type in the tools, and the 1234 makes it easy to find the corresponding Jira ticket)

• Crank out some code and tests (or tests and code, if you like TDD) and whatever docs are needed

1. This is a test

2. This is a second test

3. This is a third test