Succeeding in Agile Testing

1
(No Transcript)
2
Succeeding in Agile Testing

• by Petter Skerfving
• petter_at_testway.se

3
Agile development methodologies are becoming
commodity
4
but what happened to testing?
5
Many Agile projects are not living up to the hype
6
The full potential of Agile, unleashed
7
Three key aspects of software greatness
Technology
People
Process
8
Three key aspects of software greatness
People
9
Keeping the mind sets separate
People
10
Testers are good at keeping an overview
People
11
Good testers are failure oriented
People
12
Sharpen your TDD
People
MBUnit
JUnit
xUnit
DBUnit
CppUnit
NUnit
13
Bringing the skill sets together
People
14
Testers need to understand what the code is doing
People
main() printf("hello, world")
15
Strong focus on test automation
People
16
Testers need to know the environments
People
17
We all need to earn respect
People
18
Combining testing with other responsibilities on
the team
People
19
Summary People
Technology
People
Process

• Keep mind sets separated
• Bring skill sets together
• Respect others contributions

20
Three key aspects of software greatness
Process
21
Agile team truly integrated team
Process
22
Extend the definition of done! It is a team
commitment!
Process
IM DOOONE!!!
Well, not quite, are you?
23
Do not delay testing to the next sprint! It will
split your team
Process
Development
Test
Sprint 1
Development
Test
Sprint 2
Development
Test
Sprint 3
Time
24
Parallel workflows for development and testing
Process
Development
Planning
Dev UT
Make AT run
Dev UT
Manual tests
Test
Design AT
Introduce
Issues
Integration
25
No more defending the customers from the evil
developers
Process
26
Manual Testing ET SBTM
Process
27
The tool set
Process
28
Extending the definition of done with test
automation
Process
29
Tools are also a team thing
Process
30
Tools that provide a secondary value
Process
31
Summary Processes
Technology
People
Process

• The team is one
• Align the arrows!
• Matching tool set
• Extend the definition of done

32
Three key aspects of software greatness
Technology
33
Technology
Technology
34
Summing it up

• Your product will have to change

Technology

• People
• Keep mind sets separated
• Bring skill sets together
• Respect others contributions

• Process
• The team is one
• Align the arrows!
• Matching tool set
• Extend the definition of done

• Technology
• Your product will have to change

People
Process

• The team is one
• Align the arrows!
• Matching tool set
• Extend the definition of done

• Keep mind sets separated
• Bring skill sets together
• Respect others contributions

35
(No Transcript)
36
Scrum Principles

• Small team of 7 people (/- 2)
• Short interations Sprints
• Deliverable product in every after every
  iteration. Delivers Business Value!
• Cross-functional team!
• Team commits to sprint goals!

37
The Scrum Cycle
Daily Scrum
Sprint
Sprint Review
SPM
Retrospect
38
Scrum roles and artifacts

• Roles
• Product Owner
• Scrum Master
• Team

• Artifacts
• Product Backlog
• Sprint Backlog
• Increment
• Burndown Chart

39
Tools that provide a secondary value
Team A
Team B
40
Having different focus is OK, it is even good
41
Test-driven everything
42
Cross-functional teams need testing competence
43
Process, workflows tools