December 1st, 2009
The system
Internal customer
SERVER
MS2003 Server
Output Files
(critical)
C++ App
DB
SCOPE
WEB GUI
[1]
December 1st, 2009
Status of the project at the beginning
“Code is already complete”
Requirements: “oral tradition”
Components Design = 2 x A4
23 Functionalities in the Project Plan…… 51 implemented
[2]
December 1st, 2009
Estimating…
Trying to use the structured approach
And the management’s reaction
Expected Delivery
RegressionExecutionRamp up + analysis Specification
30 man.weeks
[3]
15 m.w
December 1st, 2009
Back to the “planning” board
We have to “discover” the requirements
Costs Ramp up + Analysis + Test design too high
Test execution starts too late => too risky
[4]
December 1st, 2009
Strategy and processes:
Exploratory Testingsimultaneous learning, test design and test execution
Test sheets“Done” , “Test Ideas”
Agile planning (SCRUM like)Burn down, self-organizing, Whiteboard
[5]
December 1st, 2009
The solution:
Test Sheets
Defects
RegressionStructured testingExploratory Testing
Defects
30 man.weeks
Test Scripts
[6]
December 1st, 2009
Did it work? Yes it worked!
RegressionStructured testingExploratory Testing Delay
Delay announced
33 man.weeks
10%
[7]
~250 defects found, ~170 fixed
4 defects found during acceptance, 1 critical
1 new defect found in 6 months
December 1st, 2009
Team needs to adapt:
TestersAttitude changes,
Building trust
Project ManagerLearning
Avoiding over-reactions
Test ManagerKeeping the vision
Product knowledge
[8]
December 1st, 2009
Lessons learned:
Building up on the pastLearning curve complete
Reusable basis for next project
Knowledge, confidence and trust
Reliability of estimatesHigh variability
Long term issuesProduct and Process Improvement
Demands on the testing team
[9]
December 1st, 2009
Conclusion:
This is a solution to bring a project back on track and reduce costs and lead time
Test team knowledge and psychology have to evolve to practice Agile
Agile can be the way to structure at project level
[10]