Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  General  handle scenario
Previous Previous
 
Next Next
New Post 2/12/2012 9:09 PM
User is offline Kochar
2 posts
No Ranking


handle scenario 

  How would one handle a scenario when requirements change midway in the project?

 
New Post 2/13/2012 2:38 AM
User is offline Kimbo
453 posts
5th Level Poster


Re: handle scenario 

Kochar,

One common way is by creating a system of formal change requests that you record, model, estimate changes, track, get approval for, etc  individually. Then prioritise them and execute

Kimbo

 
New Post 2/14/2012 2:47 PM
User is offline Sandy
74 posts
8th Level Poster




Re: handle scenario 

Kochar,

It can also be important to look at why the requirements are now changing.  It's common to find new requirements that just haven't been identified before, or to find changes as requirements become more clearly defined.  These types of changes can be managed very well using the formal change control process that Kimbo described.  However, if you find that previous decisions are being revisited and reversed, or if existing requirements are being questionned or significantly altered then you may need an additional strategy to keep a decision log as well (if you are not already doing so).

It can be very helpful to keep a log of decisions made along the way, as you collect and refine the requirements - particularly when it is decided that a function or requirement isn't needed.  The decision log should include the name/role of the person making the decision and the rationale behind it.  You'll find that stakeholders forget why a certain direction has been taken, and that one person isn't aware of a decision made by someone else.  A decision log helps keep everyone on the same page, helps keep requirements aligned and synchronized, and helps prevent repeated discussions of the same issue.  This doesn't mean that a decision can't be changed or overturned - but just gives more control for making (and enforcing) requirements decisions.

Sandy

 
New Post 2/20/2012 7:44 PM
User is offline KJ
243 posts
6th Level Poster


Re: handle scenario 

Kochar,

the longer the project the more changes you can expect. What should be the question is HOW to manage these changes.

warm regards,

K

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  General  handle scenario

Community Blog - Latest Posts

Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...
The cloud-native application development has helped enterprises all around the globe reduce time-to-market, enhance performance, and develop agility and flexibility. Several enterprises are achieving these results by migrating their systems or traditional monolithic applications to the cloud. But to gain from the real benefits of cloud technology, ...
So you’ve found the perfect time and place to study and you’re ready to finally get some work done. You’ve pulled out your laptop, your textbook, and your notes, and four different highlighters. After five minutes of reading your textbook, you start zoning out and thinking about puppies. Then, you go on Tumblr and look at cut...

 



Upcoming Live Webinars




 

Copyright 2006-2021 by Modern Analyst Media LLC