Agile projects focus on very lightweight, simple requirements embodied in user stories. However, there are some problems with relying solely on user stories. They often don't contain enough accuracy for development, testing, or industry regulations. There's a better way to write detailed requirements that are still agile.
Adam Sandman was a programmer from the age of 10 and has been working in the IT industry for the past twenty years in areas such as architecture, agile development, testing, and project management. Currently Adam is a director of technology at Inflectra Corporation, where he is interested in technology, business, and enabling people to follow their passions. At Inflectra, Adam has been responsible for researching the tools, technologies, and processes in the software lifecycle management space. Before Inflectra, Adam was a director at business and technology consulting firm Sapient.
All Stories by Adam Sandman
With API testing, if you change how the API works—even if it now works better—it will break all of the code written by people using the API. Consequently, testers have a responsibility to make sure they are testing the same contract that was established when the API was first released. Here's how to test APIs right.