YUNOVA · Agile and Scrum
Module 9: Agile engineering and quality
Extreme Programming practices
Key points
- XP pairs short cycles with practices like pair programming, small releases and refactoring.
- Simple design and collective code ownership keep code easy for any team member to change.
- Customer feedback arrives often, so the team adjusts the plan every iteration.
Test-driven development in Agile teams
Key points
- TDD follows red, green, refactor: write a failing test, make it pass, then clean up.
- Tests written first describe the behaviour before the code exists.
- A growing test suite lets the team change code with less fear of breaking it.
Continuous integration in Scrum
Key points
- Continuous integration merges small changes to the main branch many times a day.
- Each merge triggers an automated build and test run that flags breakages quickly.
- A green build supports the Scrum goal of a usable Increment every Sprint.
Managing technical debt
Key points
- Technical debt is the future cost of shortcuts taken in code or design.
- Make debt visible by adding it to the Product Backlog with a clear description.
- Reserve regular capacity to pay debt down so delivery speed does not keep dropping.