Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Practitest webinar - When a test manager makes a difference

243 views

Published on

Due to the adoption of Agile, the role of test manager seems redundant. Teams and individual professionals are self-managing and coordinating their own work.

Nevertheless, in some organizations and projects, there is a need for a quality ambassador that understand the agile quality strategy and can help, monitor and ensure that working solutions are delivered.

In this webinar we will explore situations in which you as a test manager can make a difference. For example:

How do we e.g. deal with compliance, integration and final acceptance in a contractor’s context?
How does a test manager coordinate the work over teams and ensures the quality of the testing itself?

Thanks Joel Montvelisky, PractiTest Chief Solution Architect, for hosting my webinar.

Published in: Software
  • Be the first to comment

Practitest webinar - When a test manager makes a difference

  1. 1. When a Test Manager Makes a Difference Practitest Webinar Derk-Jan de Grood / Valori 26 September 2017
  2. 2. 2 “The only constant I am sure of Is this accelerating rate of change” Source:[PeterGrabriel–downsideup]
  3. 3. 3
  4. 4. Goals Find out where Test managers can add value in todays context 4
  5. 5. The Traditional Test manager What does the test manager do? 5
  6. 6. Traditional test managers spend time on… 6 Test Policy Test strategy (for the team, the project, the organization) Budget & Resourcing PRA Environment Planning new releases to test Release Advise Test report Progress report Fight for quality (with e.g. the project manager) Connect (with e.g. Release management) Defect Triage Staff tasks like Team lead, Education, etc. TPI Tooling and Automation
  7. 7. Let’s go Agile 7 Part of Development Done = Tested Team is responsible for testing
  8. 8. … Continues Integration and Deployment 8 Part of Development Done = Tested Team is responsible for testing Part of Delivery Pipeline Automated
  9. 9. Agile testing differs Continues Involvement Tools Essential Multi Dimensional Skills Com- munication Quick Feedback 9 Nishi Grover Garg
  10. 10. Set your Course 10
  11. 11. Workshop TestNet 11 How did your work change over the last 5 years?
  12. 12. Workshop TestNet 12 How did your work change over the last 5 years?
  13. 13. More Less Started Stopped Keep • Teamwork • Exploratory testing • Automation • Feedback customers • Global TS • Releases • Security • PRA • E2E testing • Cloud • Working individually • Detailed scripts • Manual Testing • Formal acceptance • Reporting and Logging • Test planning • Uniform tests • Test automation • Using tools • Real time test results • Integrated tests • Using Production Data • Value driven decision making • Data driven decision making • Agile SCRUM • Auditing • Open source + own build tools • Testers that can only test • Detailed test plan • Manual written test reports • PRA (while doing devops) • Quality Focus • Specifications • Drafting test cases based on specifications • Hardcore Testing • Keep learning • Waterfall • UAT 13 Test management tasks gone sour How did your work change over the last 5 years?
  14. 14. More Less Started Stopped Keep • Teamwork • Exploratory testing • Automation • Feedback customers • Global TS • Releases • Security • PRA • E2E testing • Cloud • Working individually • Detailed scripts • Manual Testing • Formal acceptance • Reporting and Logging • Test planning • Uniform tests • Test automation • Using tools • Real time test results • Integrated tests • Using Production Data • Value driven decision making • Data driven decision making • Agile SCRUM • Auditing • Open source + own build tools • Testers that can only test • Detailed test plan • Manual written test reports • PRA (while doing devops) • Quality Focus • Specifications • Drafting test cases based on specifications • Hardcore Testing • Keep learning • Waterfall • UAT 14 Test management tasks with value How did your work change over the last 5 years?
  15. 15. 15 THE TESTMANAGER There is no formal role for Test management in Agile BEWARE
  16. 16. Exploring in addition to checking How Quality is achieved in agile 16 Integration testing using virtualization Feature teams complete integrated features Testing is done in the sprint
  17. 17. Traditional test managers spend time on… 17 Test Policy Test strategy (for the team, the project, the organization) Budget & Resourcing PRA Environment Planning new releases to test Release Advise Test report Progress report Fight for quality (with …) Connect (with e.g. Release management) Defect Triage Staff tasks like Team lead, Education, etc TPI Tooling and Automation
  18. 18. Honesty Call 18
  19. 19. Workshop with Jan Jaap Cannegieter 19
  20. 20. Results of the dot voting 20 Developing Craftmanship Multiple teams Acceptance manager Integration Guarding Quality Specific tests like Performance/Security Compliance officer Manager Test pool Domain expert 0 5 10 15 20 25 30 35 40
  21. 21. Settings where TM adds value Meeting compliance and regulations Coordinating teams working on the same project Responsible for acceptance Responsible for the integration test Manager of a test pool Development of test craftsmanship 21
  22. 22. Meet our crew 22 Acceptance Multiple teamsIntegration
  23. 23. As overall test manager I ensure that all the teams in the project are working on the right tests So that we reduce overlap, prevent gabs and the teams work efficiently on the overall quality 23 Multiple teams
  24. 24. Tasks and activities • Define the overall quality strategy • Watch over the boundaries between teams • Perform risk analysis and monitor risks • Make sure the DoD’s of teams are in line with each other • Monitor test coverage • Monitor that all teams do (non-functional) testing professionally • Help teams to reach an acceptable level of testing • Tune test approach of the teams • Make sure end-to-end testing is done
  25. 25. Agile Quality Strategy 26 What needs to be tested Steering committee Dashboard/ Roadmapping Auditing the test work Coaching the testing team members Organizing tests that do not fit the sprint We still need a plan to know were complete There is a need feedback and traceability (comfort & adaptivety) Testing needs be of quality to justify itself Testing needs to add value to hold up an release
  26. 26. Benefits • Enhance overall quality (E2E) • More risk control • Create transparency (quality and progress) • Prevent double work or gaps • Take away bottlenecks • Efficiency – teams become more efficient • (NOT: more uniformity in the way teams test)
  27. 27. Acceptance 28
  28. 28. As Acceptance manager I ensure that we all parties focus on the right things and know what is needed for the formal acceptance of the solution So that we succeed our mission without late surprises 29 Acceptance
  29. 29. Acceptance manager When applicable • One system that support different parts of the organization • Not one PO that has the authority to decide • When working with different suppliers • Political environment Benefits • Different parts of the organization and suppliers are involved • Working towards a clear goal • Clearer acceptance criteria upfront
  30. 30. Tasks and activities • Elicitate the acceptance criteria • Make sure acceptance criteria are taken into account • Make sure acceptance criteria are used in testing • Stakeholder management • Keeping track on progress during the project • Stimulate collaboration between parties • Become a trusted wing partner
  31. 31. Experience: building an mobile network 32
  32. 32. 33
  33. 33. It ain’t done until its accepted 34 Witness Development en Tes ng Tested solu on Witness report Customer
  34. 34. Witness proces 35
  35. 35. 36 Transparency
  36. 36. As integration manager I ensure that we maintain a focus on integration of component and systems So that customer journeys can be completed and we actually deliver value 38 Integration
  37. 37. Integration Manager When Applicable • Project or changes that involve multiple systems • Organization is not yet completely on DevOps Benefits • Better Quality and user experience • Early detection of Integration problems • Sharing knowledge on system landscape • Bridging between teams • Better efficiency and saving money 39
  38. 38. Tasks and activities • Managing environments • Advising tooling and virtualisation • Version and configuration management • Scrum of Scrums • Communication and advising teams • Drafting customer journeys and scenario’s • Quality ambassador • Tracking progress, auditing test quality
  39. 39. 41 Experience story: Energy Market
  40. 40. Architecture • What are the business processes? • What are the components? • What are the interfaces? Acceptance criteria • What is the Minimal Viable Product? • What integrations are needed to make it work? Requirements traceability • When are we complete? • How do test results add up to acceptance? 42 Missing
  41. 41. What should a car minimally do? 43
  42. 42. Planned Integration Tests 44 Integration tests Release Date
  43. 43. Ensuring Integration (rough sketch) 45 Organization Component System Service Continuously (in the sprint) Occasionally (e.g. prior to a release)
  44. 44. Synergy 46
  45. 45. 47
  46. 46. Do’s and Don’ts (workshop results) 48 Do • Coach the teams • Build bridges • Give teams responsibilities • Create transparency • Align with e.g. PO’s • Create clear quality requirements • Talk with testers (1:1) • Be approachable • Help and Advice • Audit • Helicopter view • Be a quality ambassador Don't • Micro management • Telling people what to do • Interfere with team internal affairs • Short term focus • Tunnel vision • Combined functions (tester + manager) • Difficult complex reports
  47. 47. 49 Develop Craftsmanship
  48. 48. 50 Develop Craftsmanship As Practice lead I ensure that we exchange experiences and develop our profession So that we keep adding value and excel as testers
  49. 49. Development craftmanship When applicable • Big organizations with different testers • Testing important for the business • Organizations that invest in their employees Benefits • Enhanced craftmanship • Better, more professional testing • Happy testers • More happy customers • Save money and time 51
  50. 50. Tasks and activities • Coach testers • Organize knowledge sessions • Organize courses • Stimulate that testers visit conferences • Keep your own knowledge up-to-date • Test when necessary • Manage knowledge • Organize that testers share knowledge • Manage test community • Promote the importance of testing
  51. 51. Other crew members Compliance officer and Manager of the test pool 53
  52. 52. Finale 54
  53. 53. Quality is embedded in agile development 55
  54. 54. Role is changing 56 Traditional test managers spend time on… 15 Test Policy Test strategy (for the team, the project, the organization) Budget & Resourcing PRA Environment Planning new releases to test Release Advise Test report Progress report Fight for quality (with e.g. the project manager) Connect (with e.g. Release management) Defect Triage Staff tasks like Team lead, Education, etc TPI Tooling and Automation
  55. 55. Value as a test manager 5757 Acceptance Multiple teamsIntegration Develop Craftsmanship
  56. 56. 58 Show your worth
  57. 57. We need less of them… Test manager Test Engineer 59
  58. 58. 60 Related roles
  59. 59. 61 So be good…. or grow into a new role
  60. 60. 62
  61. 61. Benefits of this webinar We looked at  the activities of the Test manager  the settings where a Test manager has value  how to make a difference  alternative roles 63
  62. 62. Derk-Jan Valori Coltbaan 4a 3439 NG NIEUWEGEIN The Netherlands • derkjandegrood@valori.nl • +31(0)651807878 • www.valori.nl • @DerkJanDeGrood • http://djdegrood.wordpress.com 64

×