There’s a piece of North American folklore about John Henry, who was a manual laborer during the expansion of the railroads in our country. His job was being replaced by steam-driven heavy equipment, as the railroad industry applied technology to become more efficient. The same dynamics are happening today with manual testers. We need to make sure that manual testers avoid John Henry’s fate – read on to see why.
Requirements / Requirements gathering / Software development / Testing
Posted on:
Quality and Requirements – You Got Chocolate In My Peanut Butter
Quality writers are writing about requirements. Requirements writers are writing about quality. Just like the Reese’s Peanut Butter Cup – Two Great Tastes that Taste Great Together. You can’t have one without the other.
Agile / Prioritization / Project Management
Posted on:
Agile Prioritization and Tracking
Stealing a couple cool ideas for managing project priorities with something you can touch.
Agile / Process Improvement / Requirements gathering / Software development
Posted on:
Agile Argument
Another challenge to a premise of agile comes in a well assembled argument from Tony at Seilevel, in his article, Agile…again.
Process Improvement / Product Management / Requirements / Requirements management software / ROI / Software development
Posted on:
Companies Will Waste $1B This Year on Software Tools
Gartner reported that companies spent $3.7 Billion USD on application development tools in 2004, with a 5% annual growth rate. The Standish Group has shown that 40% to 60% of project failures are due to requirements failures. At least 1/3 of the money spent on getting more efficient at coding is being wasted – it should be spent on writing the right software.
Product Management / Requirements / Software requirements specification / Testing / Writing
Posted on:
Writing Verifiable Requirements
One of the ten big rules of writing a good MRD is writing verifiable requirements. Verification is both a function of having a precise goal, and having the ability to affordably measure the requirement. A precise goal is a verifiable requirement if we can clearly answer “yes” or “no” when asked if the requirement has been implemented. We also face the practical realities of being able to measure the results profitably.
Design / Product Management / Requirements / Software development / Software requirements specification / Writing
Posted on:
Writing Design-Free Requirements
One of the ten big rules of writing a good MRD is writing requirements that do not specify design. How do we specify enough detail to be actionable without constraining the engineering team? How do we trust our developers to do the right thing? The Big Rule of Avoiding Design-Agnosticism […]
Interaction design / Product Management / Requirements / UX
Posted on:
Writing Valuable Requirements
One of the ten big rules of writing a good MRD is writing valuable requirements. How do we determine what requirements are valuable? To whom are they valuable? When a requirement represents a continuum how much is enough? What is too fast, what is too scalable? To whom must the requirement be valuable?
Software development / Test Automation / Testing
Posted on:
Test Smarter, Not Harder – A Detailed Article
A detailed (15-page) article by Scott Sehlhorst showing how to incorporate test automation for complex software has been published at developer.*. This article shows the math, benefits, and weaknesses of traditional approaches to automating functional tests. The article also proposes improvements to the process, rethinking the problem to provide innovative solutions. This post discusses the background for the article and provides an overview, as well as links to related content.