Scrum Flashcards
Scrum overview
1) Rigid
2) Roles and responsibilities
3) Strategic meetings
4) Sprint events
5) Artifacts
Scrum vs Waterfall
1) defined scope vs changing scope
2) well defined req vs changing requirements
3) reliable estimation vs not all activities known /non estimateable
4) Linear vs iterative
5) scope /budget vs value
scrum 3 pillars
1) visibility
2) inspection
3) adaptation
Scrum structure
1) Well defined roles
2) fixed time boxes
3) at least 5, no more than 9
4) strict enforcement
6) burndown chart updated after every scrum meeting
Pigs and chicken
1) Chicken is involved but pig is committed
2) rooster - unproductive
Product owner responsibilities
1) Determines features, release date, prioritization,budget
2) protect team members from distraction
Development team
1) membership should only change between the sprints
2) Cross functional (everything can be done without outside help)
3) Create definition of done
Scrum master
1) Usually project manager or project leader
2) enacting scrum values and practices
3) remove impediments, politics, keep team productive
4) foster close cooperation
Servant leadership
1) Delegates
2) Supports initiative
3) Emerges from anywhere (power)
4) accesses power for the interest of the team
5) gives credits to others and takes blame
Scrum events
1) Strategy meeting
2) Release planning
3) Sprint planning
4) Sprint review
5) Sprint retrospective
6) Daily scrum
Strategy meeting attendeess
1) product owner(lead and facilitate)
2) stakeholder
3) scrum master
4) project manager
Strategy meeting steps
1) Create product vision statement
2) Create initial epic user stories
3) Create initial detailed user stories
4) Prioritization
5) Create initial product road map
6) Create initial product backlog
Release planning overview
1) Plan the specific release (deliver cycle)
2) Plan which features will be included
3) Prioritization for each release
4) Create initial high level estimates for features
Release meeting attendeess
1) product owner(lead and facilitate)
2) stakeholder
3) scrum master
4) project manager
5) Development team members
Release planning guidelines
1) 4 to 8 hours
2) PO creates agenda, leads, establishes the ground rules, documents output
3) Conducted periodically based on agreed upon release dates
Release planning steps
1) Review product vision (PO)
2) Review key dates and milestones (PO)
3) Present product backlog (PO)
4) Dev team asks questions
5) Relative estimation
6) determine sprint length
7) release theme
8) Create release product backlog
9) stakeholder consensus
10) PO commitment
Sprint planning overview
1) backlog items to be completed
2) detailed task for the backlog item
3) identify acceptance criteria according to the definition of done
Sprint planning guidelines
1) 2 hours for every week of sprint
2) PO creates agenda
Sprint planning steps(1)
1) Discuss sprint goal(PO)
2) Present user stories (PO)
3) estimation (planning poker - more specific level than relative size)
Sprint planning steps(2)
1) Define and assign tasks
2) review workload and determine feasibility
3) agreement
4) PO decides what will be included
Sprint review
1) ensure product acceptance criteria met
2) demo
3) process feedback
4) outline expected functionality in next sprint
Sprint review potential roadblocks
1) Not showing actual functionality
2) attempting to include last minute functionality
3) PO may not accept certain functionality
4) Functionality may have worked, but not anymore
Sprint review guidelines
1) 1 to 2 hours
2) invite all
3) why demo did not happen and when will happen
Sprint review steps
1) PO present release goal, sprint goal, and new features
2) demo by team members
3) Field questions
4) PO formally accepts and close the sprint
Sprint retrospective
1) 1 to 3 hours
2) 45 minutes for each week of sprint
3) evaluate what done correctly, what can be approved next
4) Plan for improvement and potential roadblocks
5) Only to the Scrum team
Sprint retrospective roadblocks
1) ganging up on individual team member
2) individual or process external team are blamed
3) may be facilitator for conflict resolution
Sprint retrospective steps
1) What went well
2) what did not go well
3) improvement for negative items
4) determine next sprint roadblocks
Daily scrum attendees
everybody involved in the project
Daily scrum guidelines
1) Daily 15 minutes, same place same time
2) scrum team members must attend
Daily scrum steps
1) What accomplished from last meeting
2) what will be working today
3) What roadblock in your way
4) log parking lot issues and take it offline
Scrum staging
The process of defining and prioritizing the nonfunctional requirements for scaling is called staging. Staging occurs prior to the start of the first Sprint and takes just one day. During this day, the nonfunctional scaling requirements for this particular project are determined and placed in the Product Backlog.
three level of listening
Level I – Internal Listening - Listening to our own thoughts and judgements
Level II – Focused Listening - Focus on what the client is saying
Level III – Global Listening - Listening focus is on more than just the words
