Requirements
Articles
Designing Products for Users in Context When designing software, you must look beyond simply knowing the goals of your users. It's far more useful to understand the context in which the product will be used. |
||
Three Ways to Talk When You Are Listening We know listening is important—typically it’s what our stakeholders have to share that we most need to hear when eliciting and validating scope or requirements. At the same time, as business analysts, we cannot be passive flies on the wall. |
||
The Power of “Pull” Conversations My team has been looking for ways to make sure we understand what our business stakeholders really want from each software feature that we develop. We felt that we had to solve a basic communication problem but didn’t know how to approach that. |
||
True Performance: Moving Beyond Basic Load Testing Basic load testing is valuable, but it's important to move past simplistic efforts. Here are some ways to gain more accurate metrics from your load tests. |
Jim Holmes
June 18, 2012 |
|
Dear Customer: The Truth about IT Projects In this personal and direct letter to customers, Allan Kelly pulls no punches and explains why IT projects don't always pan out for all of the parties involved. |
||
Question Your Project Customer When leading technical projects, project managers and their teams know the task ahead can be a daunting one. So, when the customer comes with a desired solution mapped out and detailed requirements in hand, the first thing you want to do is move forward. That's your cue to start asking questions. |
||
An Obvious Bug or a Deliberate Strategy? What first may appear to be an obvious bug, may not be after all. Closely looking at a recent experience shopping online revealed what first seemed like a bug, but could also have very well been a cleverly placed, well-executed sales strategy. |
||
Specification by Example: Collaborating on a Scope without High-Level Control Understanding what the business users are trying to achieve can significantly help you focus the project on things that really matter. In this excerpt from Gojko Adzic's book Specification by Example, the author offers some tips for effectively collaborating on the project scope when you don’t have high-level control of the project. |
||
Agile Requirements Management with Keith Johnson Keith Johnson is vice president of product development at Jama Software. in this Sticky ToolLook interview, he discusses some of the changes that agile development has brought to the requirements management process. |
TechWell Staff
December 7, 2011 |
|
Tester, Know Your Product Should you diligently produce multiple big documents before testing begins? Consultant Fiona Charles argues that you should do that only if you believe that documentation is your product as a tester. If your product is information, you should instead minimize test documentation and engage with the software to build the product your stakeholders are paying for. |
Pages
Recommended Web Seminars
Mar 28 | The Testing Practices Fueling High-Performing Software Teams |
On Demand | Building Confidence in Your Automation |
On Demand | Leveraging Open Source Tools for DevSecOps |
On Demand | Five Reasons Why Agile Isn't Working |
On Demand | Building a Stellar Team |