Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

"Scrum Master - The Team Spirit Guardian" : Presented by Vijay Bandaru


Published on

Lord Krishna was our first Scrum Master who helped "Pandavas" to win the "Kurukshetra" war without using a single weapon. On top of it, he was the almighty with so many invisible powers, but he still guided the "Pandavas" through his servant Leadership.

Inspired by this concept, I have created a session to highlight the role of a "Scrum Master" and how can we make a Scrum Master a true "Servant Leader" without so much depending on authority or tools rather concentrating on simple things that can make his contribution to the team a true differentiating factor.

Topics covered in the task:

- Understanding the team formation stages
- 5 dysfunctions of teams
- Gauge the team members' behaviours
- How a Scrum Master can make his team GREAT
- Soft skills for Scrum Master
- How a Scrum Master help his team in various situations
- Importance of learning for a Scrum Master
- Scrum Master's backlog for his team's improvements
- Scrum Masters checklist

Published in: Engineering
  • Be the first to comment

"Scrum Master - The Team Spirit Guardian" : Presented by Vijay Bandaru

  1. 1. … the “team spirit” guardian Scrum Master CSP, CSM, PMI-ACP, ITIL, PMP
  2. 2. 2 1. MYTH: The best Scrum Masters already worked as a Dev Team member 2. FACT: The ScrumMaster must have courage to do his job 3. MYTH: The best Scrum Masters already worked as Project Manager 4. MYTH: The Scrum Master is the most important role in a Scrum project 5. FACT: The Scrum Master must have good interpersonal skills 6. MYTH: The Scrum Master is one of the decision makers for the project schedule 7. MYTH: The Scrum Master and the Dev Team estimate the Product Backlog items 8. FACT: The Scrum Master must protect the Dev Team from external interference 9. MYTH: The Scrum Master usually cannot change the organization she works for 10. FACT: The Scrum Master is responsible for ensuring that Scrum is correctly used 11. MYTH: The Scrum Master must manage the work of the Dev Team 12. MYTH: The Scrum Master should be the single point of contact to the stakeholders 13. MYTH: The Scrum Master is the Project Leader 14. FACT: The Scrum Master does not have any authority but has responsibility 15. MYTH: The Scrum Master decides when to cancel a sprint Scrum Master Role – Myths & Facts
  3. 3. 3 Scrum Master Role – SHU – HA- RI Phases  Schedule Meetings  Team Assistant/Scribe  Daily 3 Questions  List Impediments  Moderate Meetings  Protect The Team  Diagnose  Remove Impediments  Team Interface  Assign Tasks  Decide Technical Issues  Evade conflict  Bossy  Talks Velocity, Timelines  Facilitate Meetings  Grow The Team  Progressively Delegates  Help Team Find Causes  Make Team Accountable  Teach F2F Communication  Encourage Collaboration  Constructive Conflicts  Trainer, Mentor, Coach  Cares About Motivation  Continuous Learner  Focus on Innovation  Change Agent  Agile Evangelist
  5. 5. 5Reference: Patrick Lencioni The 5 Dysfunctions of a Team
  6. 6. 6 Team’s Behavior
  7. 7. 7 ROOTS MUST BE STRONG AND HEALTHY Scrum Master Can Make The Teams “GREAT”
  8. 8. 8 Soft Skills Matter !!
  9. 9. 9 Nurturing Your Team1
  10. 10. 10 Nurturing Your Team2
  11. 11. 11 Nurturing Your Team3
  12. 12. 12 Ask yourself a question “how do I learn?” This is the starting point to become agile Tell me, I forget; Show me, I remember; involve me, I understand Curiosity is the first step for learning & ego is the first blocker Learning Pyramid with average retention Rate Learn & Make The Team Learn
  13. 13. 13 CROSS- FUNCTIONAL HIGH PERFORMANCE SELF ORGANIZED MOTIVATED 1. Encourage secondary skills 2. Arrange training 3. Encourage knowledge sharing 4. Dedicate x% of capacity for learning 5. Move people around 1. Introduce Pair programming 2. Start TDD 3. Introduce Refactoring 4. Start continuous integration 5. Aim for ZQC 1. Manage their own impediments 2. Time boxing 3. Innovative Inspect & Adapt 1. Team building activities 2. Select good metrics 3. Celebrate their success 4. ROWE Scrum Master Backlog
  14. 14. 14 Morale is a multiplier for Velocity An approach to success: Scrum Masters have to follow the below: Protect – When there are obstacles from outside Pride – For the good work done or when delivered great work Empower – The team Optimism – Process efficiency Celebrate success – To make the moments memorable Create happiness – Genuinely…. How we perform?How we feel? An Approach To Success
  15. 15. 15 Agile is built on RESPONSIBILITY at all levels of the ORGANIZATION  We as Scrum Masters, have to show the responsibility at our level  Let our teams also feel the responsibility by closely working with them by addressing their impediments and protect them and support them  Help the management understand the Agile and be agile  Bridge the gaps at all levels through information radiation  ….. How Can You Make The Difference?
  16. 16. 16 Summary Change Agent Empathy Healing Coaching Awareness Active Listening Persuasion Commitment Positive Attitude Communication Courage Patience
  17. 17. 17 Thank You +91-9848032144