software-engineering-eng-agile

Acceptance criteria using Given/When/Then structure define preconditions, triggers, and expected outcomes for user stories to guide Agile development and verification.

The Red-Green-Refactor TDD cycle is a process where you write a failing test, write the simplest code to pass it, and then refactor for simplicity while maintaining behavior.

Choosing between stubs, spies, mocks, and fakes depends on testing needs: stubs provide canned answers, spies record interactions, mocks verify expectations, and fakes simulate real implementations.

Setting up continuous integration with trunk-based development requires merging short-lived feature branches frequently into the main trunk to trigger automated quality gates and maintain fast feedback loops.

Pair programming is a core Extreme Programming practice where two developers collaborate at one workstation to improve code quality, share knowledge, and enforce real-time design reviews.

You should apply the YAGNI principle in simple design whenever adding speculative functionality to defer implementation until it is actually needed, reducing unnecessary complexity and maintenance overhead.