Overview
ISO/IEC 33202:2024 - Software and systems engineering - Core agile practices defines a concise, vendor‑neutral set of core agile practices and concepts that have wide acceptance across industries. The standard describes practices applicable to a single agile team or multiple teams and across the entire life cycle of software systems, products and services. It frames each practice with purpose, overview and expected outcomes, and includes conceptual foundations and conformance guidance for organizations that want to adopt or align to the standard.
Key Topics and Requirements
The standard organizes content into conceptual foundations, conformance rules, and a catalogue of core practices. Key technical topics include:
- Conceptual foundations: distinctions between practices and processes, criteria for defining a practice, and common agile concepts such as cadence, gemba and limiting work in progress.
- Conformance: intended usage and definitions for achieving full conformance to the standard.
- Practice descriptions: each practice is presented with a purpose, overview, and outcomes, providing a consistent structure for adoption and assessment.
- Core practices (selected examples from the standard):
- Agreement, Acquisition, Supply
- Cross‑functional, Feature and Component team practices
- Co‑located and Distributed team practices
- Collective ownership
- Release planning and Release review
- Deployment planning, Iteration planning, Synchronized iteration
- Daily synchronization, Cross‑team and Product owner synchronization meetings
- Value stream mapping
The standard does not prescribe a single agile methodology; instead it defines widely accepted practices and outcome expectations that organizations can implement, adapt or assess.
Practical Applications and Users
ISO/IEC 33202:2024 is practical for:
- Agile teams and team leads seeking a standardized reference for core practices.
- Agile coaches, scrum masters and product owners aligning team behaviors across programs.
- Engineering managers and program managers coordinating multiple teams or scaling agile.
- Procurement and supplier relationships where acquisition and supply practices need alignment.
- Organizations implementing process improvement, internal audits, or external certification where standardized agile practice descriptions support evaluation.
- Tool vendors and training providers who want to map features and curricula to an internationally recognized set of agile practices.
Using this standard helps reduce ambiguity when scaling agile, contracting work across teams or suppliers, and embedding agile practices consistently across the product life cycle.
Related Standards (if applicable)
For organizations aligning lifecycle or process frameworks, consider mapping ISO/IEC 33202:2024 to other ISO/IEC software and systems engineering standards (for example, ISO/IEC 12207 on software life cycle processes) to create a coherent compliance and improvement program.
Keywords: ISO/IEC 33202, core agile practices, agile standard, software engineering standard, agile teams, agile scaling, agile practices, value stream mapping.