|
|
sponsored by Hewlett-Packard Company
|
|
|
Posted:
|
05 Mar 2012
|
|
Published:
|
01 Mar 2012
|
|
Format:
|
PDF
|
|
Length:
|
7
Page(s)
|
|
Type:
|
eGuide
|
|
Language:
|
English
|
|
|
ABSTRACT:
Tracking requirements changes within Agile development can be tricky, which begs the question of whether or not it's a good idea to use an Agile methodology for fixed-price contracts where requirements must be defined upfront. Answering the question, "What is the best way to track changes to requirements?" in today's environments depends on many variables and will be entirely unique for different development teams.
This e-guide provides expert guidance on requirements management in Agile development. Read it to find best practices for contract negotiation and tracking changes the Agile way.
|
|
|
|
BROWSE RELATED
RESOURCES
Application Development | Application Life-Cycle Management | Software Development Life-Cycles | Software Development Methodologies | Software Project Management
|
View All Resources
sponsored by Hewlett-Packard Company
|
|
|
|
|
|
TechTarget provides enterprise IT professionals with the information they need to perform their jobs
- from developing strategy, to making cost-effective IT purchase decisions and managing their
organizations' IT projects - with its network of
|
|
|
Definitions:
|
|
 |
|
All Rights Reserved,
Copyright 2000 - 2013, TechTarget |
|
|
|
|