Agile Team Smells<br />Agile NCR 2010<br />Presented by <br />Anurag Shrivastava, MD,  Xebia IT Architects India Pvt. Ltd....
Context<br />Small company engaged in offshore software development using SCRUM and XP<br />Technically challenging assign...
Daily Stand-ups are Going OK<br />
Minor Problems with Quality Build<br />
Retrospective went fine<br />
Progress Charts are Little Old<br />
Do Not Need a Tester<br />
We pair well<br />
Team Feels No Need for Collocation<br />
Few Days In Between Sprints<br />
Fixes<br />Daily standup meetings must happen on time and every team member should be present<br />Make sure that a succes...
Fixes<br />Check if the team gets excited about the progress<br />Make sure that the team has a tester<br />Pair should be...
Thank you<br />
Upcoming SlideShare
Loading in …5
×

Agile Team Smells : Early Detection and Fixes by Anurag Shrivastava

860 views
800 views

Published on

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'.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
860
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Agile Team Smells : Early Detection and Fixes by Anurag Shrivastava

  1. 1. Agile Team Smells<br />Agile NCR 2010<br />Presented by <br />Anurag Shrivastava, MD, Xebia IT Architects India Pvt. Ltd.<br />and Founder of Agile NCR <br />
  2. 2. Context<br />Small company engaged in offshore software development using SCRUM and XP<br />Technically challenging assignments<br />Typical teams have 3 to 8 persons<br />Highly self-organizing culture<br />All team members are equal<br />High focus on software quality<br />
  3. 3. Daily Stand-ups are Going OK<br />
  4. 4. Minor Problems with Quality Build<br />
  5. 5. Retrospective went fine<br />
  6. 6. Progress Charts are Little Old<br />
  7. 7. Do Not Need a Tester<br />
  8. 8. We pair well<br />
  9. 9. Team Feels No Need for Collocation<br />
  10. 10. Few Days In Between Sprints<br />
  11. 11. Fixes<br />Daily standup meetings must happen on time and every team member should be present<br />Make sure that a successful quality build is one of the sprint success criteria<br />Make sure that recurring problems are not simply voted out and every team member feels engaged in the retro<br />
  12. 12. Fixes<br />Check if the team gets excited about the progress<br />Make sure that the team has a tester<br />Pair should be switched<br />Let team not worry about the costs<br />Make sure that Product Owner and Business are disciplined<br />
  13. 13. Thank you<br />

×