requirements

Articles

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.

Laura Brandenburg's picture Laura Brandenburg
Secrets About IT Projects 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.

Allan Kelly's picture Allan Kelly
Software Customer Project 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.

Brad  Egeland's picture Brad Egeland
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.

Naomi Karten's picture Naomi Karten
adzic cover 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.

Gojko Adzic's picture Gojko Adzic
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
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.

Fiona Charles's picture Fiona Charles
How to Build a CM and ALM Strategy

Joe Farah writes that a next-generation CM and ALM strategy may seem aggressive, but it will help ensure that you're happy with the result. It will make sure that you deal with the entire problem domain from an organization perspective, rather than just the part your team is traditionally comfortable with.

Joe Farah's picture Joe Farah
flow chart Four Agile Tips to Eliminate Rework in Application Development

Your applications need to meet business needs, overcome complex processes, and provide instant results to customers. And, ideally, they’ll require minimal rework on your part. The first step to success is requirements definition. Here, Filip Szymanski offers some tips from agile methods that will improve your requirements—even if you haven’t otherwise adopted agile.

Filip Szymanski's picture Filip Szymanski
The Satir Interaction Model Why Not Ask Why? Get Help From the Satir Interaction Model

Having trouble with responses to why questions? Get help from the Satir Interaction Model and learn when to use data-oriented questions.

Don Gray's picture Don Gray

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.