Pakistan Agile education Lahore chapter Meetup. Scrum values Importance and real-world scenarios where they can be practiced and applicable. No matter how hard scrum is to master yet If you master scrum values you can master scrum.

1. Master Scrum through Scrum Values
Sobia Sheikh

2. Values
1. Define you
2. Your Goal
3. Decisions
4. Direction
values

3. 1

4. Scrum is build on developing FOCUS
SM Keep Development TEAM
Focused
By removing obstacles or external
interference
Dev Team - Focused on
Developing Product of high
quality while being
productive and creative
PO - Focus on Product . Responsible for
developing product that is valuable

5. Focus (where in Scrum)
● Sprint Goal (PO -> product value)
● Daily SCRUM (Dev Team -> goal)
● Sprint backlog ( PBI -> goal)
● Sprint Planning ( -> Professional)
● Sprint Review ( Release ->valuable Product)
● Cross Functional Team ( -> Self Organized )
● Retrospective - Feedback to focus on improvement.

6. Focus (how many of you distract from plan)
What to Focus What not to focus
Valuable Product Delivering signed Requirement
Professionalism
● no extra hours
● realistic estimation
● Quality
● Productivity
● creativity
● Meeting estimated efforts
● Excelling techniques than product
Growth and Adaptability Make Project Manager happy

7. 2

8. Openness (what if)
1. A developer working on backend procedure knew performance issue but to
save his credibility; keep on struggling to fix while taking next task. On Review
the process stuck and sprint failed
2. A developer discovered his SBI require further tasks to perform and need
testing on multiple devices. He overlooked in planning
3. A PO with tech background suggest a different approach at planning
4. A change in dod, code refactor may affect prev functionality yet something
required to ship

9. Openness
Where in SCRUM
Sprint Planning Story Points : Why there is difference of number (task)
PBI- Detail : Any ambiguity
DoD - Team Sync at Done
Daily Scrum Highlight any impediment toward goal
Realistic about your task discovery and estimate
Sprint Review To get Feedback
Retrospective Team assessment, areas to improve, adapt

10. Openness (Challenges: credibility, Stand out from)
Open about What not
Impediments Impediments not Dev Team Secret
Would not raise question on credibility
Progress towards goal
(Daily Scrum)
Justifying delay
Everything going good (How champion we are)
Story Points (why differ) Why we need to discuss our task detail with Non tech ppl
Realistic effort / estimate Keep your safe side
Be Hero ( more work in less hour)
Feedback & adapt Justifying requirement

11. 3
Courage

12. Courage
1. Development team failed to achieve sprint goal. Last moment issue arose and
they have nothing to show in Review. What to do?
2. Quality defines Dev Team. And being Code geek, Tech Debt is hurting
3. Commitment is dragging towards extra hours and week days
4. Product owner asking Dev team why story point is not reflecting the velocity
in review

13. Courage (Challenges: Job Security, Hurting Ego or Org Standards)
1. Take responsibility of an adaptive complex problem
2. Tell we are in trouble
3. Change design or trying new things
4. Ask feedback on incomplete work
5. Take on org impediments or trying to change the organization rules
6. Prioritize different stakeholder requirement
7. Not let Stakeholders to dominate Dev Team
Require Courage to

14. Courage
Share your stories of courage
What Practices are common in your Org-Culture that require courage for real
implementation of SCRUM

15. 4

16. Respect (Challenges: Accepting team Autonomy)
1. In Sprint Planning, Some Non-Tech members or new employee comes up with
a very low or high Story Points.
2. Dev team could not deliver value at the end of Sprint
3. Stakeholders questioning the pre estimate and credibility of dev team
4. A new member in Dev team taking more time in developing a card
5. Your team member stuck in a pre req task and so you are waiting
6. You reserve sharing your domain or tech expertise doubting on the ability of
other person
7. A member takes time to capture or thrive in a field

17. Respect
Stakeholders and External
forces
Respect Autonomy of Dev Team. Empowering and directing them to
focus on mastery and purpose of goal -> eventually lead to
self org expert team and valuable product
Product owner Respect team’s ability to deliver
Sprint Review Respect change of direction, even failure while crediting the lesson
learnt to move further
Retrospective Respect people intent
Cross Functional Team Respect the diversity and exposure of different members

18. 5

19. Commitment
Scrum is all about commitment towards
1. Scrum values
2. Building Self Organized team
3. A team that is professional when comes to quality and growth
4. A team that doesn’t compromise on its personal life while committing to the
Sprint Goal or Job
5. Developing product that deliver value and is sustainable with the time and
new challenges

20. Few Challenges to adopt Scrum:
Resistance to Change by Stakeholders
Leadership refusing to get Agile coaching
Project instead of Products
Treating the Product Backlog like a Project Plan.