Traditionally, the testing community has perceived test data the same way most organisations perceive test. Boring, time consuming and none value-adding. But new winds are blowing. Initiated by the complex project and test environments of today, testing departments are now taking the first small steps to recognise the importance of a focused test data management function. Maybe the testing community will too? Realising that we have long passed the good old days where a mainframe test data copy would do the trick, challenges in implementing a TDM function in today’s complex set-ups are many and insidious. And it needs a well executed plan. This presentation takes outset in experiences and hardships gained from a TDM optimising project and provide a live demo, inspiration and guidelines in moving forward with implementing and optimising a TDM function. The project was run alongside a big-scale on-going SOA programme at a major Danish pension fund. The project focused on three areas: Technical, Process, and People & Communication. In the Technical area, the project developed a TDM Dashboard. As a main management component, the Dashboard provides a test data copy function from Production to Test and between test environments. Besides, it offers an overview of the test data in the different applications and environments. The Process area developed a TDM strategy and optimised the test data processes in order to deliver valid, transversal test data quicker. It focused on a wide range of areas such as production copying, data generation, handling of requirements, data cleaning, profile usage, data pools and data re-use. The People & Communication area focused on including stakeholders proactive in the test data process and communicating roles and responsibilities as well as new functions and processes. Not only has the project delivered measurable and visible results, number of defects in Production has been reduced; hereby stressing that a well implemented TDM function with continuous focus on optimising TDM is added value and worth the effort.

1. Allan Hendeles,
ATP
Kristian Fischer,
PA Consulting Group
Test Data Management and Project Quality Go
Hand In Hand
Eurostar, Manchester, 2011
November 23 @ 09:45 am

2. Allan Hendeles – Test Specialist
In charge of Test Data Management at the largest Danish pension scheme ATP
Kristian Fischer – Management Consultant
Expertise in project and test management working at PA Consulting Group
2
Both are experienced in test in general and in test data management &
test environments specifically.

3. ATP was established in 1964 and is the largest Danish Pension
Scheme with approx. 4.5 million members. ATP pay pensions to more
than 675,000 pensioners. ATP employs 750 people, which will triple in
2012 as ATP will administer five more schemes for the Danish state.
PA Consulting Group is a leading management and IT consulting and
technology firm. Independent and employee-owned, we operate globally
in more than 30 countries and transform the performance of major
organisations in both the private and public sectors.
3

4. This presentation takes outset in experiences gained and processes used
from a Test Data Management (TDM) function implementation.
And provides a live demo, inspiration and guidelines in moving forward
with implementing and optimising a TDM function.
4

5. 5
Complex environments call for simple solutions
Communication domains
Data domains
Infrastructure domains
Core1
.net
DB2
windows
UnitLink
.net
DB2
Unix
Payment
SAP
Core2
SAP
Masterdata
java
DB2
windows
Call Center Portal Document Journal
Security Integration Workflow
pl1
DB2
mainframe

6. 6
How to cope with test data in complex environments
Situation
• Complex projects and test environments
Challenge
• Handling test data is becoming increasingly
harder and more important
Question
• How do we cope with test data in the complex
projects and test environments of today?
Key
Message
•Implement a TDM function to ensure project
success through a quality test process

7. 7
Implement a TDM function focusing on three areas
7
People &
Communication
Strategy &
Process
Technical &
development
Look at the animal
farm…
Know proactive
stakeholder
management is key.
Set up the
communication and
get the necessary
commitment…
Write a test data
strategy…
Include process work
Think before you
develop
Take into account
the need for coherent
data…
Don’t ignore security
when approaching
production data…
Prioritise the most
valuable
functionalities

8. 8
Look at the animal farm
Key Point 1: Create a stakeholder map to help manage, align, report and control
project engagement.
Buy-in (attitude to the project) Shareofvoice
(degreeofinfluence)
Big
Small
Positive
Beware of the snakes, but don’t ignore the others…

9. 9
Know proactive stakeholder management is key
Stakeholders on the TDM project were among others
 IT testers & business testers
 Project managers
 Sponsors
 IT Directors
 Technical architects
 Operations
 Security.
Key Point 2: Use your stakeholder management strategy, plan proactively
and keep it updated.
What ‘s in the best interest of one stakeholder may not be in the best interest of another stakeholder…

10. 10
Set up communication and get commitment
Key Point 3: Create a communication plan and align with stakeholder
management plan.
We said
A
We meant
B
They
understood C
They did
D
Should have
been E
1. Have a one minute vision in hand
2. Don’t be afraid to repeat
3. Let the people know
4. Get to the point
5. Listen actively.
Clear eyes, full hearts, can’t lose!

11. 11
Write a test data strategy
 Managing test data requirements
 Controlling the use of test data
 Managing test data profiles
 Copying production data to test
environments
 Protecting data privacy.
Key Point 4: Write a strategy, implement it and execute it.
 Maintaining test data quality
 Creating additional test data
 Reusing test data
 Cleaning up test
environments
A good strategy looks at problem solving and the best ones are executed

12. 12
Include process work
Simplify complicated things by drawing processes
 Test data ordering
 Test data copying
 Test data reservation
 Test data refresh
 Test data cleaning.
Key Point 5: Have your processes ready-drawn and head out for a road-show
Processes are not boring, they just look that way…
Example

13. 13
And then - time to develop
Develop a TDM Dashboard by
 Prototyping
 Agile development
 User inputs
 ATP GUI look-a-like
 Priorities
 One domain at a time.
Key Point 6: Implement in the small and use the users. No big bang here.
A fool with a tool is still a fool…

14. Take into account the need for coherent data
Production
UnitLinkMasterdata Core1 Core2 Payment
s
Integration
environments1-6
Key Point 7: Plan ahead to secure that data is coherent, valid & useful in all
relevant environments.
Everyone has a plan - until they get punched in the face. - Mike Tyson…
Core2 Payment
s
Core1UnitLinkMasterdata
14

15. 15
Include security measures
 Depersonalization from production
 Production access requires acceptance from security-department
 Production access restricted to daytime
 Logging and auditing
 Only selected features are available in Production
 DBA SQL review
In close cooperation with Security and Operations.
Key Point 8: Make a big effort of getting the security right.
Don’t ignore security when production data
Security don’t come cheap, but it’s worth it…

16. 16
Ten examples of what the TDM can do
1. Data parameter search
2. Data overview in domains
3. Data copying
4. Data reservation
5. Simple data modification by users
6. Log of user activities
7. Replication
8. Service tester
9. Presentation of log
10. Access to production data.
Prioritise functionalities
Key Point 9: Review your business case (because you do have one) and
prioritise functionality again.
Little strokes fell great oaks…
Will be demoed

17. 17
 Out of 200 in the IT organisation, more than 25 % uses TDM every
month
 Up to 5,000 searches a month - average of 100 per person per month
 200 monthly data changing functions
 An estimate of 650 hours saved a year.
The TDM dashboard numbers are

18. KP1: Create a stakeholder map to help manage, align, report and control project engagement.
KP2: Use your stakeholder management strategy, plan proactively and keep it updated.
KP3: Create a communication plan and align with stakeholder management plan.
KP4: Write a strategy, implement it and execute it.
KP5: Have your processes ready-drawn and head out for a road-show.
KP6: Implement in the small and use the users. No big bang here.
KP7: Plan ahead to secure data is coherent, valid & useful in all relevant environments.
KP8: Make a big effort of getting the security right.
18
KP9: Review your business case (because you do have one) and prioritise functionality again.
Nine steps for implementing a TDM function and
securing project quality
Treat a Test data project exactly the same way as you would do a
‘normal’ project. With respect and professionalism.