Expositor: Janet Gregory Resumen: When agile development first gained popularity, agile meant collocated teams, including testers, programmers, analysts, and customers who were expected to perform many functions. As agile methods have spread and expanded, it becomes apparent that one size does not fit all. For example, large organizations and those with globally-distributed teams are facing challenges with their agile deployment. Having worked with many teams, Janet Gregory has observed ways that testing in any agile teams can still help deliver a high-quality product. Whether your agile team is part of an enterprise solution, or part of a distributed team is scattered across time zones with individuals working remotely from home, or is part of an offshore outsourced project, you’ll take away techniques and tools to help develop open communication, deal with cultural differences both within an organization and across continents specifically related to testing activities.

1. 2019-05-29
1
@janetgregoryca | #testinguy
Agile Testing in
Context
Janet Gregory
janet@agiletester.ca
@janetgregoryca
13 y 14 de mayo, 2019
testinguy.org
@testinguy | #testinguy
DragonFire Inc.
Copyright @2019 DragonFire Inc.
@janetgregoryca | #testinguy
- Small companies - less than 100 people
- Large companies - more than 1,000 or 5,000 or …. employees
- Different cities, same time zone (or 1 hr. apart)
- Time zones more than 7 hrs difference
- Practice agile or agileish?
- Practice continuous delivery or deployment
- Practice phased and gated (waterfall)
…….. and so many others contexts
Different Contexts
1
2

2. 2019-05-29
2
@janetgregoryca | #testinguy
My Message Today
to share my
experiences on how
agile testing activities
can be used in any
context
@janetgregoryca | #testinguy
Some of the challenges
Plan for testing
Key testing practices that work across teams
Sharing is caring
3
4

3. 2019-05-29
3
@janetgregoryca | #testinguy
Small co-located teams: Agile’s sweet spot
@janetgregoryca | #testinguy
Organizations that
have enterprise
applications and
solutions
Large organizations Distributed teams
Teams that cross cities,
countries, continents
5
6

4. 2019-05-29
4
@janetgregoryca | #testinguy
What is Organizational Culture?
Defined by its:
• Values, norms, assumptions
• Social system
• Visible artifacts
• Icons
• Rituals
• Vocabulary
Let’s try something …
7
8

5. 2019-05-29
5
@janetgregoryca | #testinguy
Organizational Issues ..
How do we
interact?
Do you play the
blame game?
@janetgregoryca | #testinguy
Struggles for large agile teams
• Bureaucracy – lots of paper work
• Reporting needs (real or imagined)
• Orders handed down from above…
• Too many concurrent projects
9
10

6. 2019-05-29
6
• Organizational controls – regulatory, internal
• Working with third parties
• Involving customers in other locations
• Large system integration
• Fast delivery cycles
Why is testing hard?
@janetgregoryca #TestingUy
@janetgregoryca | #testinguy
Other Testing Specific Issues
Too many dependencies
Tester on more than one team
11
12

7. 2019-05-29
7
@janetgregoryca | #testinguy
@janetgregoryca | #testinguy
Some of the challenges
Plan for testing
Key testing practices that work across teams
Sharing is caring
13
14

8. 2019-05-29
8
@janetgregoryca | #testinguy
Consider the feature
Create testable stories
Who tests what?
Testing is a team problem
@janetgregoryca | #testinguy
ReleasePlanning
Team A
Planning
Test Mind Map
Team B
Planning
Team C
Planning
Team D
Planning
Release
Test Matrix
Release
Test Planning
/ Approach
15
16

9. 2019-05-29
9
Lots of Stuff Shopping
Release 1.5
DataIntegrity
Look&Feel
Calculations
Currency
Localization
DevicesiPad
DevicesiPhone
BoundaryConditions
Load/Performance
Security
Store customer information
Add to shopping cart
Calculate shipping costs
Mobile iOs - view only
Next feature
Legend
Good to Go
Some testing; could use more
Major issue
No testing done
Not applicable `
#TestingUy@janetgregoryca
17
18

10. 2019-05-29
10
Think in Levels of Detail
Dependencies
between teams
Remove them
before the iteration,
but remember to
test them
@janetgregoryca #TestingUy
19
20

11. 2019-05-29
11
@janetgregoryca | #testinguy
@janetgregoryca | #testinguy
Testing is a team problem, but
who is your team?
21
22

12. 2019-05-29
12
Who is in your extended family?
@janetgregoryca | #testinguy
Each team responsible
for delivering their
feature -- completely
Specialist teams report
to the “owner” feature
team.
23
24

13. 2019-05-29
13
@janetgregoryca | #testinguy
Implicit vs explicit needs
Over-riding test strategy on how …. but
• Understand who is testing what
• What are the overlaps?
• Where are the gaps?
• Co-ordination between teams?
• ASK: Who, when, how???
@janetgregoryca | #testinguy
Coordinate tools and practices
Especially important in continuous delivery
25
26

14. 2019-05-29
14
@janetgregoryca | #testinguy
Team Tools
• Same version control
• Understand the branching and merging approach
• Same continuous integration (CI) environment
• Use to visualize test results
• Accessible & stable test environments
• Know what versions of applications are in each environment
@janetgregoryca | #testinguy
Some of the challenges
Plan for testing
Key testing practices that work across teams
Sharing is caring
27
28

15. 2019-05-29
15
@janetgregoryca | #testinguy
•What is the state of testability of your architecture?
• Can you simplify it for automation?
•Regulatory
• simplest thing you can possibly do
• Consider NECESSARY artifacts – can you automate
•Working with third parties (internal / external)
• Remove dependencies
• Create fast feedback loops
Consider practices for effective testing
@janetgregoryca | #testinguy
• Aim for short feedback cycles – especially in continuous delivery
• Remove dependencies early
• Start with a test to remove assumptions
Key testing practices
29
30

16. 2019-05-29
16
@janetgregoryca | #testinguy
Feature
(with examples) User
Story
High-
Level
AT
Fix Defects
Code, test & automate story
ATDD
Acceptance Test Driven Development
Accept
Story
Explore
Examples
@janetgregoryca | #testinguy
We can use tests and examples for shared
understanding and common language
For example, create a function to add 2 numbers
-2 + 1 = -1
2.0 + 1.050 = 3.050
2.0 + 1 = 3.0
2 + 1 = 3
31
32

17. 2019-05-29
17
• Power of 3
Create a Shared Understanding
• Repeat verbal conversations in writing
• Question
• Draw pictures
• Test ideas
@janetgregoryca | #testinguy
Pair - Share your desktop
33
34

18. 2019-05-29
18
Explore in Groups
@janetgregoryca #TestingUy
@janetgregoryca | #testinguy
Testing
is a team
problem
• Tests can provide fast feedback
• Examples (tests) show desired behaviour
• Remember -- know your team!
35
36

19. 2019-05-29
19
@janetgregoryca | #testinguy
Some of the challenges
Plan for testing
Key testing practices that work across teams
Sharing is caring
@janetgregoryca | #testinguy
Sharing information, that is
Transparency means less blame
• No hiding
• No secrets
• No gaming the system
The hard part is making it visible
Sharing is Caring ……
37
38

20. 2019-05-29
20
@janetgregoryca | #testinguy
• Share dependencies
• Same vision
• Same goal
• Accessible to all
• Keep everyone “in the loop”
Visibility / Transparency
Remember: Include your extended family
39
40

21. 2019-05-29
21
@janetgregoryca | #testinguy
@janetgregoryca | #testinguy
Use communities of practice for sharing
41
42

22. 2019-05-29
22
@janetgregoryca | #testinguy
@janetgregoryca | #testinguy
Work together to achieve your goal
43
44

23. 2019-05-29
23
@janetgregoryca | #testinguy
Final note:
I’m not advocating distributed teams or out-sourcing
but if you are faced with those problems, I hope you can use
some of these ideas to help manage your agile testing.
and
Agile ≠ NO DOCUMENTATION
Know your own context!
Contact Information
janet@agiletester.ca
https://janetgregory.ca
twitter: @janetgregoryca
https://agiletester.com
https://agiletestingfellow.com
(subscribe to our newsletter!)
45
46

24. 2019-05-29
24
@janetgregoryca | #testinguy
• Practices for Scaling Lean & Agile Development: Large, Multisite and Offshore Product
Development with Large-Scale Scrum, Craig Larman and Bas Vodde, Addison-Wesley, 2010
• Agile Software Development in the Large: Diving into the Deep, Jutta Eckstein, Dorset House,
2004
• More Fearless Change: Patterns for introducing new ideas, Linda Rising and Mary Lynn
Manns
• Adzic, Gojko, Specification by Example: How Successful Teams Deliver the Right Software,
Manning, 2011
• Wynne, Matt and Aslak Hellesoy, The Cucumber Book: Behavior-Driven Development for
Testers and Developers, Pragmatic Programmers, 2012
• Gáspár Nagy, Seb Rose, Discovery: Explore behaviour using examples (BDD Books) (Volume 1)
• http://sites.google.com/site/visualisingquality/
• www.lisacrispin.com
More Reading & References
@janetgregoryca | #testinguy
Janet Gregory
janet@agiletester.ca
@janetgregoryca
13 y 14 de mayo, 2019
testinguy.org | @testinguy | #testinguy
¿PREGUNTAS?
¡MUCHAS GRACIAS!
COLOQUE AQUI LOGO
DE EMPRESA
47
48