In this Update, we explore how to collect and communicate contextual information, increasing the odds that customers will see value in software and willingly adopt it. The same principle applies to contextual information that applies to any kind of requirements insights: the type of information needed, and the medium for communicating it, varies according to the question asked. Therefore, software professionals need to develop a toolkit of techniques that will vary across teams, projects/products, organizations, and time, since the same questions do not arise for everyone.
Executive Update
Collecting and Testing Contextual Knowledge Requires a Toolkit Approach
By Tom Grant
Posted May 14, 2015 | Leadership |
About The Author
Tom Grant is the former Practice Director of Cutter Consortium's Agile Product Management & Software Engineering Excellence practice. Dr. Grant's expertise in software development and delivery with a particular focus on Agile, Lean, application lifecycle management (ALM), product management, serious games, collaboration, innovation, and requirements.
Most recently, Dr. Grant was a Senior Analyst at Forrester Research. Previously, he served… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.