- What is DevOps? (page)
- Introduction to DevOps (18m)
- Slow Down, Go Faster (page)
- State of DevOps - 2021 (slides)
- Transformational Leadership & DevOps (29m)
- DevOps: A Culture Transformation (32m)
- Comparing Agile vs Traditional Roles (58m)
- Stop "Going Agile" (32m)
- Lean vs Agile vs Design Thinking (47m)
- The Five Ideals of DevOps - IT Revolution (page)
- What DevOps Taught Me About Agile | Scrum.org (page)
- CI/CD Pipeline: Everything You Need to Know (page)
- Please stop recommending Git Flow!
- How trunk-based delivery is key to faster, more reliable software
- DevOps tech: Trunk-based development | Google Cloud
What is a branching strategy? source
A “branching strategy” refers to the strategy a software development team employs when writing, merging, and shipping code in the context of a version control system like Git. Software developers working as a team on the same codebase must share their changes with each other. But how can they do this efficiently while avoiding malfunctions in their application? The goal of any branching strategy is to solve that problem and to enable teams to work together on the same source code without trampling on each other. A branching strategy defines how a team uses branches to achieve this level of concurrent development.
- Scrum Basics (7m)
- What is Agile? (5m)
- What is Scrum? (13m)
- Scrum Values (12m)
- Estimating & Planning (8m)
- Scrum Pillars (4m)
- Product Backlog (8m)
- Sprint Backlog (6m)
- Sprint Review (5m)
- Retrospective (5m)
- Praise the Product Owner(5m)
- Sprint Planning (8m)
- Backlog Grooming (5m)
- TDD & BDD (4m)
- What is TDD? (5m)
- What is BDD? (4m)
- TDD vs BDD: Focus (5m)
- TDD vs BDD: Writer & Reader (5m)
- TDD vs BDD: Speed of Execution (5m)
- TDD vs BDD: Specificity (5m)
- TDD vs BDD: Summary (7m)
- Leaving Time for Testing (7m)
- Good Gherkin Enables Good Testing
- Clean Code Fundamentals (54m)
- BDD vs Traditional (9m)
- BDD in Action (60m)
- What is Clean Code? (108m)
- Comments Lie (66m)
- Professionalism (60m)
- TDD (90m)
- Good Architecture (130m)
- Clean Code - TDD pt1 (61m)
- Clean Code - TDD pt2 (75m)
- TDD w/JB Rainsberger (65m)
- Coding Blocks Clean Code