2017 ice - rqm - stop wasting time and take control

Watson / Presentation Title / Date1
ICE 2017
M. Kevin McHugh
Kirk Woods
Lee Thomas
RQM – Stop Wasting Time and
Take Control

• Introduction
• Aspects of Testing
• Past Training
• 5Ws + H
• Q&A
Agenda

• M. Kevin McHugh: Senior Managing Consultant
• Kirk Woods: Senior Managing Consultant
• Lee Thomas: Senior Managing Consultant
Introduction

Quick
Poll

• Planning
• Authoring
• Execution
• Defects
• Reporting
• Coverage
• Tracking
Aspects of Testing

RQM Documentation

How can we manage Test…

How can we manage Test…
“On Purpose”

RQM Artifacts
Test Plan
Test
Suites
Execution
Records
(TCER,
TSER)
Execution
Results
Test
Environments
Schedules
Test
Cases
Test
Scripts
BuildsUser IDs

RQM Artifact Concepts – 5 Ws + H
Planning
Group of
Whys
When
Where
Why
How
Factual
Record
Where
When
Why
How
WhatWho

RQM as a CLM component: QM
Test Plan
Test
Suites
Execution
Records
(TCER,
TSER)
Execution
Results
Test
Environments
Schedules
Test
Cases
Test
Scripts
BuildsUser IDs
Requirements
RM (DNG)
Defects
CCM (RTC)

RQM promotes re-use, not copying:
– Test Environments can be re-used for multiple Test Plans
– Test Cases can be re-used for multiple Test Plans and Test Suites
– Test Scripts can be re-used for multiple Test Cases
– Test Data and Execution Variables allow Test Scripts to be run multiple times with varying
input values
– Test Scripts can be assembled from Keywords
– Test Execution Records are executed multiple times to create unique Test Execution Results
Make changes to one copy instead of many times
Save time by minimizing maintenance

Test Scripts don’t contain Why, Where, or When - only How
An Execution Record combines Why, Where, When, and How
– e.g. Test Case, Environment, Schedule, Test Script
Testers (Who) executed Test Execution Records (TCER or TSER)
– Therefore Testers don’t need to spend extra effort or time to capture the result’s context in the
5W’s
– A Test Script can be debugged by running a Test Case
• This creates a temporary TCER; its Test Execution Result will not contribute to Results
tracked in any Test Plan
Execution Record concept – “no lost Ws”

Track test authoring and test execution, live
– Progress within a Test Plan, details of one or many Test Plans on a Dashboard
• Have we addressed all the “Why we need a test” items?
• Who has too much to test? Who has found many failures? Where are they occurring?
– Shorten status meeting time dramatically.
Track changes to requirements and defects, live
– Did a Why change, prompting us to re-think our How and Where?
– Do we need a particular new build (a What+Where)?
– Stay informed, reduce surprises.
Create reports as needed
– Auditable records of Who, What, When, Where, Why, and even How (if needed)
– Formatted for stakeholders who do not have RQM access
– Reduce the manual labor of compiling data you don't consume.
Tracking, Reporting – consume and send 5 Ws + H

RQM Artifact Concepts – 5 Ws + H
Planning
Group of
Whys
When
Where
Why
How
Factual
Record
Where
When
Why
How
WhatWho

Reporting “On Purpose”
Planning
Group of
Whys
When
Where
Why
How
Factual
Record
Where
When
Why
How
WhatWho
Planning

Planning
Group of
Whys
When
Where
Why
How
Factual
Record
Where
When
Why
How
WhatWho
When - Iterations

Planning
Group of
Whys
When
Where
Why
How
Factual
Record
Where
When
Why
How
WhatWho
Why – Test Cases

Planning
Group of
Whys
When
Where
Why
How
Factual
Record
Where
When
Why
How
WhatWho
Where -
Environment

Planning
Group of
Whys
When
Where
Why
How
Factual
Record
Where
When
Why
How
WhatWho
Who – TCER Owner

Uses: Who, When, Where, and Why

Planning
Group of
Whys
When
Where
Why
How
Factual
Record
Where
When
Why
How
WhatWho
Planning

Planning
Group of
Whys
When
Where
Why
How
Factual
Record
Where
When
Why
How
WhatWho
When - Iterations

Planning
Group of
Whys
When
Where
Why
How
Factual
Record
Where
When
Why
How
WhatWho
Why – Test Cases

Planning
Group of
Whys
When
Where
Why
How
Factual
Record
Where
When
Why
How
WhatWho
Where -
Environment

• Planning
• Authoring
• Execution
• Defects
• Reporting
• Coverage
• Tracking
Aspects of Testing

Some more comments
• We can now say that Build 455, has a pass or fail verdict.
• What happens when you create a defect from Test Execution?
• Requirements impacted
• Test Case impacted
• Work items (user story) impacted
• Friday, 4PM Magnolia 1 – Tracing presentation

Q&A

Thank
You!

2017 ice - rqm - stop wasting time and take control

More Related Content

Similar to 2017 ice - rqm - stop wasting time and take control (20)

More from M Kevin McHugh (8)

Recently uploaded (20)

2017 ice - rqm - stop wasting time and take control