Processes

Sprint 0

We start any new development project with Sprint 0. Sprint 0 is essentially our pre-planning. The main benefit of a Sprint Zero is that it allows a team to get an idea of the work ahead of them Should not take longer than a week, it should be kept lightweight and avoid big design principles. Don’t do more than is expressly needed for the first sprint to have a successful kickoff. Some of the key activities we do in Sprint 0 activities:

• Backlog updated.
• Set up repo.
• Set up deployment pipelines in Azure DevOps.
• Set up production environment (RFC needs to be approved)

Development:

During the development process, the developers are expected regularly (daily) update their local branches from the develop branch. Pull requests are used to request a merge into the develop branch. We are expected to have a shippable/deployable product at the end of each sprint cycle (2 weeks). This means the development is completed, all the necessary quality checks have been done – code review, pull requests, testing and merging, smoke testing and demos.

Deployment to Production

Because of the activities of Sprint 0, particularly the repo setup and the pipelines, deployment to production should be rather seamless. This should happen through the Azure Pipelines.