Impetus webinar on ‘Managing Self-organizing SCRUM Teams’ available at http://bit.ly/ufarGs

1. Impetus Technologies Inc.
Managing Self-organizing
© 2014 1 Impetus Technologies
Scrum Teams
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52

2. Outline
• Self-organizing Scrum teams
• Building self-organizing teams
• Managing self-organizing teams
© 2014 2 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52

3. Self – organizing Scrum Teams
• Self-organizing, empowered teams
• Not directed and controlled from top
• Team participates actively & collectively in Scrum
© 2014 3 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52
practices
• More freedom vis-à-vis traditional development
• Difficult transition for leaders from non-Scrum projects
• The balancing act
• Freedom with reliable & predictable outcomes

4. The Need – Sharing and Learning
• Frequent interactions within the team
• Learning from peers and seniors
• Learning by observing and exposure
• Diverse backgrounds, experiences &
perspectives within the team
• Frequent interactions
• Team-bonding
• Identification with project commitments
© 2014 4 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52

5. Building Self – organizing Scrum Team
© 2014 5 Impetus Technologies

6. Inertia
Scrum says…
 Scrum’s roles, artefacts, events and rules are
immutable
Challenge
• Why should we change, old ways were good enough
Our Recommendations
• Explaining the benefits of following the rules
• Making them mandatory for all concerned
© 2014 6 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52

7. Personality Type
• Challenge
• Loner v/s team player
• Aggressive v/s submissive
• Our Recommendations
• Carefully choosing members while forming the team
• Avoiding extreme personality types
© 2014 7 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52
Scrum says…
 Common shared language

8. Personality Clashes
© 2014 8 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52
Scrum says…
 All team members are called Developers regardless of the nature of
work
 No sub-teams dedicated to particular domains, like testing
• Challenge
• Lack of bonding between members of different roles
• Old hierarchy can’t co-exist with new demands
• Our Recommendations
• Ensuring collective participation in all Scrum events
• Dismantling hierarchy appropriately

9. Geographically Dispersed Team
Scrum says…
Team is responsible for conducting daily Scrum for transforming backlog
items into next increment. Only team members can participate in this
meeting..
© 2014 9 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52
• Challenge
• Communication & collaboration bottlenecks
• Our Recommendations
• Virtual meeting facilities with high quality audio / video
• Encouraging informal interactions to develop team bonding

10. Multi – Organization Team
Scrum says…
 Product Owner is the only person accountable and responsible for
managing the product backlog..
© 2014 10 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52
• Challenge
• Product owner and team from diverse cultures
• Our Recommendations
• Encouraging openness & tolerance to diversity
• Product owner’s availability for the team
• Team leader as proxy-product owner

11. Managing Self - organizing Scrum
© 2014 11 Impetus Technologies
Team

12. Perceived Drop in Efficiency
© 2014 12 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52
Scrum says…
 Sprint plan is created by the collaborative work of entire team
• Challenge
• Parallel working discouraged
• Results in reduced utilization of resources
• Our Recommendations
• Using enhanced learning to avoid rework & delays
• Encouraging team to take proactive decisions and actions

13. Measurement & Reporting
Scrum says…
 The work remaining and date are the only variables of interest
 Development team tracks the work remaining in daily scrum
© 2014 13 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52
Challenge
External stakeholder’s discomfort in letting go of old channels
Our Recommendations
Intermediate deliverables with in the sprint
Leveraging the enhanced visibility & transparency
Using daily updated sprint backlog for latest information

14. Team Accountability
© 2014 14 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52
Scrum says…
 Selection of product backlog for the sprint is solely up to the
development team
• Challenge
• No single person accountable
• Our Recommendations
• Team delivers
• Team members can hold each other accountable
• Team identifies the weakest link

15. Loss of Control over Team
© 2014 15 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52
Scrum says…
 Self-organizing teams choose the best way to work
• Challenge
• External stakeholders feel loss of control over the team
• Our Recommendations
• Identifying risks in sprint backlog and daily updates
• Determining quality & velocity improvements
• Intermediate review with Product Owner

16. Introducing Changes During Sprint
© 2014 16 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52
Scrum says…
 Development Team must only consider the priorities given by product owner and
no one else
 After planning Scrum, the team crafts a sprint goal which gives some flexibility
regarding implemented functionalities
• Challenge
• Inability to introduce changes as and when they come up
• Our Recommendations
• Avoiding intervention once the sprint commences
• Changes to be made only if they help sprint goal

17. The Big Shift
© 2014 17 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52
Scrum says…
 Scrum Master is the servant-leader for Scrum Team
• Challenges
• Scrum master has to earn respect by serving team
• Others need to accept and adjust to his new role
• Our Recommendations
• Choosing Scrum Master carefully
• Scrum Master to focus on serving product owner, team and
organization

18. Summary
• Scrum creates challenges but also provides solutions
• Self-organization is challenging yet highly rewarding
• Boundaries are demolished and team bonding encouraged
• Far greater autonomy as well as responsibility
• Distributed & multi-organization teams have greater challenges
• Scrum Master is the biggest change manager
Building self-organized team is a tough job,
© 2014 18 Impetus Technologies
Sustaining it is tougher!
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52

19. © 2014 19 Impetus Technologies
About Impetus

20. • Strategic partners for software product engineering and
R&D
• Thought leaders in cutting-edge technologies
• Mature processes and practices that are methodical, yet
flexible
• Diverse domain expertise
© 2014 20 Impetus Technologies
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52

21. © 2014 21 Impetus Technologies
Q & A

22. © 2014 22 Impetus Technologies
Thank You
Write to us at inquiry@impetus.com
Follow us on Twitter @impetustech
Recorded version available at
http://www.impetus.com/webinar_registration?event=archived&eid=52