1.
do testers really thrive at night? Alan Mather QBIT Test Expo 19.09.2007 www.diverdiver.com/egovblog.html To achieve great things, two things are needed; a plan and … not quite enough time

2.

3.
ables f elivery

4.
1. our architecture is robust

5.
2. we won’t be working Christmas again trust me

6.
3. we will be innovative no, trust me!

7.
4. we have a highly skilled “can do” team Tester Programme Director Project Manager Account Manager’s Lackey Ops Manager Account Manager Health and Safety HR Service Manager Test Manager Commercial Director

8.
5. the customer has clear requirements Special To Hint Urgent circumstance or door is take placed out to break down for hour, please draw apart this to revolve the red solution to lock the pole

9.
the inevitable reality the design team’s plan the test team’s plan Programme Starts Design Starts Build Starts Testing Starts Deliver On-Time Deliver Early Testing Starts Test Planning Expectation Gap test plan? we need one of those?

10.
Heroes emerge … crunch time <ul><li>work harder and longer … always </li></ul><ul><li>de-scope … usually </li></ul><ul><li>add people … fred p. brooks says no </li></ul><ul><li>spend more … of course </li></ul><ul><li>… slip the live date … unthinkable </li></ul>Expectation Gap

11.
or worse … resort to … drive by testing got to deliver

12.
so what are we going to do about it? help! I’m just the customer

13.
build for the long term Today’s sexiest technology is tomorrow’s legacy (if it even works)

14.
no more accidental testers appoint a C.T.O

15.
use established teams

16.
save (all) environments … go forth and replicate get the basics right …

17.
[really] partner if you’re not [really] strong <ul><li>bigness does not lead to greatness; </li></ul><ul><li>Small [companies] can still be beautiful … they </li></ul><ul><ul><li>ramp up faster </li></ul></ul><ul><ul><li>come with lower overheads </li></ul></ul><ul><ul><li>innovate to get ahead </li></ul></ul><ul><li>but they might test you out </li></ul>Let’s not be bull-headed about this

18.
know your risks do you know what you’re getting into? leaping is part of testing

19.
know what you (all) want = + success depends on it

20.
know your maths/metrics <ul><li>what is the true cost of future change? </li></ul><ul><li>how much coverage is good coverage? </li></ul><ul><li>what ratios are you using? </li></ul><ul><li>have you architected, from day one, for automation? </li></ul><ul><li>what will you do when you find out you were wrong? </li></ul>all testing is a process of subtraction

21.
time for the IT industry to grow up <ul><li>build for the long term </li></ul><ul><li>no more accidental testers </li></ul><ul><li>save (all) environments </li></ul><ul><li>hire established teams </li></ul><ul><li>[really] partner if you’re not [really] strong </li></ul><ul><li>know your risks </li></ul><ul><li>know what you (all) want </li></ul><ul><li>know your metrics </li></ul>do testers really thrive at night?