This short presentation will highlight how TREDD provides the missing ingredient needed for product development teams to successfully implement SCRUM to peak effectiveness and quality.

1. HOW TREDD
CAN
IMPROVE YOUR
SCRUM TEAMS PERFORMANCE

2. Many companies have implemented SCRUM
as their software development methodology…
with lackluster results

3. Ask Yourself This Question…

4. High
Defects
Unimaginative
Incomplete
Sprints
Poor
Quality
Disjointed
Contributions
High
Maintenance
Admonished
Self Imposed
High Standards
IS THIS HOW YOU ENVISIONED
YOUR
SCRUM TEAM PERFORMING?

5. Quality
Minded
Innovative
Sprints
Fully
Completed
Forward
Thinking
Highly
Collaborative
Self
Accountable
Admirable
Self Imposed
High Standards
OR THIS?

6. 3 Common Factors Hindering
SCRUM Team Performance
A. Quality is under-emphasized, and mistakenly
believe to occur at the end of the iteration by
QA members
B. SCRUM doesn’t provide leading indicators for
team performance.
Burndown/up charts provide insight for progress, not
performance
C. Team members continue to contribute based
on their roles (like in waterfall) ,not based on
their talents

7. Improve Performance with
TREDD
• Test Requirement Driven
Development (TREDD)
• Originated from listening to the
frustration and disappointment of
Senior Management and Product
Development Teams trying to
implement SCRUM
• Proven through successfully turning
around low performing SCRUM
teams across several organizations

8. Four Game Changing Aspects of
TREDD
1. Quality - Begin with the End in Mind
2. Test Requirements
3. Objective Metrics for Performance
4. Talent Based Collaboration

9. Quality – Begin with End in Mind
QA contributes their value
when the product is being
developed, by defining
the test cases with the
User Story; not at the end
of the development cycle.
As W. Edwards Demming once said:
“Inspection does not improve
quality, or guarantee quality.
Inspection is too late. The quality,
good or bad, is already in the
product”

10. Test Requirements
What are Test Requirements?
– More detailed requirements,
replacing acceptance criteria
– Like test cases, they are
simple, singular pass or fail
statements
– Provide what developers
need to develop and verify
their code
– Have 4 classifications,
providing leading indicators
of teams performance
Test Cases
(from QA)
Requirements
(user stories
and
acceptance
criteria)
TEST
REQUIREMENTS

11. Objective Metrics for Performance
• 4 Test Requirement
Classifications
– Passed
– Defective
– Rejected
– New
• Provide an accountable and
objective metric to diagnose
and improve team
effectiveness

12. Talent Based Contribution
• TREDD encourages collaboration
• All team members are expected to add, define,
discuss, and evaluate Test Requirements
• De-emphasizes roles and encourages talent
contributions
• Creates a Product-Centric mindset:
Product Owner Product Facilitator
Product Analyst Product Developer

13. Is This What You Need?
This is how the TREDD methodology catalyzes and improves the efficiency
and effectiveness of Product Development Teams utilizing SCRUM.
If your SCRUM teams aren’t performing to the level you were expecting,
then it may be worth your while to contact Savvy Management, and
further explore how TREDD can raise the performance and quality of your
Product Development Teams!
For More Information Contact:
www.SavvyMGT.com
Info@SavvyMGT.com