SAFe Scrum Master Exam latest 2022

SAFe Scrum Master Exam latest 2022Waterfall Lots of WIP, end-timed delivery of value Agile Reduced & visible WIP, iterative delivery, fast feedback Agile Value Statements Individuals and interactions over processes and tools. Working software over comprehensive documentation. Customer collaboration over contract negotiation. Responding to change over following a plan. 6 Agile Frameworks SAFe, Scrum, Crystal, Kanban, XP, Feature-Driven Development Agile Practices (8) Timeboxing, user stories, daily stand-ups, frequent demos, test-driven development, information radiators, retrospectives, continuous integration Scrum Values (5) Courage, Commitment, Respect, Openness, Focus Scrum Pillars (3) transparency, inspection, and adaptation Scrum Artifacts Product Backlog, Sprint Backlog, Burndown Charts Each iteration does these 4 things Defines, builds, integrates, and tests stories from iteration backlog Goal of an iteration Deliver working software at the end SAFe Core Values - Alignment - Transparency - Built-in Quality - Program Execution Non-functional requirements Conditions that a proposed IT system must meet, such as working on certain hardware or giving results within a certain time. Should be part of the DoD. Program Increment (PI) 8-12 weeks or 4-6 sprints. A timebox in which an Agile Release Train (ART) delivers incremental value in the form of working, tested software and systems. The most common pattern for one is four development iterations, followed by one Innovation and Planning (IP) iteration. Innovation and Planning Iteration (PI) Occurs every PI and serves multiple purposes. It acts as an estimating buffer for meeting PI objectives, as well as providing dedicated time for innovation, continuing education, and PI planning and Inspect and Adapt (I&A) events. SAFe Lean-Agile Principles (9 total) 1. Take an economic view. 2. Apply systems thinking. 3. Assume variability; preserve options 4. Build incrementally with fast, integrated learning cycles. 5. Base milestones on objective evaluation of working systems. 6. Visualize and limit WIP, reduce batch sizes, and manage queue lengths. 7. Apply cadence, synchronize with cross-domain planning. 8. Unlock the intrinsic motivation of knowledge workers. 9. Decentralize decision-making. Agile Release Train (ART) 5-12 teams (tycA long-lived and cross-functional team-of-Agile-teams, which along with other stakeholders, develops and delivers solutions incrementally, using a series of fixed-length Iterations within a Program Increment (PI) timebox. Aligns teams to a common business and technology mission. Product Management has content authority for the Program Backlog (owns, defines, and prioritizes it). They are responsible for identifying Customer needs, prioritizing Features, guiding the work through the Program Kanban and developing the program Vision and Roadmap. Solution Management has content authority for the Solution Backlog. They work with customers to understand their needs, prioritize Capabilities, create the Solution vision and roadmap, define requirements, and guide work through the Solution Kanban. Release Train Engineer (RTE) A servant leader and coach for the Agile Release Train. Facilitates the major events and processes, and assists the teams in delivering value. Communicates with stakeholders, escalate impediments, help manage risk, and drive continuous improvement. Business Owners The key stakeholders on the agile release train System Architect provides architectural guidance and technical enablement to the teams on the train SAFe Program Events, time boxes, values 1) PI Planning / 2 days / Teams commit to set of objectives to be delivered in the PI 2) ART Sync / 1 hour / Train teams sync regarding the progress of the PI 3) System Demo / 2 hours / Deliverables reviewed with stakeholders who provide feedback 4) Inspect and Adapt Event / .5 day / Train reviews and improves its process before the next PI Each Value Stream produces one or more ... Solutions, which are products, services, or systems delivered to the Customer, whether internal or external to the Enterprise.