What is Scrum?
Scrum is framework of breaking down
complex problems into smaller and
simpler goals and executing to achieve
the goal in a “said” timebox.
Its empirical, timeboxed, iterative.
Work with small team size, 3 to 9 team
5 SCRUM values:
Scrum Team Attributes:
• Self Organising
• Cross functional
• Accountability as a
• Ideal size between 3 to
Scrum Master Attributes:
Scrum PO Attributes:
• Business Savvy
3 different roles in SCRUM:
Scrum Team, Scrum Master and Scrum Product Owner (PO).
Scrum Events & Artifacts
Atrifacts Product Backlog
What is team dynamics?
How team interact with one another?
How many people are there in team?
How each team mate play his/her role in the
How bonded the team is?
Does the team follow SCRUM ?
“Behavioral relationships between members of the team.
How they interact with one another when things are good
and when things go awry.”
Use Case 1:
Team is not
When team is not cross functional then there is
◦ Dependency on outside teams, Impact on the timeline, Sprints
◦ Motivational issues as the outside team mate may not be as
motivated as the team is
◦ They are working on a schedule much different from your team
◦ May not participate in Scrum activities and give and receive
Use Case 2:
PO is the Scrum master.
PO are focused on “WHY” of the product, bringing more
and more value to business, take up more and more
backlogs items. SM are focused “HOW” to build the
product, on team work, ensuring team consistency and
achieve a sustainable pace. When both are played by one
person, there is interleaving of scope and process which
tends towards locking scope, schedule and quality.
Use case 3:
No Demo at end of every sprint, No Retrospectives done,
Daily Standup not done
Sprint backlog not maintained
Team accept changes in middle of sprint, frequently
Product Backlog does not have clarity and PO is often
required to clarify
Use case 4:
Retrospective meeting is more like RCA finding meeting
Team mates avoid Retrospective meeting
Team mates defensive at the mention of Retrospective
Non ideal team size
Floating team members
Team inadequately staffed
Roles mix up
Scrum being partly followed
• Tying team success to the appraisals rather could be in addition
to the individual rating
• Focus on building cross functional teams
• Ensuring that team stays constant for a longer period of time
• Ensuring no roles mix up
• Bonding, teambuilding
• Following Scrum practices diligently
• Accountable for work undertaken