Development process

Development process

General

Development is done using Kanban with cadences for planning and reviewing. Cadences have two purposes: Provide transparency and make it clear when work is planned and reviewed Add trust between "business team" and development team by continuously adding and demonstrating value Visioning, planning, and reviewing is done using two week cadence.

Two week development cadence

Period is divided into two weeks. The only difference between weeks is that Friday's meeting agenda will change biweekly:

• Week1 Friday meeting will concentrate on demonstrating implemented features
• Week2 Friday meeting will concentrate on visioning and grooming the backlog and seeing what functionality will be implemented next

Branching, backlog and milestones

All code that we work on must reside under https://github.com/HSLdevcom. Repositories should be either:

• Forks from other repositories (e.g. OpenTripPlanner)
• Our own work (e.g. OpenJourneyPlanner)

Forks from projects that are not controlled by us are done for two reasons:

• It enables us to use our own issue management for every software component
• If we must, we can deploy new versions even when our pull requests are not accepted to upstream repositories