Archive for the "Validation/Testing/UAT" category

Requirements in the News: Prison security system fails and releases Florida prisoners from cells

Poor requirements too often result in delay and expensive rework, but in the case of a Miami prison that repeatedly released all of its maximum security inmates from their cells, missed requirements caused serious injury. As reported by Wired Magazine, on two separate occasions the doors of Turner Guilford Knight Correctional Center in Miami, Florida [...]

Measuring the Effectiveness of a Feature

There are two possible outcomes: if the result confirms the hypothesis, then you’ve made a measurement. If the result is contrary to the hypothesis, then you’ve made a discovery. Enrico Fermi There are four key factors that determine how effective any feature is in achieving its design objectives. They are: Discovery, Comprehension, Execution and Performance. [...]

What do you do when your product passes UAT and fails when it’s released?

Let’s say you’ve been engaged in a project that’s much needed by the company. Let’s say that it has had a past filled with failure. Let’s say that it’s on the chopping block to be cut, due to being a seemingly money pit. Let’s say that you’re on a super awesome team to turn the [...]

A Business Analyst’s Checklist for User Acceptance Testing

A while ago, Joy wrote a post about how to prep for a UAT (User Acceptance Testing). I would like to add to that, with my own experience, for what is needed in order to prep for a UAT.   I had a client once who was building an internal software product, failed their UAT, [...]

Tips for Business Analysts: Requirements Documentation, Working Memory and Reviews

Everyone hates going through and reviewing large documents – no one wants to sit down and read a 300 page software requirements specification (SRS) or business requirements document (BRD) and provide feedback. However, it is a necessary task! How else will the business know that they are getting what they want? How else will developers [...]

Incorporating the Software Test Team into the Software Requirements Creation Process – Part 3

This is the last post in a series on “why incorporate the test team into software requirements creation earlier” – for the first post, click here; for the second post, click here. In the first part of this series on the role Testers can and should play in the requirements creation process, I stated that [...]

Incorporating the Software Test Team into the Software Requirements Creation Process – Part 2

This is the second post in a series on “why incorporate the test team into software requirements creation earlier” – for the first post, click here. The downsides to not integrating the Test organization into the requirements creation process are rework, schedule slippage, scope changes and budget overruns. Bringing the Test team into the picture much [...]

Incorporating the Software Test Team into the Software Requirements Creation Process – Part 1

A lot of the popular literature, training, documentation and processes related to the management of Software Requirements in an organization are typically focused on two constituencies – Users and Developers – and thus miss an important constituency, Testers. User is the catch-all term for anyone who may use the software being created. They typically define [...]

A Layman’s View of a Great Tester

Over the last six months our project has deployed 2 major releases and 2 minor releases. Depending on how your organization is structured, Requirements analysts may or may not be part of the testing efforts. I have been fortunate to work closely with the testing teams as we tested and eventually deployed our solution. I [...]

A (Failed) Humorous Attempt: How to Write the Imperfect User Story

As a User Story, I should not have an actor for my user story. I’m not too certain if a user story is still a user story if the story…lacks a user. As a User Story, I must use systems as my actor. Hey! Systems can be actors too! The only issue is…how do you [...]