8/30/2017 What Requirements Documents Does A Business Analyst Create? We'll Help You Start Your Business Analyst Care [extwton [ xcoumee | eatenpnar [ atc [cones [Rone [nooo [For con JoWW OUR FREE COURSE What Requirements Documents Does A Business Analyst Create? In: Requirements Model: ana Specifications By: Laura Brardenburg Comets, i ¥ a Joe yout Recewve ‘you working on outst projet as top BA Cate t bungee naa? Have you ome Framing Corse wondered nat wal eiremes Now Arties to Hap You documents a business analyst creates: rf ceed as a Busines: torreon byte bios ane cial poy teams? Information on New Course While the requirements documents created for any specific project will heavily depend on the type of project, Click here to learn more the needs and preferences of your business and technical stakeholders, and your organization's business Aids analysis standards, what follows is 10 diferent types of diferent types of ToP ARTICLES requirements specifications you might consider creating as a business analyst. "Business Analyst Webinars #1 — Stakeholder Analysis Theft singe eed oie cbse nai who ae etter ha Experience are, meaning who do we actually need to talk to to understand the business ‘Experience? (s Examples problem and flesh out the requirements. What Does Suocess Look Even ifthe business analyst doesn't create a formal stakeholder analysis Like? specication, you wil need to determine who the sponsor and key business stakeholders forthe project, the mul ves youll want to bring i tothe ‘Being aBA is Not forthe requirements, and discover anyone else who needs to be invalved. On a EnintofHeart technology project, stakeholders typically involve subject matter exces from the business and IT teams. Hove Do I Convince My Team soAdopt Better ‘Requirements Practices? #2 - Business Analysis Plan Why This Might Be Taking Next on he itis to rate abusinoss analysis plan. A business analyst wil : typical cea & plan that cuties the elation, requirements analysis, and HongeeThantondsnssh \alidation!veriiction efforts as well as clearly incicates who is responsible for what The Danger in Bs ‘The Dangerin Being an within the context ofthe business analysi efor. Expert “The business analysis plan will ofen be dtven by an organization's business Cases: A Pas analisis methodoloay, whlch may be formal or informa. History (anda bitofa love #3 - Current State Analysis hpiliwmw brdging-the-gap.comvrequirements-documentation! 1M8/30/2017 What Requirements Documents Does A Business Analyst Create? Understanding the current state is acrtcal step in the businoss analysis process, If What TeDoWhena the current business process or business domain is not wall understood, it may be Developer Says “That necessary to analyze and document the current slate before scoping a project fo Ampossible” Improve upon it. This could involve “as is" process documentation or an assessment of curent capabilities. #4 - Scope Statement Specification HABA ist eesten This the most fundamental delverebe on any project ~ caer dtnton of the . Fie scope of to poect or pod, This pecan might lobe eored i as 8 fd peaiiect ‘usnoss Casa. Vision Document or Business Requirements Document (though in Management practice, BRDs typical incude many addtional sections that woul include the : Institute Functional Requirements, which | classify as a separate deliverable). In this requirements specification, you are essential answering the following auastions: eee Brats What problem are we solving of whats the business need? eee anc ‘What i the scope ofthe solution tothe problem? Is the investment in solving the problem worth it? {nan agile environment, these sort of questions might be answered in an epic format (Before | forget, all of my requirements documentation templates, including a simple ‘Scope Statement, are included in my Business Analyst Template Toolkit) #5 - Functional Requirements Specification Sen It the solution is software solution (not all solutions are), then the business analyst vill specity the functional requtaments forthe project. These requirements specifications might also be referred to as software requirements, technical requirements, or system requirements. Functional requirements identity what the system does ~ how it functions ~ and typically are written atthe level of what a civen “user” can get the system to do. Functional Requirements can be captured in 8 wide variety of requirements deliverables Use cases 38 a very common way to capture functional requirements, Other times the use cases are captured together in a Solware Recuiremen's ‘Specification (SRS) , which may also include the non-functional requirements. nana vironment, functional requirements are captured in user sores which are organized in a product backlog. For Bis without an IT backoround, this is the level at which you need to learn to Understand and talk inteligently about “IT” —i's about whet the system can do for the business, not about how that system is built. f even if his level of Understanding technology eystems is not appealing, you are probably beter off focusing on business process focused BA roles. #6 — Wireframes and Other Visual Documentation (ten times, functional requirements are accompanied by renderings ofthe user Interface, most commonly in lowfidelty wireframes. ABA who Is also a user ‘experience designer may also be responsible for creating a high-fdelty prototype, tp iwwurbrdging-th-gap.comrequirements-documentation! 2168/30/2017 What Requirements Documents Does A Business Analyst Create? ‘And i the rules behind the user interface are important, a user interface soscification can be a handy spec to pul al the details togethorin context for your velopment team, Woridow claarame are algo commonly used to depict a functional or business process in a visual way, which facilitates a more efficent requirements approval process. #7 - Information or Data Model Documentation In addition tothe user-facing functionality of the software, the business analyst may identify elements of the information model too, This could be at @ conceptual level (Which | tend to capture in a ciomain modi!) or a more detailed level using a sala dictionary or data mapping specication #8 - Test Plans, Test Cases, or User Acceptance Test Plans the business analyst is involved in testing the software application, they may also create atest plan and dotalled test cases to validate thatthe functional requirements are met. Often ths task is handled by a dedicated Quality Assurance Engineer in which case the BA might be asked to review their plans. Even when basic functional testing is performed by QA, the BA may be involved in testing conducted by business subject matter experts. This is typically called User ‘Acceptance Testing (UAT), The BA may lst out scenarios for the business stakeholders fo walk durough and may actually faciltate elements ofthe testing, #9 - Change Management While User Acceptance Testing gets the business community started down the path cof embracing the changes to come, other dliverables may be necessary, These could include updated business procedures or husinass processas, checklists or Work aids, or new training materials. Again, sometimes these deliverables and processes are covered by other groups. Towards the end ofthe project, the business analyst may also update the requirements deliverables to reflect the as- built functionality so thatthe team can start the next project working for up-to-date system documentation #10 - Throughout the Project \While ideally the business analysis and project management roles are fled by two different individuals, the business analysts responsible for managing the requirements process and contributing to the project plan. Often this means. ‘maintaining a requirements issues Ist, contributing tothe project implementation plan, and providing regular status updates. You'l also be creating mesiing avandas and typing up mesetina notes to capture the results of your requirements ciscussions and may be involved in managing change cequests as stakeholders discover updates to the requirements, Choose Your Requirements Documents By no means does a business analyst create every one of these requirements specifications for each project. Most 8AS pick and choose the most appropriate specifications given the nature oftheir project and customize their lomplates based fn stakeholder needs and project considerations. tp iwwurbrdging-th-gap.comrequirements-documentation! 388/30/2017 What Requirements Documents Does A Business Analyst Create? >>Save Time on Your Next Requirements Document ERREETTRTIE Would you tke a staring point for approaching common peerees cr business analyst work scenarios? Check out my Business, ‘Analyst Template Toolkit ~ all of my requirements templates are fuly annotated and editable by you, giving you a great starting point for starting your next business analyst project, ‘or formalizing your work samples. aw artic! Stay informed about r jes and course offerings. (agate lp a eta Sion UP (Click hereto learn more eucntatenataase copymrt© 2017 ise cn usin Ana LLC Aza ae Pay olay | are an Dimer | aera hpiliwmw brdging-the-gap.comvrequirements-documentation! 418