What is a sprint branch?

What is a sprint branch?

The sprint branch aims at containing commits of completed stories, the ones that will be presented to the Product Owner during the sprint review. This branch can be seen as the “ready for demo” branch. At the beginning of each new sprint, its sprint branch is created from the master branch (i.e.: sprint/S01).

What is a source code branch?

A branch is a copy of a codeline, managed in a version control system (VCS). Branching helps software development teams work in parallel. It separates out “in-progress work” from tested and stable code. The codebase in a VCS is often referred to as the trunk, baseline, master, or mainline.

What is branching in agile?

Since agile centers around user stories, task branches pair well with agile development. Each user story (or bug fix) lives within its own branch, making it easy to see which issues are in progress and which are ready for release.

How is a new Sprint branch created in Java?

2/ A new sprint branch is created from the original one (like ‘sprint/01-take2’), identified by the tag created at the beginning of the sprint. All story branches of approved stories are merged into this new branch. This is a tedious operation but the code history will be cleaner.

When do you create a sprint branch in scrum?

At the beginning of each new sprint, its sprint branch is created from the master branch (i.e.: sprint/S01). This operation can be managed by the Scrum Master for instance. It is also helpful to tag the branch at this point (you will understand why in ‘failed stories’).

When to push a story branch to sprint branch?

In a story branch, a pushed commit is a commit ready for code-review. Once a commit has been pushed, the dev team member should create a pull-request (also called merge-request) to the sprint branch in order to ease with the code review.

What does undone work in a sprint mean?

This would include source code, scripts, documentation basically whatever was changed when working with the story. However, creating branches causes merge-hell and if the work is planned to be completed in the next sprint it’s a lot of waste to revert the work already checked in.