BIO PRESENTATION TK2 5/16/2007 4:30:00 PM "B UILDING THE T EST M ANAGEMENT O FFICE " Geoff Horne iSQA International Conference On Software Test Analysis And Review May 14-18, 2007 Orlando, FL USA
Geoff Horne Geoff Horne Geoff Horne is based in New Zealand and has founded and run two testing companies which have grown to enjoy an international clientele. He has over 28 years experience in IT including software development, sales and marketing and IT and project management. In 1994, almost by accident, he found himself involved in testing a complex fault management system which led to further testing and QA assignments covering a wide range of applications and tools. Geoff’s companies were subsequently founded to bring a full range of testing consultancy services to the IT industry. Of late, he has focused on a few select clients running complex test projects in a programme test management capacity. Geoff has written a variety of white papers on the subject of software testing and has been a regular speaker at the Star testing conferences. He is married with four children and in his spare time (which there is not a lot of) enjoys writing and recording original contemporary Christian music.
www.isqa.com BUI LDI NG THE TEST MANAGEMENT OFFI CE (TMO) Geoff Horne Managing Director
www.isqa.com Strategy Defect management & resolution Methods, standards & processes Vendor management Process adherence Tools implementation & management Communications Environments management Status reporting Planning Release management Coverage management Issues resolution Budget & cost management Schedule management Change request management Configuration management Escalation management Support management Review & approval management Human resources management Quality assurance
The typical Test Management inter-relationship model: www.isqa.com
www.isqa.com Sliced:
www.isqa.com Sliced and diced:
www.isqa.com Strategy Defect management & resolution Methods, standards & processes Vendor management Process adherence Tools implementation & management Communications Environments management Status reporting Planning Release management Coverage management Issues resolution Budget & cost management Schedule management Change request management Configuration management Escalation management Support management Review & approval management Human resources management Quality assurance Automation
www.isqa.com Strategies Defect management & resolution Methods, standards & processes Vendor management Process adherence Tools implementation & management Communications Environments management Status reporting Planning Release management Coverage management Issues resolution Budget & cost management Schedule management Change request management Configuration management Escalation management Support management Review & approval management Human resources management Quality assurance Automation
www.isqa.com Defect management & resolution Tools implementation & management Environments management Coverage management Budget & cost management Configuration management Review & approval management
www.isqa.com Defect management & resolution Tools implementation & management Environments management Coverage management Budget & cost management Configuration management Review & approval management
www.isqa.com Defect management & resolution Tools implementation & management Environments management Coverage management Budget & cost management Configuration management Review & approval management
www.isqa.com Defect management & resolution Tools implementation & management Environments management Coverage management Budget & cost management Configuration management Review & approval management
www.isqa.com Defect management & resolution Vendor management ! Tools implementation & management Communications Environments management Release management Coverage management Budget & cost management Configuration management Support management Review & approval management
www.isqa.com What is a Test Management Office? • A centre of governance for the testing subproject • Support team & mechanism for Test Managers, Test Analysts etc. • Carries responsibility for selected testing functions that may not realistically be carried by Test Manager(s) • Operates as a discrete team within the testing function • TMO has an operational & delivery responsibility as opposed to being a purely administrative function
www.isqa.com Why use one? • Removes some of the management overheads from Test Managers & Analysts • Enables test teams to focus on key testing activities • Streamlines & spreads workloads • Provides a central control of all test resources • Sometimes a necessity to keep on top of testing resources, assets and facilities
www.isqa.com When should a TMO be used ? • Large & complex testing projects • Integration with other technologies eg. telecommunications networks • Multi-workstream testing projects • Projects with multiple & disparate applications, platforms, technologies, environments etc. • No resources, infrastructures, processes within functions required to support testing eg. environment management, configuration management, release management etc. • Lack of expertise or commitment within same.
www.isqa.com Which test functions can be covered by a TMO? Strategies Defect management & resolution Methods, standards & processes Vendor management Process adherence Tools implementation & management Communications Environments management Status reporting Planning Release management Coverage management Issues resolution Budget & cost management Schedule management Change request management Configuration management Escalation management Support management Review & approval management Human resources management Automation Quality assurance
www.isqa.com Should there be a separate TMO Manager? • Depends on the size of the TMO and functions it covers. • What type of person; line manager, test manager, project manager? • Can the TMO Manager be a non-testing professional? • Can the Test Manager also be the TMO Manager?
www.isqa.com What type of roles are the management of each TMO function? • Should all TMO function managers be testing professionals? • Should any of the them be testing professionals? • Where is the balance?
www.isqa.com How should a TMO operate? • Clear distinction of responsibilities between Test Manager & TMO Manager • When should managers operate within the TMO and when outside? • Can the TMO Manager be responsible for one or more TMO functions? • Who/where should the TMO report?
www.isqa.com Steps for building a TMO: • Analyse requirement and determine need • Select project functions that should come under the TMO • Select/acquire TMO function managers • Develop a TMO charter that clearly defines: • What the functions are that will be under the TMO & why • How each function will inter-relate with other project streams • How the TMO will function with the Test Manager(s) • Where there are overlaps with other functional teams
www.isqa.com Analyse requirement & determine need: Function Role Covered? How? Test strategies TCM Yes Test Manager Defect management & resolution LPM Yes Test Manager Vendor management LPM No TMO Methods, standards & processes TCM No Engage iSQA Tools implementation & management SPM Yes Software Support Team Process adherence TCM Yes Test Manager Environments management SPM No TMO Release management SPM No TMO Communications LPM Yes Project Admin Status reporting LPM Yes Test Manager Test planning LPM Yes Test Manager Issues resolution LPM Yes Test Manager Coverage management TCM No TMO Test schedule development & management LPM No TMO Budget & cost management SPM Yes Project Management Office Configuration management SPM No TMO Change request management LPM Yes Software Development Team Support management LPM Yes Project Vendor Liaison Officer Escalation management LPM Yes Test Manager Human resources management SPM Yes HR Dept Review & approval management LPM No TMO Quality assurance SPM No Engage iSQA Line/project manager (LPM) Test consultant/manager (TCM) Specialist manager (SPM)
Recommend
More recommend
