Agile Team Smells : Early Detection and Fixes by Anurag Shrivastava

Post on 10-May-2015

710 views 0 download

Tags:

description

AgileNCR 2010 conference was held in Gurgaon on 17th & 18th July 2010. This largest community driven conference was the Fourth edition of Agile NCR and was organized in collaboration with ASCI. This time the event was based on four major themes : 'Agile for newbies', ' Agile Adoption Challenges', 'Workshops and Software Craftsmanship', and ' Post Agile'.

transcript

Agile Team Smells

Agile NCR 2010

Presented by

Anurag Shrivastava, MD, Xebia IT Architects India Pvt. Ltd. and Founder of Agile NCR

Context

• Small company engaged in offshore software development using SCRUM and XP

• Technically challenging assignments• Typical teams have 3 to 8 persons• Highly self-organizing culture• All team members are equal• High focus on software quality

Daily Stand-ups are Going OK

Minor Problems with Quality Build

Retrospective went fine

Progress Charts are Little Old

Do Not Need a Tester

We pair well

Team Feels No Need for Collocation

Few Days In Between Sprints

Fixes

• Daily standup meetings must happen on time and every team member should be present

• Make sure that a successful quality build is one of the sprint success criteria

• Make sure that recurring problems are not simply voted out and every team member feels engaged in the retro

Fixes

• Check if the team gets excited about the progress

• Make sure that the team has a tester• Pair should be switched• Let team not worry about the costs• Make sure that Product Owner and Business

are disciplined

Thank you