Date post: | 01-Nov-2014 |
Category: |
Technology |
Upload: | tom-roden |
View: | 127 times |
Download: | 2 times |
Do Test Managers exist in the world of Agile?
About UsBen Williams – Agile Coach
@13enWilliams
Tom Roden – Agile Coach & Test <something>
@TommRoden
Our underlying assumptions
Agile methods are on a continually increasing trend
Computer Weekly Jobs, 8th November 2012
There is no prescribed Test Manager role in Agile methods
What does this mean?
Our Hypothesis
So what are our choices?
Routes
Stay in the market for traditional Test Management?
http://rontalk.com/
Get into another profession entirely?
http://byrev.org/
Make the voyage into Agile?
Any other options
Exploring the move to Agile…
But is there a need for a dedicated test related role outside of a Feature Team?
What are the responsibilities of a Test Manager?
The group’s Thoughts on how traditional TM tasks translate into agile
Goes Away in Agile Team (incl. SM & PO) should coverTeam should own, but likely to need outside support
Dedicated role outside the team
Control Resolving team conflicts Mediating cross team discussions and disputes Establishing QA Function and operating model
Writing Test Plans Test Planning Raising team profile Accountable for testing quality output
Report Writer Deciding when enough testing has been done Coach Product Owners on testable acceptance criteria Test tool adoption and usage (tool proliferation and rationalisation)
Project data analysis (needs further definition?) Lead & motivate within the team Process Improvement (cross team / divisional) Contribute to business decisions
Managing People Test approach and acceptance requirements Team Development Lead & motivate across teamsFacilitate comms between business and IT teams defect manager Line Management Measure and Report on project / test progressInvolved from concept to cash and in operation risk mitigation (identification and owner) Test Recruitment Process development improvement
Use case challenger Test reporting measure level of quality Mitigating the SDET myth
Test Activity Planning (MS Project) running system integration tests Coach non testers on design for testability Project resourcingCounter point to Project Manager (quality vs time) security and other non-functional testing mentor feature team members
Push for long term efficiency not just short term requirements
Providing sign-off OAT coaching in testing Testing is an activity not a single role
test specification Lead by example No need for a Test Mgr in a truly agile team
Reviews and approvals Fighting / standing up for the team Team appraisals?
QA ManagementHave the broader view, are the business getting what they really wanted People Management
Managing tests Test environment coordination Personal development plans
Test environment definition Training and skills development Managing offshore partners
Test Data Management Test Process Improvement Comms with senior stakeholdersOrganise reviews of Test Basis Docs (func specs etc.)
Identify new tools, processes and practices to facilitate improvement Educate on effective test techniques
Provide Metricsarticulation and management of non-functional risks (to auditable std) Develop Junior Testers to work better for teams
Making it all add up(?) take important decisions regarding quality Quality Conscience?
ensure enough testing has happened Define and agree test strategy Team Resourcing?
Release management and documentation Thought leadership (around testing)Identify quality process problems / opportunities Issue resolution
Test infrastructure requests and management Building a team
Provide info on quality of systems and services Promotion / enforcement of validation / verification
Telling people the truth about quality provision of professional cynicism (iceberg avoidance)
Plan and manage the testing Test environment ownership
Report test coverage What problem is agile testing trying to solve?
Business LiaisonCo-ordinate disparate testing activities (cross projects, companies)
Report and Manage metrics
Lead strategic discussions (needs qualifying further)
Gaining stakeholder buy-in to the test approach
Risk Management
motivating and engaging testers
First refinement of these tasks
So what might this role do?
Set a direction and philosophy of testing
Help devise strategies for testing
Coach teams in testing practices & techniques
Writing good tests
Self-documenting
Isolated
Concise
A spec not a script
About behaviour
Readable
Clear intention
Build models for self-regulation
And Other Stuff maybe…
•
•
•
•
•
Conclusions
What skills does this role need?
So is there a better name for this role?
Thank You for listening
Ben Williams – [email protected]
@13enWilliams
Tom Roden – [email protected]
@TommRoden