 RM Articles
RM Articles provides original articles from industry thought
leaders, analysts and software providers on a wider variety of requirements management and requirements reuse topics
 Get the Feed | Subscribe by Email
|
 Requirements
management is hard work. It can also be frustrating, complex and
unfortunately also the source of serious problems that endanger a
project as well as the team trying to get their arms around the
software and systems requirements that must be met in order for the
effort to be a success. There are also a few key points that should be
kept in mind when starting any requirements management effort. Read on
if you would like to be a success with your Requirements Management!
|
 It's all about the requirements. Say otherwise and I'll turn my back on you seeking someone who isn't either insane or intoxicated. --- Perhaps a bit overstated, but I am a requirements bigot. I have focused on requirements as the source of all things good and the root of all evil since the mid 1960's when I wrote the first PSL / PSA.
|
|
Robin F. Goldsmith, JD
17 Feb 2009 | SearchSoftwareQuality.com
For something that is essential, fairly fundamental and seemingly straightforward, requirements-based software testing sure does generate a lot of discussion. Rather than representing opposite extremes of the same continuum, pro and con camps come at the topic from disparate perspectives. Advocates of requirements-based testing tend to be analytical, whereas opponents tend to couch their objections in more emotional terms. Each approach has its own strengths and issues. We'll start by ...
|
|
Many people think you don't "do" requirements on an agile project. Hogwash. Indeed, agile projects use requirements-but just enough requirements at just the right time.
In this article by author Ellen Gottesdiener, Principal Consultant at EGB Consulting, Inc., she argues that requirements do matter, and that Agile projects shouldn't abandon requirements management. Taking a light weight approach to requirements management on large agile projects saves time and money and accelerates the team's ability to deliver the right product, sooner.
Read the article
|
 Author: Doug Akers
The main benefit of today’s Agile development methodologies such as Scrum or XP is the promise of delivering more in a shorter period of time and the value derived from having the flexibility to adjust your course mid-way through a development effort. But does this type of approach allow for requirements management? Is RM necessary given the shorter development windows – sprints, milestones, stories, whatever you call them?
Well -- does the need to deliver what the requirement originally requested go away? Does the desire to control change to the requirement go away? Of course not, and neither does the need for requirements management under these newer methodologies. The nature of RM will change, certainly, but the fundamental principles will not.
|
 Author: Bob Aiello
There has never been a more exciting and rewarding time to
be in the industry of systems application development. There also has never
been a time when the risks were greater and the margin for error more critical
- you must get it right or your failure will make headlines the next day. From process
workflow, application requirements, source code management, through setting up
a seamless deployment strategy - MKS leaves a lot of its competitors stunned by
its full set of features and versatile comprehensive solution. If you are a
development manager and you want to get your projects under control than you
should take a serious look at MKS Integrity 2007. Read on if you want to learn
more about this process and workflow platform that can set the stage for your
large scale development effort to be a success in terms of meeting your
deliverables on time and within budget.
|
|
<< Start < Prev 1 2 3 4 Next > End >>
|
| Results 1 - 6 of 20 |
