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/27/2014 12:06 AM
User is offline Kimbo
456 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 12:53 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!) 
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 1: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

Business Impact Analysis(BIA): Assessing the Potential Impact of a Cybersecurity Incident on Business Operations
In today’s highly interconnected society, businesses depend on technology even more than before. While offering opportunities for innovation and creativity, businesses are exposed to various cybersecurity threats that can disrupt operations, damage reputation, and result in substantial financial losses. It is crucial to carry out a comprehens...
In today's ever-evolving market, businesses must adapt swiftly to remain competitive and meet the needs of a fast-paced digital economy. Among the various business strategies available, digital transformation, customer-centricity, and sustainability have emerged as top priorities. Let’s explore why these strategies are critical for busine...
The Cisco Certified Network Associate (CCNA) certification is a pivotal credential for networking professionals, validating your skills in networking fundamentals, security, automation, and programmability. Preparing for the CCNA exam can be challenging, but with the right strategy, resources, and mindset, you can successfully achieve this certific...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC