The Four Cs and One T of Requirements “Testing”

Evgeny Tkachenko

[video: width:300 height:200 align:right]

It is important to know that written requirements are good, but few employ a practical, repeatable approach for “testing” their requirements. Evgeny Tkachenko says his company has introduced a requirements analysis step which is done before coding of functionality begins. Checking for requirements completeness, clearness, correctness, consistency, and testability helps ensure that developers create the right features the first time. To demonstrate this process, Evgeny presents examples of buggy requirements and plays games with participants who solve logic puzzles to practice finding inconsistencies in requirements. He describes a set of guidelines for requirements analysis—having an analytical mindset, asking questions of product owners, tracing requirements to tests, paying attention to non-specific wording, using heuristics, and being guided by common sense and experience. Whether your team captures requirements in user stories or traditional formats, join Evgeny for new insights, tools, and practices to improve your requirements.

About the Presenter

Evgeny Tkachenko has more than eight years of experience in test management, automation testing, and release management, mainly on complex projects in the telecommunication, financial, and online entertainment industries. Previously his experience as a test manager in Russia’s most important technology center gave Evgeny a unique perspective in test process development. Now at EPAM Systems in the Unites States he applies his experience and expertise to do whatever is required to deliver the highest quality product possible. Evgeny is a frequent speaker at QA/Dev/Agile conferences in the US and Europe, and an author for international test and QA publications.

Upcoming Events

Apr 28
Jun 02
Sep 22