click to reveal definition
click to flip back
You know 0 of 24 cards in current set.
Ready to get certified?
Get CertifiedNeed this expertise applied inside your organization?
Explore Our ServicesFull Glossary
Foundations
- Agile Software Engineering
- The technical practices — test-first, continuous integration, quality design — that let teams build software with speed, quality, and adaptability at scale.
- Why Technical Agility
- Process agility fails without engineering practices that make software easy to change safely; ASE builds those practices.
- Built-In Quality
- Ensuring quality is created as software is built, through practices like test-first and continuous integration, rather than inspected in later.
- Fast Feedback
- Short feedback loops from tests and integration that catch problems early and cheaply.
Mindset
- Agile-Quality Mindset
- A commitment to keeping code clean, tested, and adaptable so teams sustain a fast pace.
- Emergent Design
- Letting design evolve through refactoring and learning rather than fixing it fully upfront.
- Collective Ownership
- The whole team owns and can improve all the code, supported by tests and shared standards.
Test-First
- Test-First Development
- Writing tests before code to specify behavior, drive design, and build quality in.
- Test-Driven Development (TDD)
- Developer test-first practice using red-green-refactor to create well-tested, well-designed units.
- Behavior-Driven Development (BDD)
- Business-facing test-first practice expressing behavior in Given-When-Then scenarios that become tests.
- Acceptance Test-Driven Development
- Defining acceptance tests collaboratively before development so teams share a clear, testable goal.
- Test Automation
- Automating tests so they run frequently, enabling continuous integration and fast feedback.
Continuous Integration
- Continuous Integration (CI)
- Frequently integrating and testing changes so defects surface early and the system stays working.
- Version Control
- Managing all changes in source control with practices that support frequent integration.
- Continuous Delivery Pipeline
- The automated flow that builds, tests, and delivers changes toward production reliably.
- Trunk-Based Development
- Integrating small changes frequently to a shared mainline to reduce merge risk.
Design & Quality
- Refactoring
- Improving code structure without changing behavior, kept safe by tests.
- SOLID Principles
- Object-oriented design guidelines that produce flexible, maintainable code.
- Design Patterns
- Proven, reusable solutions to recurring design problems.
- Code Quality and Smells
- Recognizing and removing signs of poor design like duplication and tight coupling.
- Clean Code
- Writing readable, simple, well-structured code that is easy to change and maintain.
Applying It
- Executable Specifications
- Tests that specify and verify behavior, doubling as living documentation.
- Engineering in SAFe
- Applying these practices across Agile Release Trains so quality and flow scale with the organization.
- Continuous Improvement
- Relentlessly improving engineering practices to sustain speed and quality over time.