Does This Sound Familiar?

  • Lack of Centralization

    Too many folders, too many documents and spreadsheets overwhelming and slowing down your testing efforts

  • Managing Cumbersome & Overly Complex Workflows

    “Click this, then click that, then check this value and update here, comment there” type test documentation

  • Impossible Spreadsheet Management

    You spend more time updating spreadsheets than actually testing while constantly on the hunt for data about a project

  • No Visibility Into the Health & Status of a Project

    It’s near impossible to get a feel for a product based on a statement like “There are currently 2 high severity, 23 medium, and 4 low bugs in this build”

Everyone Shares The Spreadsheet Pain

Excel as a testing documentation tool starts out powerful and effective, grows in usage throughout a group, then, just after it becomes essential, it slowly begins to choke productivity, leading to diminishing returns.

Pain for Testers

Excel is creating problems, slowing us down and project wide inefficiencies

  • We’re spending more time documenting, organizing and managing our testing assets than we are testing
  • Test schedules overrun because of a comprise on documenting our test activities to achieve Quality Testing
  • Test cases and defects slip through the cracks – too many email attachments and spreadsheets to dig through
  • Lack of visibility into whether or not a requirement, platform, version or component/module of an application is tested

Keeping a Pulse on Projects is a Nightmare

Keeping a pulse on a project involves digging through emails, and plumbing the depths of Excel files stored in different places for different teams

  • I need a more efficient way to communicate performance and quality to by boss
  • I have little to no visibility into overall team performance and the performance of the individual testers
  • I’m constantly on the hunt about data for a project and am forced to collect it in different formats and in different places

Organizational Dysfunction

  • Testers are spending more time working around, organizing and updating documents than testing software
  • Managers are spending more time on work that that isn’t facilitating a release
  • Lack of or very little visibility into testing puts releases at risk for post production bugs, which can lead to revenue loss and customer dissatisfaction
  • Spreadsheets are blocking our ability to effectively collaborate

Things Happen for a Reason

The Road To Excel Hell May Have Been Unavoidable

  • Let's Use Excel

    Everyone has a spreadsheet on the desktop; there is nothing to buy, install, or argue about with purchasing or IT

  • It seems like a good idea at first

    You want to understand what is happening in testing - to get your arms around it. So you create a spreadsheet

  • New Features = New Spreadsheet

    Each new release involves copying all the spreadsheets, putting them in a folder to mark the current release, then going into each spreadsheet and checking them off

  • Who's doing what?

    Tracking who is doing what, of course, takes another spreadsheet, plus possibly a slew of other spreadsheets to track bugs

  • Soon you're drowning in spreadsheets

    The very thing that was supposed to create order has created the haystack syndrome, where everything you need to know is in a spreadsheet ... if you can only find it

  • Documentation Becomes A Disaster

    Testers are likely spending more time working around and updating the documents than testing software

  • Visibility Breaks Down

    Keeping a pulse on the project takes a combination of reports emailed in, checking the bug reporting system, and plumbing the depths of Excel files stored in different places for different teams

  • Welcome To Excel Hell

    Before you know it, you are in Excel hell, the intersection of testing documentation burden, and time pressure

Get Out of Excel Hell with qTest