Identifying, documenting, and communicating requirements are key to all successful IT projects. Common problems in requirements engineering are How do we discover the real requirements?, How do we document requirements?, and How do user stories, use cases, and epics fit into requirements? Erik van Veenendaal answers these questions and more while helping you improve your skills in requirements engineering for both traditional and agile projects. With practical case studies and hands-on exercises, Erik illustrates requirements issues and solutions. Practice finding, specifying, and evaluating traditional requirements and user stories while learning how to gather information through varied elicitation techniques. Explore the advantages and disadvantages of each technique. Learn a rule set for determining how much documentation you need for “good enough” requirements. Explore requirements review techniques—walkthroughs and inspections—to determine what will work best for you. Create a set of Golden Rules for requirements engineering that your project can use.
Erik van Veenendaal
A leading international consultant, trainer, and recognized expert in software testing, Erik van Veenendaal (erikvanveenendaal.nl) is the founder of Improve Quality Services BV, a company that specializes in testing, requirements engineering, and quality management. Erik is the author of a number of books and papers, a core developer of the TMap testing methodology and the TMMi improvement model, a participant in the International Requirements Engineering Board working parties, currently on the TMMi Foundation board, and a frequent speaker at international testing conferences. For his major contribution to the field of testing, Erik received the 2007 European Testing Excellence Award.
Many projects implicitly use some kind of risk-based approach for prioritizing testing activities. However, critical testing decisions should be based on a product risk assessment process using key business drivers as its foundation. For agile projects, this assessment should be both thorough and lightweight. Erik van Veenendaal discusses PRISMA (PRoduct RISk MAnagement), a highly practical method for performing systematic product risk assessments. Learn how to employ PRISMA techniques in agile projects using Risk Poker. Carry out risk identification and analysis, see how to use the outcome to select the best test approach, and learn how to transform the result into an agile one-page sprint test plan. Erik shares practical experiences and results achieved by employing product risk assessments. Learn how to optimize your test effort by including product risk assessment in your agile testing practices.