While agile methods do not prescribe a dedicated test manager role, there may still be value in having a role focused on testing responsibilities outside of a feature team. Such a role could help set a testing philosophy and strategy, coach teams in testing practices and techniques, and build models to help teams self-regulate testing activities. This role may need skills in coaching, facilitating communication, and helping teams work effectively. There is debate around what to call this role, as "test manager" may not fully capture its responsibilities in an agile context.
18. Goes Away in Agile Team (incl. SM & PO) should cover
Team 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 teams
Facilitate comms between business and
IT teams defect manager Line Management Measure and Report on project / test progress
Involved 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 resourcing
Counter 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 Management
Have 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 stakeholders
Organise reviews of Test Basis Docs (func specs
etc.)
Identify new tools, processes and practices to facilitate
improvement Educate on effective test techniques
Provide Metrics
articulation 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 Liaison
Co-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
Firstrefinementofthesetasks