Please enable JavaScript.
Coggle requires JavaScript to display documents.
Prep. Examen SCRUM MASTER Curso LinkedIn por Kelley O'connell, "…
Prep. Examen SCRUM MASTER
Curso LinkedIn por Kelley O'connell
Four principles
Individuals interactions
(over process and tools)
Working Software
(over contract negotiation)
Customer Collaboration
(over comprehensive documentation)
Responding to change
(over following a plan)
Foundation
Agile manifesto 2001
Scrum: just at time and
customer into the team
Highly flexible
Adaptative Framework
12 principles
1 Satisfy Customers Through Early & Continuous Delivery
2 Welcome Changing Requirements Even Late in the Project
3 Deliver Value Frequently
4 Break the Silos of Your Project
5 Build Projects Around Motivated Individuals
6 The Most Effective Way of Communication is Face-to-face
7 Working Software is the Primary Measure of Progress
8 Maintain a Sustainable Working Pace
9 Continuous Excellence Enhances Agility
10 Simplicity is Essential
11 Self-organizing Teams Generate Most Value
12 Regularly Reflect and Adjust Your Way of Work to Boost Effectiveness
Pilares
TRANSPARENCY
INSPECTION
ADAPTATION
SCRUM EVENTS
Sprint planning
Outcomes
Sprint goal
Backlog items for sprint
Sprint plan
Time: 2 hours/1 week of the sprint
Daily Scrum
Time: 15 minutes/day
SCRUM ALLIANCE
Entire scrum team attends
Any scrum team member
can provide updates
Any interested party can attend
SCRUM GUIDE
Team member attended
and facilitated
No attendance by scrum mastar
No participation by PO
QUESTIONS
What did I do yesterday
to help meet sprint goal?
What will I do today to help
meet the sprint goal?
What impediment do I have that are
blocking me from meeting the sprint goal?
Sprint review
Time: 4 hours/month
Sprint retrospective
Time: 3 hours/month
Timebox and sprint planning
meeting inputs
Ordered product backlog
Record of completed items
Knowledge of past performance
Development team capacity
SCRUM VALUES
Commitment
Courage
Focus
Openness
Respect
SCRUM MASTER ROLE
Customer
Ensure backlog is updated
Make sure sprints are appopiate
Development
Protect against outside distractions
Protect against overwork and burnout
(exceso de trabajo y agotamiento)
Prevent complacency
Own the scrum framework
Scrum
owner and leader of the process
Responsible for educating the team, P.O.,
Organization
Servant role
Focused on helping others
get the most out scrum
Product Owner
Clarify goals and objectives
Coach best practices
Guide process and planning
Facilitate scrum events
Share knowledge
Organization
Coach the adoption of scrum
Guide awareness and understanding
Help others scrum masters
Assist their development teams
PRODUCT OWNER ROL
Manage the product backlog
Finals decisions over product
Clearly express PBIs
Order PBIs efficently
Ensure backlog is accessible
Clary requirements
Provide status report and forecast
DEVELOPMENT TEAM
3 a 9 people (5 as ideal)
Self-organizing
Cross-functional (T perfil)
Doesn't acknowledge roles o titles
How to minimize disruption
Early inclusion (people with skills necessary)
Big-picture perspective
Backlog understanding
Timing estimations
NORMS
Interactions
Considering ideas
Asking for help
Keeping commitments
Holging team accountable
Communication
Respect
Gratitude
Meeting interaction
Device usage
Start/end times (on time)
Preferred hours
Decision making
Consensus standard
Voting rules
Tiebreakers (desempates)
Conflict resolution
Process
Expectations
Escalation
ARTIFACTS
Product backlog
Robust
Value
PBIs Characteristics
Feature
Functionality
Requirement
Defect
Enhacement
Backlog ordering
ONGOING
PO and delegates refine
requirements for product
Product increment
(working software)
Team's definition of DONE
PO's accetance criteria
Value envisioned in sprint goal
Definition of DONE
Workin software with
high-quality standards
Acceptance criteria for PBI specific
Definition of DONE (DoD)
applies to all PBIs
TRACKING PROGRESS
Burn-down charts
Burn-up charts
"PO manages the backlog, NOT the team"