Wedge Team – we provide all of the key, high-level roles that are not needed full time on the project but are essential to success. This team acts as a ‘startup’ team to ensure the project is foundationally sound – and the team continues on throughout the project, attending sprint planning and review sessions as they occur. This team includes: Architect, Engagement Manager, Scrummaster, and QA Manager.
Master – Production Server Branch
- Only Tech Lead pushes into Master branch
- Master should contain current Production code
- Code should be pushed To Master only from Staging Branch after regression QAT on it and UAT Hot Fixes
Staging – Staging Server Branch
- Only Tech Lead pushes into that branch
- Master should contain current Staging Server code
- Tech Lead should push to this branch from Sprint, UAT and Hot Fix Branches
Sprint # – Branch for each sprint (for Test Server)
- Tech Lead reviews and merges pull requests from Team members
- Demo is done from that branch during sprint review
- Current sprint branch should contain code that is on Test Server
- Each new Sprint branch should be created as a copy of Last Staging branch version
Story#/Bug – Branch for each story
- Each team member creates a branch for his User Stories (as a copy of Current Sprint Branch)
- Name of the Branch should start with User Story JIRA ID
- If the Sprint branch was changed before dev finishes his User Story – it should be pulled to his Story Branch
- After Story branch contains final code – Dev should create a Pull Request to Sprint Branch