Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  How do you keep track of various versions of requirements documents? (first post. Hello!)
Previous Previous
 
Next Next
New Post 2/26/2014 11:06 PM
User is offline Kimbo
441 posts
5th Level Poster


Re: How do you keep track of various versions of requirements documents? (first post. Hello!) 

 Or just use your company's document management system

Kimbo

 
New Post 3/19/2014 11:53 AM
User is offline Machelle
6 posts
10th Level Poster


Re: How do you keep track of various versions of requirements documents? (first post. Hello!) 
Hi, Great question. If you're fortunate enough to work for a company that has a formal requirements management software, you would use its version tracking feature. Most of us are not that fortunate, so we make do with adding something to our requirements document. As others have mentioned, it's crucial to keep the latest version, and only the latest version, in a central location available to the entire project team. It's important that the requirements be locked down so that a single person, typically the BA, is the only one with write access. All changes should come through the person in charge of requirements and should go thru a change discipline if they've been baselined. I usually add a change log to the front of my requirements that tracks several key attributes of the change including date requested, submitted by, requirement # it applies to, rational for the change, status, date approved and impact of the change. If requirements are not managed properly, all sorts of problems will happen down the road. When it comes time to test requirements, having a single, approved version of requirements is critical. It's also important to identify who is authorized to request changes to the baselined requirements. If you follow the BABOK, requirements have different states that they go thru. The rigor applied to requirements management gets more stringent the further down the SDLC one gets. If you are at the beginning of the project, you may elicit requirements from a wide array of stakeholders. Once the requirements are prioritized, the list of people authorized to submit and approve changes is greatly reduced. Of course when using the Agile Methodology, the requirements undergo more frequent changes. So in summary, I recommend keeping one copy of the requirements with a version # in a central location, track requirements change attributes, ensure only people authorized to submit changes do so and ensure one person owns the requirements document updates. Good luck!
 
New Post 3/19/2014 12:02 PM
User is offline Machelle
6 posts
10th Level Poster


Re: How do you keep track of various versions of requirements documents? (first post. Hello!) 
Having conflicting SME views in a JAD session is common, especially if you have various departments represented. That's why it's important to have roles clearly defined and discussed prior to beginning the session. When I worked at Intel, we used the RAPID decision model. This is an acronym that describes each person's level of contribution/authority in a decision. Several people may have the authority to input their opinion, but it's the 'D' who makes the final decision. RAPID: R - Recommend A - Agree P - Perform (person doing the work) I - Input D - Decide (single decision maker) RACI: R - Responsible A - Accountable C - Consulted I - Informed
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  How do you keep track of various versions of requirements documents? (first post. Hello!)

Community Blog - Latest Posts

Neetu
Neetu
As a business analyst, we capture client requirements in different documents like BRD (business requirement document), FSD (functional specification document) and SRS (software requirement specification). If we are capturing the requirements in these documents, then why the document nomenclature is different? The answer is Yes. We are capturing the...
2 Responses
Jason White
Jason White
With time, we have evolved from oiled lamps to ever-present electricity, printing every page manually to now producing thousands of copies a day and so on. But what is the one thing these distinct things have in common? Yes, technology.One such branch of technology that has crossed leaps and bounds and turned into a  working technology fr...
3 Responses
Digital Business Analysis
Digital Business Analysis
Nowadays, companies like Audi and HSBC, use IT systems in everything they do. Does that make them to be IT companies rather than banks? Most would probably agree that HSBC is a bank, just as Audi is a car manufacturer. But what about digital banks such as Chime or companies offering digital products? In digital companies, most of the employees work...
1 Responses






Latest Articles

Learning from Experience
Apr 05, 2020
0 Comments
Everyone’s crazy busy when you’re launching a new project, and taking the time to study existing bodies of knowledge doesn’t seem li...
Copyright 2006-2020 by Modern Analyst Media LLC