the one-story-sprint

Taskular Testing

who am i?

‘’the guy that thinks there’s

always room for improvement.’’ -Dean Bodart

@DeanBodart

Dean Bodart

Topics

1. the average epic

2. multiple stories

3. bad management

4. counter attacks

5. results & bp’s

are not productive

Average Epics

• big, chunky & messy

• unclear acc. criteria

• not always coherent

• hardly maintainable

• needs to be split up!

make work easier

Multiple Stories

• small, tangible & clear

• easy to maintain

• more visibility

• the ‘’too-complex-look’’

will destroy results

Bad Management

• splitting takes to much time?

• to much stories?

• low visibility?

• bad agile

do it for the team

Counter Attack

1. are you the only tester?

never go at it alone.

2. are there multiple testers?

leave no one behind.

pair up, a lot.

manage tasks yourself

Ignore Management

3. divide story in logical parts

like a writer.

4. create corresponding tasks

for each part.

5. do not re-estimate the story

it’s an estimation.

6. discuss tasks with a’s and d’s

it creates insight.

7. create a seperate taskboard

to track your business.

value to completion Daily tasks Scrum

8. Additional private stand-up

before the official one.

• only test-team

• explain ongoing

• express concerns

• define impediments

• move break points

to cover the team Build a Buffer

9. limit work in progress

one task at the time.

10. have an expedite lane

for urgent & unexpected work.

check & correct Do Reviews

11. review e.o. test cases

never your own.

• reviewers be critical

• creators endure critics

• test the tests

• create a solid coverage

12. blend into the real sprint

subtle & with ease.

summary.

iteration

1 .

2 .

tasks

review work

work more

efficient

3 .

because quality matters.

click here

get the full ebook for free