In case you are planning or making ready for SAFe Scrum Grasp SSM 6.0 (Scaled Agile Framework) certification then this text is so that you can get began.
Overview
- Put together nicely for the examination. Perceive all SAFe ideas and you may crack it like me!
- Requires 1 to three weeks of preparation relying upon your dedication per day.
- It’s essential to clear up 45 questions (a number of alternative = 1 reply and a number of choose = 2-3 solutions) in 90 minutes out of your laptop computer with none supervision. It’s an open-book on-line examination the place you possibly can seek for the solutions.
- Passing rating is 33/45 (73%) means you must reply at the least 33 (out of 45) questions appropriately. No damaging scoring so reply all of the questions!
- You get the consequence (Move or Fail) when you submit the examination.
- First try is included within the course registration price if taken inside 30 days after all completion. Every retake or try previous the 30-day window is $50
- You’ll be able to obtain the SAFe Scrum Grasp SSM Scholar Workbook after the course registration from https://community.scaledagile.com/
- Seek advice from the official Exam Details for extra info.
- Seek advice from the official SAFe Website for examination materials.
Examination Domains
- Area 1 – Introducing Scrum in SAFe (22-28%)
- Area 2 – Defining the Scrum Grasp / Crew Coach function (26-30%)
- Area 3 – Supporting Crew Occasions (17-21%)
- Area 4 – Supporting ART Occasions (25-29%)
Different Hyperlinks to Seek advice from:-
Examination Questions
Learn Leading SAFe Agilist 6.0 (Scaled Agile) Exam Questions
Purchase Leading SAFe Agilist 6.0 (Scaled Agile) Exam Questions with Answers and Explainations at reasonably priced worth
Follow Leading SAFe Agilist 6.0 Practice Exams at Udemy
Examination Notes
Lesson 1: Introducing Scrum in SAFe
What are the SAFe Agile Frameworks?
Agile Frameworks:-
• SAFe
• Scrum
• Kanban
Practices:-
• Timeboxing
• Frequent demos
• Data radiators
• Tales
• Take a look at-driven improvement
• Retrospectives
• Crew Syncs
• Habits-driven improvement
• Steady Integration
• Pair/mob programming
• DevOps
What’s the Agile Manifesto?
Agile Manifesto uncovering higher methods of growing software program by doing it and serving to others do it. By way of this work we’ve got come to worth:
- People and interactions over processes and instruments
- Working software program over complete documentation
- Buyer collaboration over contract negotiation
- Responding to alter over following a plan
That’s, whereas there’s a worth within the gadgets on the proper, we worth the gadgets on the left extra
Reference: https://scaledagileframework.com/lean-agile-mindset/
Reference: https://agilemanifesto.org/
What are the 12 Agile Manifesto Ideas?
- Our highest precedence is to fulfill the shopper by means of early and steady supply of priceless software program.
- Welcome altering necessities, even late in improvement. Agile processes harness change for the shopper’s aggressive benefit.
- Ship working software program incessantly, from a few weeks to a few months, with a desire for the shorter timescale.
- Enterprise folks and builders should work collectively every day all through the mission.
- Construct initiatives round motivated people. Give them the atmosphere and assist they want, and belief them to get the job carried out.
- Probably the most environment friendly and efficient methodology of conveying info to and inside a improvement crew is face-to-face dialog.
- Working software program is the first measure of progress.
- Agile processes promote sustainable improvement. The sponsors, builders, and customers ought to be capable of preserve a continuing tempo indefinitely.
- Steady consideration to technical excellence and good design enhances agility.
- Simplicity – the artwork of maximizing the quantity of labor not carried out – is crucial.
- The most effective architectures, necessities, and designs emerge from self-organizing groups.
- At common intervals, the crew displays on easy methods to develop into more practical, then tunes and adjusts its conduct accordingly.
Reference: https://scaledagileframework.com/lean-agile-mindset/
Reference: https://agilemanifesto.org/principles.html
What are the ten SAFe Lean-Agile Ideas?
- Take an economic view
- Ship Early and Typically
- Apply a Complete Financial Framework:-
-Function Inside Lean Budgets and Guardrails
-Perceive Resolution Financial Commerce-Offs: Improvement expense, Lead time, Product price, Worth, and Danger
-Leverage Suppliers
-Sequencing Jobs for Most Profit: Weighted Shortest Job First (MSJF)
- Apply systems thinking
- The Resolution Is a System
-Optimizing a element doesn’t optimize the entire system
-For the system to behave nicely, groups should perceive the supposed conduct and structure
-The worth of a system passes by means of its interconnections
-A system can evolve no sooner than its slowest integration level - The Enterprise Constructing the System Is a System, Too
- Perceive and Optimize the Full Improvement Worth Stream
- Solely Administration Can Change the System
- The Resolution Is a System
- Assume variability; preserve options
-Versatile necessities and design, the Cone of uncertainty, set-based over point-based method - Build incrementally with fast, integrated learning cycles
-PDCA = Plan – Do – Examine – Modify, The shorted the cycles, the sooner the educational
-Integration factors management product improvement and scale back danger - Base milestones on objective evaluation of working systems
-Part-gate milestones power design choices too early, false-positive feasibility, they assume a degree Resolution exists, big batches and lengthy queues, centralized necessities and design.
-Use Goal milestones as a substitute, PI System Demos, steady, cost-effective changes in the direction of an optimum Resolution) - Make value flow without interruptions
-Scale back batch dimension for greater predictability. Whole price = Holding price + Transaction price. Decreasing transaction prices will increase predictability, accelerates suggestions, reduces rework, and lowers price.
-Little’s Regulation: Wq = Lq / Lambda, Common wait time = Common queue size / Common processing charge - Apply cadence, synchronize with cross-domain planning
Cadence – converts unpredictable occasions into predictable occurrences and lowers price, makes ready occasions for brand new work predictable, helps common planning and cross-functional coordination, limits batch sizes to a single interval, controls injection of recent work, offers scheduled integration factors;
Synchronization – causes a number of occasions to occur concurrently, facilitates cross-functional trade-offs, offers routine dependency administration, helps full system integration and evaluation, offers a number of suggestions views - Unlock the intrinsic motivation of knowledge workers
-Employees are most certified to make choices about easy methods to carry out their work
-The employees have to be heard and revered for administration to steer successfully
-Information employees should handle themselves. They want autonomy
-Persevering with innovation have to be a part of the work, the duties, and the tasks of data employees.
-Unlocking intrinsic motivation with autonomy, mastery, and goal - Decentralize decision-making
Centralize – Rare, Lengthy-lasting, Important economies of scale
Decentralize – Frequent, Time vital, Requires native info - Organize around value
-Worth doesn’t observe silos
-Set up round Improvement Worth Streams.
Reference: https://scaledagileframework.com/safe-lean-agile-principles/
What are the 4 SAFe core values?
SAFe has the next 4 core values:-
- Alignment
- Transparency
- Respect for folks
- Relentless enchancment
Reference: https://scaledagileframework.com/safe-core-values/
What are the Scrum pillars and values?
- The three pillars of Scrum are transparency, inspection, and adaptation
- The 5 values of the Scrum are Braveness, Dedication, Focus, Respect, and Openness
What are the SAFe vs Scrum Terminologies?
SAFe | Scrum |
---|---|
Iteration | Dash |
Iteration Planning | Dash Planning |
Iteration Evaluation | Dash Evaluation |
Iteration Retrospective | Dash Retrospective |
Iteration Targets | Dash Targets |
Iteration Backlog | Dash Backlog |
Crew Sync | Every day Scrum |
Agile Crew | Scrum Crew |
Crew Increment | Increment |
Program Increment (PI) | Usually 5 Sprints |
Program Increment (PI) Planning | Planning for sometimes 5 Sprints |
Cadence and Synchronization | Velocity |
Agile Launch Prepare (ART) – Groups of Agile groups | Groups of Scrum groups |
Launch Prepare Engineer | Chief scrum Grasp |
ART Sync | Scrum of Scrum |
What’s an Iteration?
- Definition: Iterations are a single improvement cycle the place every Agile Crew defines, builds, integrates, and checks the Tales from their Iteration Backlog
- Period: Every Iteration is similar size, operating back-to-back.SAFe advises two-week Iterations
- Purpose: To ship new worth to the Buyer on the finish of every Iteration
- Keep away from including scope as soon as the Iteration has begun
What’s an Agile crew?
- An Agile Crew is a cross-functional group of sometimes ten or fewer people with all the talents essential to outline, construct, take a look at, and deploy increments of worth to their prospects.
- Agile groups are optimized for communication and the continual supply of worth to the shopper.
- Agile Groups visualize movement with SAFe Scrum or SAFe Kanban
- Agile Crew Occasions are:- Crew Sync, Backlog Refinement, Iteration Evaluation, Iteration Retro, Iteration Planning
The Agile Crew’s tasks are:-
- Connecting with the Buyer (led by PO)
- Planning the Work: ART Planning (PI Planning), Crew planning utilizing SAFe Scrum or SAFe Crew Kanban, and refining the Crew Backlog.
- Delivering Worth: Continuously combine and take a look at, Sync with different groups in ART by means of ART Sync (contains Coach Sync and PO Sync), construct steady supply pipeline, launch incessantly.
- Getting Suggestions: with the assistance of PO and thru System Demos
- Enhancing relentlessly: take part in ART’s joint Examine & Adapt, deal with the issues as they happen
Reference: https://scaledagileframework.com/agile-teams/
What are the 2 specialty roles in Agile Groups?
The Agile Crew comprises two specialty roles:- Product Proprietor (PO) and Scrum Grasp/Crew Coach (SM/TC).
- Product Proprietor (PO) tasks are:-
- Join with the shopper
- Contribute to the Imaginative and prescient and Roadmap
- Handle and prioritize the Crew Backlog
- Assist the crew in delivering worth
- Get and apply quick suggestions
- Scrum Grasp/Crew Coach (SM/TC) tasks are:-
- Facilitate SAFe Scrum (or SAFe Kanban) and PI planning
- Helps Iteration Execution
- Improves Circulation
- Construct a high-performing crew
- Optimizes and improves the crew and ART efficiency
Reference: https://scaledagileframework.com/agile-teams/
What’s Agile Launch Prepare (ART)?
- ART is a crew of cross-functional Agile Groups and has the capabilities to outline, construct, validate, and launch to ship a steady movement of worth.
- ART is a digital group of 5-12 groups (50-125+ people)
- All of the groups in ART are synchronized on a standard cadence – a Program Increment (PI), aligned to a standard mission by way of a single Program Backlog (ART Backlog).
Crucial Roles within the ART are:-
- Launch Prepare Engineer (RTE) is a servant chief (chief scrum grasp) who facilitates ART execution, obstacle removing, danger and dependency administration, and steady enchancment.
- Product Administration is essentially liable for ‘what will get constructed,’ as outlined by the Imaginative and prescient, Roadmap, and new Options within the ART Backlog. They work with prospects, groups, and Product Homeowners to know and talk their wants and take part in answer validation.
- System Architect is a person or crew that defines the system’s general structure. They work at a stage of abstraction above the groups and parts and sometimes outline Non-functional Necessities (NFRs), main system components, subsystems, and interfaces.
- Enterprise Homeowners are key stakeholders of the ART, with ultimate accountability for the enterprise outcomes of the practice.
- Clients are the final word financial consumers or worth customers of the answer.
Different important roles within the ART are:-
- System Groups sometimes help in constructing and sustaining improvement, steady integration, and take a look at environments.
- Shared Providers are specialists crucial for the success of an ART however can’t be devoted to a particular practice. They usually embody information safety, info architects, web site reliability engineering (SRE), database directors (DBAs), and plenty of extra.
Three Sync occasions to maintain ART on observe:-
- Coach Sync: (timeboxed: 1 hour) focuses on executing the present PI, together with danger, dependencies, progress, and impediments
- PO Sync: manages the PI’s scope, opinions progress, adjusts priorities, and prepares for the next PI
- ART Sync: normally replaces the Coach Sync and PO Sync for a selected iteration to cut back overhead. The ROAM board created throughout PI planning could be reviewed throughout the ART Sync. ART Planning board is used throughout ART sync to trace and handle dependencies, guaranteeing they don’t block different groups.
Different occasions in ART:-
- PI Planning (timeboxed: 2 days) Every ART begins with the PI Planning utilizing the PI planning board, the result is PI Targets to be accomplished within the PI iteration.
- System Demos (timeboxed: 1 hour) Happen on the finish of Iteration to overview deliverables and obtain suggestions from stakeholders, enterprise house owners, and prospects.
- Examine & Adapt (timeboxed: 1/2 day) Every PI concludes with I&A occasion for retrospection the place ART opinions and improves its course of earlier than the following PI.
Reference: https://scaledagileframework.com/agile-release-train/
Reference: https://scaledagileframework.com/planning-interval/
Lesson 2 – Characterizing the Function of the Scrum Grasp
What are the traits of an efficient Scrum Grasp?
A Scrum Grasp acts as a Servant Chief. An efficient scrum grasp ought to have the next traits:-
- Empathetic: Perceive and empathize with others.
- Battle navigator: Hearken to and assist crew members in drawback identification and decision-making
- Servant Chief: Persuade moderately than use authority. Seeks to assist with out diminishing the dedication of others.
- Mentor: Encourage and assist the non-public improvement of every particular person
- Clear: Is open and appreciates openness in others
- Coach: Thinks past day-to-day actions
What are the tasks of the Scrum Grasp within the SAFe enterprise?
- Works with the RTE to make sure the practice meets its general PI Targets
- Coordinates with different Scrum Masters, the System Crew, and Shared Providers throughout PI Planning
- Works with the groups all through every Iteration and PI
- Participates within the Coach Sync
- Fosters normalized estimating inside the crew
- Helps groups function beneath architectural and portfolio governance, system integration, and System Demos
What are the frequent attributes of the high-performing crew?
The Scrum grasp’s accountability is to construct a high-performing crew with the next frequent attributes:-
- Self-organizing
- Efficient decision-making
- Open and clear communication
- Worth variety
- Mutual belief
- Wholesome battle
- Clear objectives and goal
- Focus and focus
- Possession and accountability
- Perceive work’s influence on a company
- Aligned and collaborative
- Protected environment to take dangers
- Efficient, well timed suggestions
- Enough sources for native management
- Success focus over failure avoidance
- Skills balanced with problem
- Engagement
- Have enjoyable with work and one another
There are 4 levels of constructing a high-performing crew:-
- Forming
- Storming
- Norming
- Performing
What are the Crew Occasions?
Occasion | Timebox | Worth |
---|---|---|
Backlog Refinement | 1 hour | Crew prepares necessities for Iteration Planning |
Iteration Planning | 2 to 4 hours | Crew commits to a set of objectives to be delivered in theIteration |
Crew sync | quarter-hour | Teammembers sync concerning the progress of theIteration Targets |
Iteration Evaluation | 1 hour | Crew meets with stakeholders to overview thedeliverables and supply suggestions |
Iteration Retrospective | 1 to 1.5 hours | Teamreviews and improves its course of earlier than thenext Iteration |
Lesson 3 – Experiencing PI Planning
What’s PI Planning and its occasions?
- PI Planning stands for Program Increment Planning.
- PI Planning is a cadence-based occasion that serves because the heartbeat of the ART, aligning all groups on the ART to a shared mission and Imaginative and prescient.
- PI Planning classes are frequently scheduled occasions held all year long the place a number of groups inside the identical Agile Launch Prepare (ART) meet to align to a shared imaginative and prescient, talk about options, plan the roadmap, and establish cross-team dependencies.
- PI Planning is a 2 full day occasion that sometimes runs each 8-12 weeks (10 weeks typical). The 2-day agenda is as follows:-
Day 1 08:00 – 09:00 Enterprise Context 09:00 – 10:30 Product/Resolution Imaginative and prescient 10:30 – 11:30 Structure Imaginative and prescient and Improvement Practicies 11:30 – 01:00 Planning Context and Lunch 01:00 – 04:00 Crew breakouts 04:00 – 05:00 Draft Plan Evaluation 05:00 – 06:00 Administration overview and drawback fixing Day 2 08:00 – 09:00 Planning Adjustment 09:00 – 11:00 Crew breakouts 11:00 – 01:00 Remaining Plan Evaluation and Lunch 01:00 – 02:00 ART Dangers 02:00 – 02:15 Confidence Vote 02:15 – ?? Plan Rework (if wanted) When prepared Planning Retrospective and shifting ahead - Major Inputs to the PI Planning embody: 1. Enterprise context, 2. Roadmap & imaginative and prescient, and three. Highest precedence Options (sometimes high 10) of the ART backlog
- Major Outputs of the PI Planning embody: 1. Dedicated PI goals, and a pair of. ART planning board
- Product Administration offers the imaginative and prescient and backlog (sometimes represented by the highest ten or so upcoming options) and owns the function priorities
- Enterprise Proprietor offers the enterprise context and assigns enterprise worth (BV) to every PI Goal on a scale from 1 to 10
- Improvement Groups personal Story planning and high-level estimates
- ART Planning Board is used for PI Planning displaying: 1. Options, 2. Important Dependency, and three. Milestone or Occasion
- Architect and UX work as intermediaries for governance, interfaces,and dependencies
Reference: https://scaledagileframework.com/pi-planning/
What are PI Uncommitted Targets?
Uncommitted goals are used to establish work that may be variable inside the scope of a PI. The work is deliberate, however the end result is just not sure. Groups can apply uncommitted goals every time there may be low confidence in assembly the target. This may be as a consequence of many circumstances:
- Dependencies with one other crew or provider that can’t be assured.
- The crew has little to no expertise with performance of this sort. On this case the groups could plan ‘Spikes’ early within the PI to cut back uncertainty.
- There are a lot of pretty vital goals that the enterprise is relying on and the crew is already loaded near full capability.
What’s a Function?
- Options are maintained within the ART Backlog
- Function are sized to slot in a Program Increment (PI) and delivered by a single Agile Launch Prepare (ART)
- Options are break up into Tales and slot in one Iteration for one crew
- Options embody a definition of Minimal Marketable Function (MMF), a profit speculation (to justify improvement price) and Acceptance standards (outlined throughout program backlog refinement).
- Options are prioritized utilizing WSJF and the highest 10 options are offered to the crew throughout PI planning
- Usually Product Administration creates enterprise options and System Architect creates enabler options
Reference: https://scaledagileframework.com/features-and-capabilities/
What’s a Story?
- Options are applied by Tales
- Tales are small increments of worth that may be developed in days and are comparatively straightforward to estimate
- Options suits in a single PI for one ART; Tales suits in a single iteration for one crew.
- A Story Level is a relative quantity that represents: Quantity, Complexity, Information, and Uncertaity.
- Crew breaks down Options into Person Tales and Enabler Tales
Reference: https://scaledagileframework.com/story/
write a great Story?
What’s an Acceptance standards?
- Present the main points of the Story from a testing perspective
- Are created by the Agile Crew
- May be written within the Given-When-Then format
As a driver, I need to get a receipt after fueling in order that I can expense the acquisition. Acceptance standards:- Given that the fueling is over When the driving force asks for the receipt Then it's printed and contains: quantity fueled, the quantity paid, tax, date, time
What are Enabler Tales?
Enabler Tales construct the groundwork for future Person Tales. There are 4 sorts of Enabler Tales:-
- Infrastructure: Construct improvement and testing frameworks that allow a sooner and extra environment friendly improvement course of
- Structure: Construct the Architectural Runway, which allows smoother and sooner improvement
- Exploration: Construct an understanding of what’s wanted by the Buyer to know potential Options and consider options
- Compliance: Facilitate particular actions reminiscent of verification and validation, documentation, signoffs, regulatory submissions, and approvals
What’s a Story Level?
- Fibonacci is used for Story Level estimation
- A Story level is a singular quantity that represents:-
– Quantity: How a lot is there?
– Complexity: How laborious is it?
– Information: What do we all know?
– Uncertainty: What’s not identified? - Story factors are relative. They aren’t linked to any particular unit of measure.
– An 8-point Story ought to take 4 occasions longer than a 2-point Story to finish
– Usually, a 1-point Story would take at some point to developand take a look at - Estimating Poker can be utilized for quick and relative estimation