3. Agenda KBB Background Five Dysfunctions of a Team Starting Small Growing the Teams Hyderabad, India Beijing, China Learnings Q & A 3
4. Background KBB has been working with Scrum since 2005 Began expansion to all development teams in 2007 Moderate Scrum experience level Currently 18 teams/200 users 5 Dysfunctions of Team introduced in 2006 Primary development efforts KBB.com Dealer Products Some internal tools and systems
5. The Five Dysfunctions of a Team Inattention to Results Avoidance of Accountability Lack of Commitment Fear of Conflict Absence of Trust The Five Dysfunctions of a Team By Patrick Lencioni
6. The Five Dysfunctions of a Team Inattention to Results Avoidance of Accountability Lack of Commitment Fear of Conflict Absence of Trust Avoidance of Accountability The need to avoid interpersonal discomfort prevents team members from holding one another accountable for their behaviors and performance. Absence of Trust The fear of being vulnerable with team members prevents the building of trust within the team. Inattention to Results The pursuit of individual goals and personal status erodes the focus on collective success. Lack of Commitment The lack of clarity or buy-in prevents team members from making decisions they will stick to. Fear of Conflict The desire to preserve artificial harmony stifles the occurrence of productive, ideological conflict.
7.
8. Each person on the team “answers” 3 questions for the team
39. On-shore Team travelled to India to re-introduce Scrum and the Five Dysfunctions of a Team model
40.
41.
42. Beijing Team – Adjusting (调节) Changed the focus of work to site optimization, UI compliance, testing automation More frequent exchanges and longer stays Technical standards Scrum Training 5 Dysfunctions reinforcement Stories are more well-written and clear Vendor is providing English language training after hours to continually improve skills
43. Beijing Team - Adjusting Resulted in: Getting issues out faster during calls or SharePoint discussion boards All team members now feeling like they can provide input at Planning Meetings, Daily Scrums, Reviews and Retrospectives Better team deliverables and velocity Beijing team members want to work on KBB teams
44. Additional Team Building Discoveries Vendors wanted to please the client Off-shore teams didn’t reveal issues quickly enough and resulted in poor daily Scrum and retrospective meetings None of the off-shore team members had ever had direct contact with the client before; this structure was new to them, and therefore the leads ending up being the spokes person for the team Continual reinforcement of Scrum principles and 5Ds is necessary for everyone - on-shore and off-shore teams We had to make sure company values and attitude toward Scrum and 5Ds were embraced Support of off-shore takes time and it is important to make sure the time is allocated!
45. Final Thoughts We’re a small technology shop We are focused on making every interaction as effective as possible. Off-shore teams need to understand KBB culture and what is important to us Its more than Client – Vendor relationship. It is an extension of an on-shore team. We make adjustments all the time and will continue to do so.
First learning’s.Not following system architectureNot reusing existing components Not following coding standards
First learning’s.Not following system architectureNot reusing existing components Not following coding standards
China Team projects – small enhancement to internal for content management on KBB.com – editorial tool, meta tag management tools, etc. so updates can be deployed quickly to the Web site by internal departmental usersThe Learnings.Not following system architectureNot reusing existing componentsNot following coding standards (naming conventions, code commenting, etc.)Things worked but didn’t look pretty under the covers.
For the India team, as a next step we paired them up with an equal sized onshore team to work on retiring a KBB CD dealer product by enhancing an existing web application. Significant work, since the web app was supporting over 20k users.The processes that we followed evolved over time. Initially we setup weekly code reviews to address the technology finding from the previous work. However, assigning interdependent stories to the two teams turned out to be key to the quality of the code.Both teams used a common development environment, and Some basic processSolid results meeting both business and technical expectations!A 7 month with 5 onshore resources project was completed in 3 months by the combined team.
Fibonacci scalePlanning poker.Its hard to get convinced that the right points are allocated to stories when all cards are upside down.
Without trust you can’t engage to healthy conflict. After going through the 5 D’s training the board got full.Only took about 10 minutes to get all of the retrospective items on the board, there was no hesitation by the team members to share their thoughts in the retrospective.