SCRUM

Question 1

What is SCRUM

Answer 1

PM process
lightweight dev process to manage and control software development 
embraces iterative and incremental practices
not artefact driven
no large requirements documents
results oriented
commitment oriented
disciplined

Question 2

commitment oriented meaning

Answer 2

commitment through ownership and team centric values that build commitment

Question 3

results oriented meaning

Answer 3

focus on what the game is every month rather than where you are in a schedulle

Question 4

what does it mean that scrum is disciplined

Answer 4

specific practices that are simple and must be followed

Question 5

three scrum roles

Answer 5

product owner
scrum master
team

Question 6

scrum pig

Answer 6

players, committed, accountable, responsible

Question 7

scrum chicken

Answer 7

spectators, interested, consults, informed - management

Question 8

what is the scrum product owner

Answer 8

represents the interest of everyone with a stake in the project and its resulting system
achieves initial and ongoing funding
creates: release planes, ROI objectives, initial overall requirements

Question 9

Product backlog

Answer 9

list of requirements

Question 10

relationship between product owner and product backlog

Answer 10

owner uses backlog to ensuer the most valuable functionality is produced first and built upon
- achieved by frequently prioritising the backlog queue uo the most valuable requirements for the next iteration

Question 11

what is the scrum team

Answer 11

10 or fewer
responsible for developing functionality
self-managing, self-organizing and cross functional\responsible for deciding on how to tyrn backlog into an increment of functionality with the next iteration
managing own work to do the above
all members are responsible for the success of each iteration and the project as a whole

Question 12

what is the scum master

Answer 12

responsible for the scrum process
teaching scrum to everyone involved
implementing scrum properly
ensuring that everyone follows the scrum rules and practices

Question 13

what does it mean to empower the pigs and remove the chickens

Answer 13

empower the people who make personal commitment to the success of the project and remove the people who dont

Question 14

how to go about changing scrum rules

Answer 14

change should originare from the team and not management
changes should only be entertained if the scrum master is convinced everyone understands how scrum works
no rule changes until scrum master determines that the above stage has been reached

Question 15

describe the scrum flow

Answer 15

any project starts with a vision
product owner produces product backlog
work is done in sprints
- iteration of 30 consecutive calendar days
- initiated with sprint planning meeting
goal is to get to work not to think a bout working

Question 16

sprint planning meeting

Answer 16

product owner and team collaborate about what will be done for the next sprint
selecting from the highest priority product backlog
owner tells team what is desired
team tells owner how much it believes it can turn into functionality over the next sprint
cannot last longer than 8 hours
prevent handwringing about what is possible

Question 17

sprint planning meeting inputs, outputs, players

Answer 17

inputs - backlog, team capabilities, business conditions, tech, current product
players - owner, team, scrum master, management, customers
outputs - sprint goals

Question 18

Sprint planning meeting timing

Answer 18

time boxed to 8 hours

each of two segments time boxed to 4 hours each

Question 19

first segment of sprint planning meeting

Answer 19

selecting product backlog that it believes it can commit to turning into an increment of potentially shippable product functionality - will demonstrate this at the end of sprint at the sprint review meeting

Question 20

second segment of sprint planning meetings

Answer 20

preparing a sprint backlog

Question 21

what to do in the first 4 hours of sprint planning meeting

Answer 21

owner presents highest priority backlog to the team
team questions stuff about the backlog
team selects as much of backlog as it believes it can turn into working product by end of sprint

Question 22

what to do in the second 4 hours of sprint planning meeting

Answer 22

planning the sprint
team is responsible for managing its own work
- plan needed to start the sprint
- chosen tasks are placed in sprint backlog
- these tasks emerge as the sprint evolves
owner answers questions from the team
team works out how to turn selected backlog into an increment of potentially shippable product functionality
output - sprint backlog: tasks, task estimates and assingments

Question 23

Daily scrum meeting

Answer 23

time boxed to 15 minutes
held in the same place and time everyday - best done first thing in the day so members think of what they’ve done the day before and what they plan to do today
all team members required to attend
punctuality is very important

Question 24

how does the daily scrum meeting work/what unfolds

Answer 24

scrum master goes around room until everyone has reported

each team member responds to only 3 question: what have you done? what will you do? what stands in the way?

Question 25

purpose of daily scrum meeting

Answer 25

synchronize the work of all team members daily

schedule any meetings needed to help progress

Question 26

Chickens role in scrum meetings

Answer 26

not allowed to talk etc
stand on periphery
limited attendance of chickens
not allowed to talk to team members after meeting
non-conformance to rules: excluded from meeting or removed from the team

Question 27

what is a sprint

Answer 27

time-boxed to 30 days
time needed for team to build something of signiificant i interest to the owner and stakeholders and bring it to state where it could possibly be shipped
max time to do work without artefacts and documentation to support thought process
maximum time stakeholders will wait

Question 28

what happens to the backlog during a sprint

Answer 28

remains frozen until end of sprint

no one is allowed to change it

Question 29

team unable to complete all the committed backlog

Answer 29

consult owner in which items to remove

if so many items require removal that sprint has lost value - scrum master can terminate the sprint

Question 30

team can address more backlog

Answer 30

consult owner on which additional backlog items to add

Question 31

team responsibilities during a sprint

Answer 31

attend daily scrum meeting

keep the sprint back log up to date and available for public access

Question 32

what is the sprint review meeting

Answer 32

4 hours
team should not spend more than 1 hour prepping
present functionality to owner and other stakeholders
don’t present what is not done
present functionality on team work stations
start with presenting spring goal, backlog committed to and the backlog completed
get stakeholder questions and impressions

Question 33

sprint retrospective meeting

Answer 33

3 hours
attended only by team, master and optionally by the product owner
- what went well during last sprint
- improvements in next sprint?
scrum master  summarizes

Question 34

scrum process overview

Answer 34

product backlog
sprint backlog
30 day sprint - looped daily scrum
sprint review

Question 35

scrum artefacts

Answer 35

product backlog
sprint backlog
burn down chart

Question 36

burn down charts

Answer 36

used to identify the rate at which the work is being completed
graphical representation of sprint backlog
illustrates the work done
demonstrate steady drive to zero hours remaining

Question 37

reasons for too work being done too slow

Answer 37

inexperienced devs
challenges that cannot be overcome
distractions
holidays
bad planning

Question 38

what can go wrong with scrum

Answer 38

Loss of rhythm - sprints not always the same length
talking chickens
missing pigs
specialized job roles - each specialist must accept general responsibility for the system as a whole
daily scrum is for the scrum master
scrum master assigns work