200 likes | 323 Views
Iterative Task Management Process Using Group Estimations Based On Time-Boxing September 24 th , 2009 Gihan B Madawala gihanm@shaw.ca Argus Technologies Ltd CREO Products Inc Chancery Software Ltd Meridian Project Systems Ltd Modular Mining Systems Canada Ltd. PURPOSE.
E N D
Iterative Task Management Process Using Group Estimations Based On Time-Boxing September 24th, 2009Gihan B Madawala gihanm@shaw.ca Argus Technologies Ltd CREO Products Inc Chancery Software Ltd Meridian Project Systems Ltd Modular Mining Systems Canada Ltd
PURPOSE Continuous improvement Work smarter Improve productivity Clear goals/objectives Accountability Better Communication Timely delivery Have fun!
EFFECTIVE MOSTLY WHEN TEAM PROFILE • Large # of Test engineers • Many contractors • Automation/Performance engineers • Inshore/Offshore outsourcing companies • Many Geographical locations
PROCESSES USED • Rational Unified Process • Iteration based within RUP • SCRUMS – Every other day • Weekly meetings • Requirement based testing • Automation of all BVTs • Retrospectives • Iterative Task Management Process
PROBLEMS WITH TRADITONAL TEST ESTIMATIONS • Most of the time they are Open-ended • Project Manager does not have the bandwidth or enough details to do test estimations in project level • Mostly testing tasks are piggy backed to Dev tasks and has too much dependency • Sometime ad-hoc • Inaccuracy
OBJECTIVES OF TIME-BOXING METHOD • Tend to have more accuracy in estimations • Group estimation method • Tied down to iterations (sprints – usually 4 weeks) • Availability of testing resources are determined before the start of sprint • PM can have a better certainty of iteration end and release date
OBJECTIVES OF T-B METHOD Contd.. • Estimations of a task can go up or down • Testing tasks are managed in a SharePoint repository • Can nail down and address project roadblocks early • Can access whether the team has enough expertise to carry out all the tasks (If not seek resources early) • Active participation of the whole test team
WHAT IS MEASURED • Work (cost) – In points or hours • Duration – sprint for 4 weeks etc • Resources (who, how many, availability) • Priority • Status • Dependency
TIME-BOX • Release\Iteration
RESOURCE AVAILABLE ( T-B) Points available for Sprint 2 (20 working days) # Test Engineer Availability Points 1 Charlie (QA) 95% 38 2 Max (LX) 90% 36 3 Irene (QA) 50% 20 4 Alisa (LX) 50% 20 5 Anne (MD) 100% 40 6 Gihan (MD) 40% 12 7 Latten (QA) 20% 8 TOTAL 174
ESTIMATION ACCURACY Points available for Sprint 2 174 Points completed for Sprint 2 162 Total sprint estimation accuracy of +- 15%
TERMINOLOGY USED Use terminology of bringing food to the ‘Table’ Freezer-> Fridge-> Cooker-> Table Freezer - Future Items that may take time before consumption Fridge - waiting to go into cooker Cooker - Cooking in progress Table - Ready to consume
CONCLUSIONS • Testing projects can/should run as a real project (If more than 2 members in the team) • There are other proven methods of test task estimations • Time-boxing testing tasks provide better certainty than open ended tasks • More involvement of team members and have fun while testing…