Please enable JavaScript.
Coggle requires JavaScript to display documents.
SCRUM - project cycle phases - Coggle Diagram
SCRUM - project cycle phases
not officially in the scrum guide
pre-game
phase activities
planning
product owner
develop the backlog
will continue to be updated
and merged during the project
prioritized requirements
functionalities will be determined by
developers not by product owner
identifies required release dates
a requirement is expressed in the form
of user story
ideal will take 10 days to develop
split in more functional parts
if too big
a user story may combine more
requirements
AS role I NEED TO the goal SO THAT
the business goal to be achieved
priority defined by
customer priority
high level of risk
es. functionality never
developed before
identifies most important
product requirements
with the help of the customer
decisions what market demand
what customer belivies will provide
most value
should descrive a functionality
if product exisitng then requirements are
based on needed updates
if product not exists
need organize meetings with
customer representative to gather
requirements
define the project's goal
initially some of the details
might not be perfectly clear
product owner responsability is to
provide to dev team a
well-defined, comprehnesive product goal
needs to reflect the vision
meet a business need
maximize ROI
details can be refined as the project progresses
features
functionalities
works on the overall budget
identifies risk control measures
ensure required resources
and tools
development of the
product high level design
product owner
has compiled project requirements
development team
review the complete
product backlog
create a basic
product design
analysis may be performed
es. evaluate impact
on existing systems
es. evalutate available
technololgies
es. evalutate changes needed
to implement backlog items
backlog revision
no key items are missing
clear on all the items
stories are arranged correctly
estimate development
es. use cards
identifies
deliverables
assign to different
development periods
or sprints
just an estimate
by the scrum book
sprint length is 30 days
create at least one functioning
deliverable per sprint
divides requirements
into increments deliverable
work
game
development team
plans each sprint, the goal
is develop a sprint backlog
develop a sprint backlog
through feedback received
from previous sprint
determines the tasks that need to
be completed
a task should last from 2 hrs to 2 days
estimate the tasks to complete
discuss the options with the product owner
sprint planning meeting
at the start of each sprint
product owner identifiy which
requirements
formulate a sprint goal
the deliverable that will be produced at
the end of the sprint
determine how best to build
the various product deliverables
completition criteria is
always a delivrable fully tested and
ready to be used by the customer
time boxed meeting
to not exceed 2 hours
ongoing testing
"backlog grooming"
made by the product owner and the team
clarify and evalutate
product backlog items
items may be
reordered,
added
removed
split
combined
unit testing
routine inspections
for testing product components
accuracy
reliability
functionalities
team can fix defects immediatly
tests helps on code refactoring
make the product
simpler and faster
daily standup meeting
task completed last 24hrs
issues that prevent task
to be completed
goal
quick update on proj status
identify any roadblocks
high level collaboration
quinck decision making
when
16 minutes time boxed
at the start of the working day
task planned next 24hrs
sprint review meeting
also interested stakeholders
may attend
dev team presents the results
of the sprint to the prod owner and
to the customer
let product owner and scrum master
gather feedback
in order to improve
customer value
owned by scrum scrum master
limit the prearation time
for each sprint review to 30min
repeat the sprint goal at the
start of the meeting
show the product backlog
the duration can be from 10min to 2hrs,
depends on time needed for feedbacks
sprint retrospective
after sprint review
owned by scrum master with
development team
discuss
how the sprint went and how
it could have been improved
helps the team formulate
best practices
identify tasks in the sprint
backlog that weren' t completed
the duration depends on
the sprint duration
es. sprint 30days, retrospective
should last no more then 3 hours
post-game
work needed
after a sprint or series of sprint
release a visible
product increment
the customer may chose to release
the latest developed functionaliy after each sprint
product may be release at specific release intervals
after a series of sprint
entire product backlog needs to be delivered
before the final product is released
scrum development demands that at the end of each
sprint a function product can be handed over to the customer
in theory each sprint
release a function product
no post-game phase are requrested
as the product should be deployed and
ready to be used by the custmer
in reality some sprints
could have no product
deployed
es. documentation
before closing
es. database tests
es. integration tests