Why swarmg is important to getting to DONE

202
-1

Published on

A team I worked with a while back had this problem...heck most new teams have this problem.
In this ppt learn not just HOW to fix/avoid this problem, but WHY!

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
202
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Why swarmg is important to getting to DONE

  1. 1.  Test is idle… then Dev is idle  Lots of bugs toward the end  Multiple Cary Over Stories
  2. 2.  Many stories get started early  They complete all about the same time  They complete about mid or late sprint  Leaving things un-started is uncomfortable  Individual ownership of code/stories  Starting things just feels good
  3. 3. Three good reasons to swarm 1. Impact on testing 2. Ability to burn up 3. Delivering Value
  4. 4.  Testing Crunched  Erratic flow  Idle people  Bugs all at the end  Reduces likelihood of Done Done
  5. 5. We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more
  6. 6.  Testing throughout  Even flow  Better use of people  More time for defect fixes
  7. 7. No Swarming With Swarming  Testing Crunched  Erratic flow  Idle people  Bugs all at the end  Reduces likelihood of Done Done  Testing throughout  Even flow  Better use of people  More time for bugs  MORE likely to reach Done Done
  8. 8.  Messes with burn down and burn up  If all the stories complete dev mid sprint then all the stories start getting bugs mid sprint thus messing with burn down  Which is more valuable?  10 stories 80% done  8 stories 100% done and 2 not started
  9. 9. story Code Test Fix story Test Code Fix
  10. 10.  2 Types of Testing  Attempting to FIND defects  Attempting to PREVENT Defects  Cuts Rework by 60% to 20%  Acceptance testing is about Understanding Requirements Per-Function Cross Function Business Function Acceptance Usability Component Exploratory Technology Unit Property
  11. 11. System State Action Final System State Setup Given Trigger When Assert Then
  12. 12. Stories & Experience Thoughts Beliefs Actions RESULTS

×