Smart Version Control for Project Managers and Decision Makers
Today I’m going to tell you about Git version control (branching) model that we use widely in ISS Art to effectively manage code base of our projects. The experienced software development teams might know this model as major ideas were found long time ago and posted in the articles:
- Version Control for Multiple Agile Teams by Henrik Kniberg
- A successful Git branching model by Vincent Driessen
Here, I’m going to consolidate these ideas in the way that could be easily understood by software project managers, product owners and decision-makers to explain them the technical challenges that can arise due to certain harmful business decisions, and how they can impact development costs and schedule. Examples of harmful business decisions:
- Task reprioritization after development start
- Request to include one more feature in release during release testing
- Too many hotfix requests
No comments yet.
Add your comment