Although requirements provide valuable information that informs and shapes testing, sometimes the information provided is incomplete or unclear. Join Julie Lebo as she shares her experience with requirements engineering and how she has integrated her testing group into the requirement process. She believes testers are a valuable asset to the requirement process, and their involvement can improve quality in many ways including finding bugs earlier in the lifecycle, gaining a deeper understanding of their project and product, and writing tests that provide more value to the organization. Julie discusses the benefits she has experienced by moving QA to the left—earning higher credibility among her team, gaining more visibility for the testing team with stakeholders and organization, and creating better communication throughout all areas of the project. Leave with the ideas and steps to get your team involved early in the requirements process.

1.
T5
Testing
&
Requirements
10/5/17
9:45
Get
Involved
Early:
A
Tester's
Experience
with
Requirements
Presented
by:
Julie
Lebo
Applied
Research
Laboratories:
University
of
Texas
Brought
to
you
by:
350
Corporate
Way,
Suite
400,
Orange
Park,
FL
32073
888-­‐-­‐-­‐268-­‐-­‐-­‐8770
·∙·∙
904-­‐-­‐-­‐278-­‐-­‐-­‐0524
-­‐
info@techwell.com
-­‐
http://www.starwest.techwell.com/

2.
Julie
Lebo
Applied
Research
Laboratories:
University
of
Texas
Software
engineer
Julie
Lebo
has
more
than
eight
years
of
test
engineering
experience,
which
began
when,
as
a
student,
she
developed
her
interest
in
and
appreciation
for
finding
bugs
and
solving
problems.
After
graduation,
Julie
became
a
software
developer
and
quickly
became
the
lead
test
engineer
for
a
software
development
group
at
Northrop
Grumman.
Now
a
QA
manager
for
the
University
of
Texas,
Julie
works
on
a
complex
software
project,
where
she
has
grown
the
software
test
program
from
the
ground
up.
Passionate
about
testing,
Julie
aims
to
continue
to
expand
her
education
and
knowledge
in
this
field.

3. 1
Getting
Involved
Early:
A
Tester’s
Experience
with
Requirements
Julie
Lebo
lebo.julie@gmail.com
https://www.linkedin.com/in/julie-­‐lebo-­‐9419b06b/
First
Exposure
to
Test
My
Test
Journey
First
Job
Out
of
College
Moved
to
Texas
Take
Job
at
ARL:UT

4. 2
Challenges
No
test
team.
Testing
only
included
at
the
end
of
the
lifecycle.
Solo
tester
Experience
Developer
requirement
meetings.
Involved
in
end-­‐user
training.
Trying
to
understand
the
project’s
context.

5. 3
Takeaway
Keep
trying
to
move
testing
forward
in
the
lifecycle.
Ask
questions.
Place
yourself
in
a
position
to
learn
information
about
your
project
and
context.
First
Exposure
to
Test
My
Test
Journey
First
Job
Out
of
College
Moved
to
Texas
Take
Job
at
ARL:UT
Grad
School

6. 4
Challenges
Ambiguity
Requirement
Acquisition
Requirement
Representation
BLUE
TEAL
Incompleteness
Experience
Understanding
my
project’s
context.
Early
lifecycle
processes
can
be
extremely
important.
Poor
Requirements

7. 5
Takeaway
Tester
skills
can
help
address
requirement
challenges.
“Test
early,
test
often”
starts
earlier
in
the
lifecycle.
Early
processes
are
key
to
understanding
our
context
and
testing
effectively.
First
Exposure
to
Test
My
Test
Journey
First
Job
Out
of
College
Moved
to
Texas
Take
Job
at
ARL:UT
Grad
School
Team
moves
to
Agile

8. 6
Challenges
User
Story
Expectations
Understanding
project
context.
Getting
team
buy-­‐in
Experience
Better
testing.
Story
Workshop
Involvement
Test
Team
Credibility

9. 7
Takeaway
All
parts
of
the
team
to
have
the
same
understanding
and
as
early
as
possible.
Test
value
is
seen
earlier
and
more
often.
Testers
can
make
more
informed
decisions
if
involved
early.
Summary
• Participating
in
requirement
process
helped
shaped
our
understanding
of
the
project’s
context.
• Better
awareness
and
understanding
of
business
and
technical
needs
led
to
richer
testing.
• Earlier
involvement
has
improved
our
team
dynamic
and
increased
test
team
credibility.

10. 8
THANK
YOU