| Feature/Approach | | Agile (e.g., XP, Scrum) | DevOps | Essence (Practice-Independent) | | :--- | :--- | :--- | :--- | :--- | | Core Philosophy | Plan ahead, document everything, follow the plan. | People-oriented, flexible, responsive to change. | Unify development and operations, accelerate delivery. | Free practices from "method prisons"; use a universal kernel. | | Requirements Approach | Extensive, detailed documentation upfront; defined scope. | Flexible scope; user stories; evolving documentation. | Tends to follow an Agile requirements approach. | Agnostic; can describe any requirements approach using the Requirements Alpha. | | Development Model | Linear or semi-linear; distinct phases (e.g., Waterfall). | Iterative and incremental; rapid cycles. | Continuous Integration and Continuous Delivery (CI/CD). | Lifecycle-independent; can model any style of development. | | Primary Focus | Process and documentation. | Customer collaboration and working software. | Speed and reliability of delivery. | Shared understanding and reasoning about practice. | | Key Practices/Terms | Formal milestones, change control boards, extensive testing phases. | Sprints, user stories, daily stand-ups, pair programming. | CI/CD pipelines, infrastructure as code, monitoring. | Alphas (Requirements, Software System), Activity Spaces, Competencies. | | Resistance to Change | High; changes are costly and formal. | Low; embraces change even late in development. | Moderate; aims for rapid, automated change. | N/A; it's a framework, not a methodology. It helps you tailor your approach to manage change. |
: It emphasizes a "layered" approach to software engineering—focusing on quality, processes, methods, and tools—to build robust systems. Critical Perspectives software engineering practitioner 39s approach free
Creating a "map" for the software journey, including technical tasks, risks, and resources. | Feature/Approach | | Agile (e
Improving the internal structure of code without changing its external behavior. | Free practices from "method prisons"; use a
The book is suitable for:
Defining audits and reviews to guarantee the product meets specifications.