Error message

Warning: Invalid argument supplied for foreach() in field_view_mode_settings() (line 627 of /var/www/communities.techwell.com/docroot/drupal-7.19/modules/field/field.module).

requirements management

Articles

Harvesting Stakeholder Perspectives to Organize Your Backlog
When Mary Gorman and Ellen Gottesdiener facilitated a game called The Backlog Is in the Eye of the Beholder for the Boston chapter of the International Institute of Business Analysis, both the players and the facilitators learned some important lessons in organizing a project requirements backlog. In this article, they describe the game and what it revealed, including the value of truly knowing your stakeholders.
How Agile Practices Reduce 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 those risks.
The Challenge of Enterprise Requirements Management
There are many accepted processes and approaches to managing enterprise requirements. These approaches vary from model-focused to document-focused and are well known and practiced by requirements-gathering specialists throughout the business world. The real intent of any enterprise requirements management organization is to accurately capture and manage needs of the business, and organizations are built to create repeatable processes for doing so. However, once the focus shifts toward processes for eliciting and managing requirements, and away from the business goals, problems can arise.
Building Requirements Quality throurh Coverage and Testability
As we look to deploy or improve a requirements practice, the output should lead to a set of complete and quality requirements. A way to get there is to ensure that requirements have been captured in all pertinent categories and are testable. Often times, requirements focus on user needs and limited functional areas. But what may be overlooked are lesser requirements categories (e.g., security, usability, etc). It is therefore essential to capture requirements that ensure coverage in the requirements space.

More

Better Software Magazine

Simplicity and Precision: Test Planning in Agile Projects
Test planning is often thought unnecessary in an agile project. However, if our mindset is on "planning" rather than "plans," we see that test-planning activities happen throughout the project, taking advantage of levels of precision, i.e., what is absolutely necessary at each level.
Why Do Requirements Matter?

A series of dining mishaps leads Lee to reflect on why mistakes happen in spite of well-defined requirements.

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.
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.

More

No matching content found for tag requirements management.

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 23 Key Principles to Mobile Performance Testing
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

Featured Resources

» Skytap Automation Pack for Microsoft VS Team Foundation Server | Skytap
» An Innovative Approach to Integration Testing | IBM Rational
» Improve Quality and Decrease Time to Market with Requirements Management | PTC
» Cloud-Enabled Software Development and Testing | Skytap
» Performance Testing in the Cloud | J9 Technologies

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.