requirements gathering

Articles

Hoarding: How to Prioritize Features to Clean Up the Clutter
Hoarding is an incredibly common—but usually unnamed and invisible—phenomenon in corporate software development. If you’ve been doing agile for a while, you are no doubt aware of the cost of hoarding and you’ve probably removed much of it, but what happens when you aren't doing agile yet? Clarke Ching explains how to counter hoarding by prioritizing the right features.
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.
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.
Kill By Wire
Linda Hayes has worked in the software industry for a long time and through a lot of changes. But a series of recent events has led her to question whether the industry has changed for the better or worse. In this article, she recommends some attitudes we should lose and some we should adopt in order to save our software and--in some cases--our lives.

More

Better Software Magazine

Managing Your Analysis Debt

What is your project's analysis debt load? What's the difference between good and bad analysis debt? What are causes and remedies for such debt? Mary Gorman and Ellen Gottesdiener explore the concept of analysis debt and consider strategies for prudent investing.

The Whos and Wheres of Stakeholder Requirements

Whether you're working on a collocated or a distributed team, it's important to take stakeholder requirements into account: "Who" are they and "where" are they located? In this article, Mary Gorman offers some tips to help you narrow the gap between thinking and acting globally and locally.

How Agile Practices Reduce the Top 5 Requirements Risks
Requirements risks are among the most insidious risks threatening software projects. Whether it is having unclear requirements, lack of customer involvement in requirements development, or defective requirements, these troubles are a major culprit in projects that go awry. As requirements expert and agile coach Ellen Gottesdiener explains, agile practice can go a long way in mitigating the top 5 requirements risks.
Do You Know Why You Are Doing That?

It's easy to get caught up in the inertia of a project and forget to ask exactly what we are developing, who our customers are, and what their goals with our software might be. Few software projects have the time and budget to figure out what their project is through trial and error. Getting clarity on project focus not only helps productivity, working to create software that people actually need increases our chances for success.

Building a Foundation for Structured Requirements

Aspect-oriented requirements engineering (AORE) is a new methodology that can help us to further improve the analysis, structure, and cost of development of software requirements. The second part of this two-part series focuses on the AORE specification techniques.

Building a Foundation for Structured Requirements, Part 1

Aspect-oriented requirements engineering (AORE) is a new methodology that can help us improve the analysis, structure, and cost of development of software requirements. AORE does not replace but rather complements any of the existing requirements methodologies. This two-part paper explains to software practitioners the AORE concept, illustrates how it can be applied on software projects, and discusses the benefits of AORE. Part I focuses on the AORE analysis techniques.

What Goes Up Must Come Down

Writing requirements purely top-down or only bottom-up is risky to say the least. The devil's in the details, and those details are likely to be missed when working from a single direction. What if you could tackle your requirements from both directions by incorporating use cases and user centered design? Learn how balancing your approach to writing requirements can result in more detailed, pragmatic documentation.

More

No matching content found for tag requirements gathering.

TechWell Stories
To Estimate or Not to Estimate—That Is the Question
Removing Waste in Software Projects
Create a Vendor Contract While Keeping Agile
How Agile Teams Use DevOps for Deployment
Build a List of Things—But Don't Call It Agile

Recommended Web Seminars

May 29 How to Integrate Performance Testing into Agile and Hybrid Environments
Jun 11 Test Infrastructure Changes as Easy as Pressing Play
Jun 18 Adopting Agile and Moving into the Future
On Demand 7 Habits of Highly Effective Agile Teams
On Demand Achieve Scriptless Test Automation Utopia!

Featured Resources

» An Innovative Approach to Integration Testing | IBM Rational
» Improve Quality and Decrease Time to Market with Requirements Management | PTC
» Perfection Just Became Mobile: An Easy-to-Use Solution for Mobile App Testing | Micro Focus
» Performance Testing in the Cloud | J9 Technologies
» Improving Test Automation for Visual Studio Projects | LogiGear

Visit Our Other Communities

The home for software testing and QA professionals—practical advice on test automation, test management, test techniques, and more.
Where configuration management and development professionals go for answers on SCM, ALM, change management, DevOps, tools and more.