SAFe Scrum Master Study Guide 5.0, Complete Solution 2022/2023
6 vues 0 fois vendu
Cours
SAFe Scrum Master
Établissement
SAFe Scrum Master
SAFe Scrum Master Study Guide 5.0, Complete Solution 2022/2023
Agile frameworks
SAFe
Scrum
Crystal
Kanban
eXtreme Programming (XP)
Feature-driven development
What does a Scrum Master do?
- Servant leaders and coaches for an Agile Team.
- Help educate team in Scrum, XP, Kanban and SAFe, ...
complete solution 20222023 agile frameworks safe scrum crystal kanban extreme programming xp feature driven development what does a scrum master do servant le
École, étude et sujet
SAFe Scrum Master
Tous les documents sur ce sujet (252)
Vendeur
S'abonner
LectDan
Avis reçus
Aperçu du contenu
SAFe Scrum Master Study Guide 5.0, Complete
Solution 2022/2023
Agile frameworks
SAFe
Scrum
Crystal
Kanban
eXtreme Programming (XP)
Feature-driven development
What does a Scrum Master do?
- Servant leaders and coaches for an Agile Team.
- Help educate team in Scrum, XP, Kanban and SAFe, ensuring the agreed Agile
process is being followed.
- Help remove impediments and foster an environment for high-performing team
dynamics, continuous flow and relentless improvement.
- Facilitates team events
- Works with RTE to ensure train meets PI objectives
- Fosters normalized estimating within the team
- Assists the PO in backlog for PI and IP.
- Attends scrum of scrum meetings.
ART
Agile Release Train
PO
Product Owner
Program Increment (PI) Planning
A cadence-based, face-to-face event that serves as the heartbeat of the Agile Release
Train (ART), aligning all the teams on the ART to a common mission and vision.
Innovation and Planning Iteration
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.
Inspect & Adapt (I&A)
A significant event, held at the end of each PI, where the current state of the solution is
demonstrated and evaluated by the train. Teams reflect and identify improvement
backlog items via a structured, problem-solving workshop
Iteration
A basic building block of Agile development. Each is a standard, fixed-length timebox,
where Agile Teams deliver incremental value in the form of working, tested software
and systems.
Cycle - Defines, builds, integrates, & test.
What is the recommended timebox duration for an Iteration?
2 weeks; however, 1-4 weeks is acceptable, depending on the business context.
Who participates in the Inspect & Adapt (I&A) phase?
,All stakeholders, including:
1. The Agile Teams
2. Release Train Engineer (RTE)
3. System and Solution Architect Engineering
4. Product Management, Business Owners, and others on the Train
What results from the I&A phase?
Improvement backlog items that go to the Program Backlog for the next PI Planning
event
3 parts of I&A
PI System Demo
Quantitative Measurement
Retrospective and Problem-Solving Workshop
Purpose of PI System Demo
To show all the Features the ART has developed over the course of the PI
Leads: PM, PO, System Team
Attend: BO, Stakehlders, PM, RTE, SM & Teams
PI System Demo Timebox
~1 hr or less
What is one primary measurement to be considered in quantitative metrics?
Program predictability measure
Updated end of inspect & adapt event
Retrospective goal
To identify whatever issues they would like to address
Retrospective objective
To identify a few significant problems that the teams can potentially address - What
went well, what didn't go well, what can do better next time.
PDCA Cycle
Plan
Do
Check
Adjust
Who facilitates the PI Planning event?
Release Train Engineer (RTE)
In which iteration does PI Planning take place?
Innovation and Planning Iteration
__ ________ is essential to SAFe; if you are not doing it, you are not doing SAFe.
PI Planning
Business Benefits of PI Planning
- Establishing face-to-face communication across all team members and stakeholders
- Building the social network the ART depends on aligning development to business
goals with the business context, vision, and team project PI objectives
- Identifying dependencies and fostering cross-team and cross-ART collaboration
- Providing the opportunity for "just the right amount of architecture and Lean User
Experience (UX) guidance)
- Matching demand to capacity, eliminating excess WIP
- Fast decision-making
, PI Planning Inputs
Business context
Roadmap and vision
Top 10 features of the Program Backlog
NFRs (Non-functional Requirements)
PI Planning Outputs
Committed PI objectives (A set of SMART objectives that are created by each team with
the business value assigned by the Business Owners)
Program board (this highlights the new feature delivery dates, feature dependencies
among teams and with other ARTs, and relevant milestones)
Plan is the goal
3 Areas of Preparation for a Successful PI Planning
Organizational Readiness
Content Readiness
Facility Readiness
Organizational Readiness
Strategic alignment and teams trains setup
Content Readiness
Management and development preparedness
Facility Readiness
The actual space and logistics for the event
Organizational Readiness Considerations
Planning scope and context - is the scope (product, system or technology domain) of
the planning process understood? Do we know which teams need to plan together?
Business alignment - is there reasonable agreement on priorities among Business
Owners
Agile teams - Do we have Agile teams? Are there dedicated developer and test
resources and an identified Scrum Master and Product Owner for the team?
Content Readiness Considerations
Executive briefing - a briefing that defines the current business context
Product vision briefing(s) - briefing(s) prepared by Product Management including the
top 10 features in the product backlog
Architecture vision briefing - a presentation made by the CTO, Enterprise Architect, or
System Architect to communicate new enablers, features, and Nonfunctional
Requirements (NFRs)
Facility Readiness Considerations
Facility - this room must be roomy enough for all attendees, with breakout rooms if
necessary
Facilities/tech support - these people need to be identified in advance and reachable
during setup and testing, and the event itself
Les avantages d'acheter des résumés chez Stuvia:
Qualité garantie par les avis des clients
Les clients de Stuvia ont évalués plus de 700 000 résumés. C'est comme ça que vous savez que vous achetez les meilleurs documents.
L’achat facile et rapide
Vous pouvez payer rapidement avec iDeal, carte de crédit ou Stuvia-crédit pour les résumés. Il n'y a pas d'adhésion nécessaire.
Focus sur l’essentiel
Vos camarades écrivent eux-mêmes les notes d’étude, c’est pourquoi les documents sont toujours fiables et à jour. Cela garantit que vous arrivez rapidement au coeur du matériel.
Foire aux questions
Qu'est-ce que j'obtiens en achetant ce document ?
Vous obtenez un PDF, disponible immédiatement après votre achat. Le document acheté est accessible à tout moment, n'importe où et indéfiniment via votre profil.
Garantie de remboursement : comment ça marche ?
Notre garantie de satisfaction garantit que vous trouverez toujours un document d'étude qui vous convient. Vous remplissez un formulaire et notre équipe du service client s'occupe du reste.
Auprès de qui est-ce que j'achète ce résumé ?
Stuvia est une place de marché. Alors, vous n'achetez donc pas ce document chez nous, mais auprès du vendeur LectDan. Stuvia facilite les paiements au vendeur.
Est-ce que j'aurai un abonnement?
Non, vous n'achetez ce résumé que pour €12,01. Vous n'êtes lié à rien après votre achat.
