OPPORTUNITY FOR

IMPROVEMENT

OPPORTUNITY FOR IMPROVEMENT

Test is idle… then Dev is idle Lots of bugs toward the end Multiple Cary Over Stories

WHAT IS THE PATTERN? Many stories get started early They complete all about the same time They complete about mid or late sprint

WHY IS THE PATTERN? Leaving things un-started is uncomfortable Individual ownership of code/stories Starting things just feels good

ONE ANSWER…SWARMING Three good reasons to swarm

1. Impact on testing2. Ability to burn up3. Delivering Value

IMPACT ON TESTING Testing

Crunched Erratic flow Idle people Bugs all at the

end Reduces

likelihood of Done Done

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 toolsWorking software over

comprehensive documentationCustomer collaboration over

contract negotiationResponding to change over

following a planThat is, while there is value in the items on

the right, we value the items on the left more

MANIFESTO FOR AGILE SOFTWARE DEVELOPMENT

IMPACT ON TESTING Testing throughout Even flow Better use of

people More time for

defect fixes

IMPACT ON PEOPLE AND WORK

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

OTHER IMPACTS 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% done8 stories 100% done and 2 not started

MOVING TEST UP

story

Code Test Fix

story Test Cod

e Fix

MOVING TESTING UP 2 Types of Testing

Attempting to FIND defectsAttempting 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

DEFINING USING EXAMPLES

System State Action

Final System State

SetupGiven

TriggerWhen

AssertThen

HOW CULTURE IS FORMED

Stories &Experience

Thoughts

Beliefs

ActionsRESULTS

Reinforcing Loop