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

The software development industry requires productivity and performance to create a successful product and meet business objectives. That's why everyone in the software industry always looks for new ways to streamline their processes and create better software. Today's world is experiencing an increasing pervasiveness of artificial intellig...
In the dynamic landscape of business analysis, staying ahead of the curve is imperative for success. The role of a business analyst is pivotal in driving organizational growth and efficiency. To excel in this domain, one must harness the power of cutting-edge tools and adopt strategic approaches that streamline operations and enhance decision-makin...
Angular is a powerful open-source web application framework developed and maintained by Google. It is designed to simplify and streamline the process of building dynamic and interactive web applications.  Angular was first introduced in 2010 as "AngularJS" by Misko Hevery and Adam Abrons during their work on a project called "...

 



Upcoming Live Webinars




 

Copyright 2006-2023 by Modern Analyst Media LLC