Sprint26: Orchestrating the Build
Great software isn’t just built; it is managed. When a team scales or a project moves closer to production, the biggest bottlenecks are rarely syntax errors—they are merge conflicts, leaked secrets, mismatched environments, and broken timelines.
In Session 6 of the Sprint26 series, we dive into SWEBOK Chapter 8 (Software Configuration Management) and Chapter 9 (Software Engineering Management). We are moving past solo development into the operational mechanics required to coordinate teams, protect codebases, and deliver software on time.
What we’ll cover:
Team Workflows: Debating Git branching strategies (Gitflow vs. Trunk-Based Development) to choose what fits your velocity.
Configuration Management: The discipline of isolating Development, Staging, and Production environments while securely managing secrets and versioning.
The Estimation Paradox: Breaking down why software projects are chronically late and how to estimate with data rather than guesswork.
The Codelab: We are taking the Zetu repository and setting it up for multi-developer collaboration and deployment. In this hands-on lab, we will:
Restructure the Zetu repo to support a structured branching strategy.
Configure environment variables and secrets management for multi-stage pipelines.
Run a live Sprint Planning exercise using the remaining Zetu backlog, estimating features and drafting a realistic delivery roadmap.