Software Quality Testing

Software Quality Testing is a Blog dedicated to extensive Software Quality Assurance and Software Testing information. This is intended to be an one-stop Information Center for all your Software Quality and Testing needs.

 
Weather
Click for Chennai (Madras), India Forecast
My Ballot Box
My Ballot Box
Which suite of Automation tool do you use while testing?

Mercury
IBM's Rational
Silk
Open Source Tools
Never use Tools


View Results
Hot Updates

:: Bug Free Zone ::

Translate
Sponsored Links
Other High Rated Testing Blogs
All Time Best Testing Articles
Technorati
Discussion Board
Visitor Count
Visitor Locations
Locations of visitors to this page
Play Sudoku



free+games free+online+games download+games
Timers
Subscribe

Enter your email address:

Delivered by FeedBurner


Add to Google Subscribe in Rojo Subscribe in NewsGator 
Online Subscribe in podnova Subscribe in FeedLounge Subscribe in Bloglines Add to netvibes Add to The Free Dictionary Add to Bitty Browser Add to Plusmo
Powered by

Page copy protected against web site content infringement by Copyscape BLOGGER

Site Score
Silktide SiteScore for this website Blogrolling.com Hot 500
FireFactor
How to handle Late Requirements !
Tuesday, January 02, 2007
Many of project issues are related to bad requirements management. One particular issue which is hard to tackle is the handling of late requirements.
Coping with new requirements after the development has started often leads to problems in the project:

1. schedule, cost and scope of the running project become unknown
2. delays due to unsufficient impact investigation, which may propagate to other projects in the program.
3. rework of finished development
4. quality problems, unsufficient time left for testing
5. lost accountability of the development team
6. drifting morale
Before starting with the implementation of late requirement, do a feasability study including an impact analysis on the cost, schedule, and scope of the project.The following alternative solutions can be offered for development to handle the late requirements:

1. Define a separate update release for the late requirements
2. Leave room in the original plan to handle late requirements
3. Prioritise requirements, leave some priority 2 requirements out to make room for the new requirements. Apply this technique Only when effort is not too big, ie less than 10% project size, and if you have good configuration management practices to take code out again after coding has started.
Late requirements do not have to end with project chaos, they can be handled in a disciplined and controlled way.
Posted @ Tuesday, January 02, 2007  
0 Comments:
Post a Comment
<< Home
 

Back to Top
Bookmark This Site
Previous Post
Archives
Software Testing Links
Quality Assurance Links
Latest Security Alerts
Sponsored Links
SIX SIGMA Links
Project Management Links
Software Estimation & Measurement Links
Sponsored Links
Tips for Job Seekers
Listed
ServTrek
Killer Directory
Site Load Testing Tool
Quick Register
Search Engine Ginie
One Way Link directory
Software Testing Zone
DaniWeb Best blogs on the Web: all about WWW Computers Blogs - Blog Top Sites Top Blogs Software blogs Blog Flux Directory Free Blog Listings @ Blog Annoucne Find Blogs in the Blog Directory PHP Blog Manager - Free Blog Directory Bloggapedia - Find It! World Top Blogs - Blog TopSites
Blogarama - The Blog Directory BlogElites.com
© Copyright 2006 Debasis Pradhan . All Rights Reserved.