Phase 5 · Module 11 of 15Quadrant D · the change
How Engineers Build Software
How does an idea become a change to a real software product?
By the end: You can follow the professional workflow from requirement to reviewed code, and recognize the rituals of an engineering team's week.
— The code workflow
L1Codebases, repositories, Git, GitHub, and commits~7 min○L2Branches, pushing and pulling, merges, and merge conflicts~9 min○L3Pull requests, diffs, code review, and approval~7 min○— The planning layer
L4Tickets, backlogs, requirements, scope, and MVPs~10 min○L5Estimates, dependencies, blockers, edge cases, and risk~10 min○— The team's rituals
L6Agile, scrum, sprints, standups, retros, and roadmaps~14 min○— The written culture
L7Specs, design documents, RFCs, ADRs, and code ownership~13 min○L8The debts we carry~10 min○What lights on your map here
codebaserepositoryGitGitHubbranchcommitpushpullmergemerge conflictpull requestdiffcode reviewapprovalticketbacklogJirarequirementscopeconstraintestimatedependency (RE: M9)blockerriskmilestoneedge casehappy pathacceptance criteriaMVPagilescrumkanbansprintstandupretroroadmaptechnical specificationdesign documentRFCADRcode ownershiptechnical debtlegacy systemrefactoringmaintenanceworkaround
Recognition terms — you'll know they exist
story pointsspike