Scrum Practice

 Organized step by step approach
 Manager oriented paradigm
 Pre planned work
 Requirements will be gathered at the beginning
of the process.
 Complete high level design before
implementation
 Complete documentation
 A successful approach for most of the
companies

 One of the Agile Methodologies.
 It’s a simplified iterative model.
 Time boxed work.
 Team friendly paradigm.
 Can start with minimal requirements.
 “Plan” for next sprint.
 “Design” only for the current sprint.
 Close interaction with developers and testers.
 Lock the Requirement for the current sprint.
 Client will get more interaction, to know the progress
of work.
 Allows you to change requirement at any point of time.

 Self organized teams
 Better coding practice
 Minimizes resource time wastage
 Easy to adapt changes
 Quick problem resolution
 Short term deliverables
 Client can see ROI
 Easy to trace the work progress

 Complete trust on team members
 Sprint planning for 1 – 4 weeks
 Allow team to decide what all stories they can
complete in the boxed time.
 Allow team to discuss on each story before actual
execution starts
 Respects all team members understanding
 Allows team member to share their road blocks
 Daily updates to know the work progress
 “Allows” you to “do” experiment
 Meetings are most important, participation is must

 Pigs
 Scrum Team
 Product owner
 Scrum master
 Sprint Team
 Chickens
 Stakeholders
 Clients
 Any End users or managers

 Holds the product back log
 Organizes all specification and simplifies them
to Story points
 Prioritizes all story points
 Conducts Sprint Planning
 Responsible for clarifying doubts
 Has to review sprint retrospective

 Key person for Scrum practice
 Has to involve all team members in Sprint planning
 Responsible for making team more interactive
 Responsible for conducting daily scrum meeting
 Holds the burn down chart to know the progress
 Has to resolve all internal team problems
 Has to respond to the team members when ever they
need help.
 Can be a team member.
 Shouldn’t allow other interference.
 Shouldn’t allow any one to change work after it got
planned.
 Can involve in Prioritizing story points

 Team size can be (5 – 9)
 Combination of developers and testers
 Team member can work on any task
 Has to attend daily scrum
 Has to update time left on his task at end of the
day
 Has to maintain good relationship with co-
team members

 Product Back log
 Holds complete specification details
 Product owner is responsible for reshuffling and
prioritizing
 Pending works from sprint will be placed here.
 Sprint Back log
 Holds current sprint story points and tasks
 Holds work left as of today with up to date values
 Burn Down chart
 Gives an idea about “how much work left in the sprint as
of today”
 It gives clear idea about team capacity

 Daily Scrum
 Sprint Planning
 Sprint Review
 Retrospective

 Standup meeting
 Not to exceed more than 15mins
 Everyone has to tell 3things
 What you have done yesterday
 What are you going to do today
 Any issues you faced in the implementation
 If the meeting requires more time to resolve problems then
separate meeting should be scheduled
 Has to respond to the team members when ever they need help.
 Can be a team member.
 Shouldn’t allow other interference.
 Shouldn’t allow any one to change work after it got planned.
 Can involve in Prioritizing story points
 Can add user stories to the product back log

 Team will play planning poker game to get
weightage of story points.
 Stories will be reviewed based on priority.
 Product owner will clarify if team has any doubts
or concerns on any story.
 Team available effort will be measured (4-6 hours
per day for a resource).
 Team will commit only on stories which has clear
understanding.
 Items that are going to work on in the next sprint
will be decided based on team comfort.

 Stakeholder and client will included along with
scrum team
 Team member will give a demo on what was
implemented in the last sprint
 All questions will be answered by scrum team.
 Transparent to every one.
 Missing/change in functionality items will be
listed and will be added to the product back
log.

 Scrum team will be participated in the meeting
 Team needs to come up with all problems that
were faced in the previous sprint
 Product owner will review those problems and
will come-up with solutions.
 Team can suggest if they need any changes to
the process

 No “Working for late hours”
 Abnormal termination
 When change in requirement has impact on current
running sprint then product owner has the right to
terminate current sprint and can propose for new sprint
plan
 Definition of “Done”
 Product owner has to define definition of task completed.
 Impediments
 Either source stopper or issues rose while implementing
 Running sprint cycle never get change.

Srinu Tamada

http://www.scrumalliance.org/profiles/95538-srinu-tamada

Scrum Practice

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Scrum Practice (20)

Scrum Practice