Detail
When you are ready to take the exam, log into the SAFe Community Platform to access the exam.
When the exam timer ends, the exam will be submitted, regardless of the number of questions answered. A score will be calculated based on the number of questions answered. Unanswered questions will be automatically marked as incorrect. If you finish answering all questions before the exam timer ends, you can click the “Submit” button and your score will be calculated.
When you launch the exam, you will be required to review and accept the Candidate Agreement before starting the exam. Exams are timed and the timer will be visible throughout the exam.
Questions are structured in multiple choice or multiple response format.
Questions will require either one answer or multiple. “Choose two” or a “Choose three” style multiple response questions indicate the number of answers required for the question. Multiple response questions require all correct answers to be selected as no partial credit is given.
Details are subject to change at any time
| Duration | 120 minutes |
| Number of questions | 60 |
| Passing score | 42/60 (70%) |
| Competency level | Intermediate difficulty; Proficient, capable; can perform tasks with some assistance |
| Question format | Multiple choice (one answer) or multiple select (2-3 answers) |
| Delivery | Web-based, closed book, no outside assistance, timed |
| Access | Community Platform upon completion of the course |
| Languages offered | English |
| Cost | First attempt included in the course registration fee if taken within 30 days of course completion. Each retake or attempt past the 30-day window is $50 |
| Exam Sections and Percentages | References |
| Introducing the course (7%)Define Agile Software EngineeringIdentify practices that define Software Engineering as Agile | SAFe Agile Software Engineering Student Workbook: materials and exercises from Lessons 1 and 2 |
| Connecting principles and practices to built-in quality (10%)Identify the Core XP PracticesRelate Core XP Practices to SAFe PrinciplesDemonstrate the core values that drive SAFe PrinciplesDefine Benefit HypothesisDefine Test-Driven DevelopmentDefine Behavior-Driven DevelopmentDefine Built-In QualityDefine application external and internal qualities | SAFe Agile Software Engineering Student Workbook: materials and exercises from Lessons 2 and 3www.scaledagileframework.com/built-in-quality/www.scaledagileframework.com/lean-ux/ www.scaledagileframework.com/test-first/ |
| Accelerating flow (7%)Outline the flow of valueDetermine the components of a value streamDetermine waste and delay in a development streamProvide examples of a Benefit HypothesisProvide examples of metrics for a Behavior Hypothesis | SAFe Agile Software Engineering Student Workbook: materials and exercises from Lesson 3 |
| Applying intentional architecture (8%)Apply systems thinking in the context of Software EngineeringExplain the role of Agile architecture in supporting Lean-Agile developmentDefine the Lean-Agile Architecture PrinciplesIllustrate the difference between Emergent Design and Intentional ArchitectureArchitect and design for testabilityDemonstrate the role of Test Doubles | SAFe Agile Software Engineering Student Workbook: materials and exercises from Lesson 4www.scaledagileframework.com/design-for-testability-a-vital-aspect-of-the-system-architect-role-in-safe |
| Thinking test-first (12%)Explain reasons for shifting testing left vs traditional testing paradigmDefine the use of the Testing PyramidExplain the Agile testing matrixIdentify the types of tests in the Agile testing matrixOutline the role of Nonfunctional RequirementsBuild quality in throughout the pipelineUse testing in a continuous flow | SAFe Agile Software Engineering Student Workbook: materials and exercises from Lesson 5www.scaledagileframework.com/nonfunctional-requirements/www.scaledagileframework.com/built-in-quality/ |
| Discovering story details (7%)Examine story criteriaIdentify how stories are estimatedIdentify how acceptance criteria are turned into testsSplit stories to reduce the Minimum Marketable FeatureDefine workflow steps and storymapsIdentify how workflows and storymaps are relevant to testing | SAFe Agile Software Engineering Student Workbook: materials and exercises from Lesson 6www.scaledagileframework.com/story/ |
| Creating a shared understanding with behavior-driven development (13%)Apply Behavior-Driven Development for shared understandingExplain the difference between behavior and test of behaviorSpecify desired behavior for domain termsSpecify behavior for business rules and algorithmsIdentify issues with large testsTest the User InterfaceApply test doubles to Behavior-Driven DevelopmentIdentify existing tests impacted by new requirements | SAFe Agile Software Engineering Student Workbook: materials and exercises from Lesson 7www.scaledagileframework.com/lean-ux/ www.scaledagileframework.com/test-driven-development/www.scaledagileframework.com/behavior-driven-development/ |
| Communicating with models (5%)Explain the importance of modelingOutline Static modelsDemonstrate Class-Responsibility-Collaboration relationshipOutline Dynamic modelsOutline State models | SAFe Agile Software Engineering Student Workbook: materials and exercises from Lesson 8www.extremeprogramming.org/rules/crccards.html |
| Building systems with code quality (8%)Define code qualitiesDefine cohesion and couplingExplain the benefits of collective ownershipDefine Abstract Data TypesDescribe aspects of code readability | SAFe Agile Software Engineering Student Workbook: materials and exercises from Lesson 9 |
| Building systems with design quality (13%)Explore design tradeoffsIllustrate the Rule of ThreeDetermine criteria for choosing design alternativesExplain Interface-Oriented DesignExplain the SOLID principlesApply quality decomposition practicesApply differentiation and synthesisApply software design patterns | SAFe Agile Software Engineering Student Workbook: materials and exercises from Lesson 10www.scaledagileframework.com/agile-architecture/ |
| Implementing with quality (10%)Design and test from contextApply Test-Driven Development practices for writing softwareExplain the Test-Driven Development cycleImplement test doubles and test dataRefactor to support new behavior of the codePractice Emergent Design | SAFe Agile Software Engineering Student Workbook: materials and exercises from Lesson 11 |