• Consultancy
    • Digital Transformation
    • Organisational Agility
    • Digital PI Planning
  • Agile Training
    • Scaled Agile (SAFe)
    • Scrum Training
  • Agile Teams
  • Tooling
  • Insights
  • About Us
    • Our Work
    • Contact
    • Join Us
AgilicistAgilicist
  • Consultancy
    • Digital Transformation
    • Organisational Agility
    • Digital PI Planning
  • Agile Training
    • Scaled Agile (SAFe)
    • Scrum Training
  • Agile Teams
  • Tooling
  • Insights
  • About Us
    • Our Work
    • Contact
    • Join Us

Agile

  • Home
  • Blog
  • Agile
  • 7 Pitfalls to Agile Testing

7 Pitfalls to Agile Testing

  • Posted by Admin
  • Categories Agile
  • Date 2016-01-20
  • Comments 57 comments
Agile testing

“Whether your company is working in waterfall or agile, your testers will have the same basic skill-set and knowledge, the real difference is in their way of working.”

Those testers who are used to working in an organisation that delivers projects in waterfall will be used to receiving a set of requirements early in the project and building their test cases around these before receiving an operational system to test.

In agile, testers are expected to be contributing to the fleshing out of requirements and then testing these without formal requirements documentation. They should also be comfortable testing code that is constantly changing in near real time and happy to operate as part of an agile team.  That agile team continuously produces value, at a sustainable pace and is able to quickly adapt to the business’ changing requirements.

When transitioning from waterfall to an agile approach, it is vital to address the following seven testing pitfalls, which, if not addressed can derail the entire transformation:

Table of Content

  • 1. Not integrating testers into dev teams
  • 2. Waiting for sprintly builds
  • 3. No input into requirements
  • 4. Manual regression testing
  • 5. Maintaining a traditional testing mindset
  • 6. Not keeping up with the Joneses
  • 7. Forgetting the bigger picture

1. Testers are not integrated into development teams

Traditionally, the test team sat outside of the development team and were independent. In agile they must be integrated into the teams.

Are testers not being invited to meetings between developers and business users to discuss stories, or more subtly, are they being invited only to be told they cannot contribute to the discussion?

One of the biggest risks here is that the tester doesn’t know whats going on; changes are made to the story and the tester is unsure how to test them resulting in rework and animosity. When the tester misses out on story conversations there can be a tendency to simply test the developer’s build without thinking about the requirements.

Tag:agile development, agile testing

  • Share:
author avatar
Admin

    Previous post

    Is The SAFe Framework worth doing?
    2016-01-20

    Next post

    Why Should Teams Write Objectives?
    2019-12-09

    You may also like

    Death of Scrum
    The Death of Scrum
    29 July, 2020
    canoeing-3600550_1920
    Six reasons behind a small team size
    20 January, 2016

    Leave A Reply Cancel reply

    Your email address will not be published.

    Latest Posts

    Rowing boat
    Six reasons behind a small team size
    20Jan2016
    Is Scrum collapsing?
    The Death of Scrum
    29Jul2020
    Should I renew my certification?
    Do I need to renew my scrum master certification?
    22Jul2020

    Categories

    • Agile
    • SAFe
    • Scrum
    This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Cookie settingsACCEPT
    Privacy & Cookies Policy

    Privacy Overview

    This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
    Necessary
    Always Enabled

    Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.

    Non-necessary

    Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.

    • 02033222296
    • info@agilicist.com