How to manage Requirements? Training 02 How to manage Requirements? 5 mins

Documentation Overview Concept Problem Definition Feasibility & Analysis Solution Definition Business & Functional Requirements Technical Architecture Project Planning Design-Development-Testing Technical Documents Test Cases Code Documentation Bug Reports Implementation Installation manuals Admin manuals Go Live Sign-off Support User manual Operational manual 5-7 mins

How to Elicit Requirements? Create a questionnaire & have interviews Context: What Business process?(Finance, HR, Marketing & Sales, Operations, IT) Who are the users?(Nature of the users: Demographic, Education level, IT awareness) Solution: How does the existing system work?(Current Process) Any similar products you have seen or used?(Get examples) What does the future look like? How would the process work after the new system is implemented? Create User stories Ask for data that is currently used [Excel sheets] Understand and document the constraints Conduct Workshops Discuss the learnings from the interviews Have discussions on the requirements 10 mins

How do you manage & document? Maintain two buckets Discussion Freeze For Discussion use following tools: Create Agenda’s for meeting when meeting clients and send it before the meeting Prep the client about what you are going to discuss and what you need closure on. Line up your requirements on a slide and let them discuss and finalize them then and there Manage the discussion, give your inputs. Keep bringing them back to the problem. 5 mins

Example Discussion Slide Req # Title : Web Portal Actors Description Portal will Primarily have two types of Actors 1. Entities - will include the Stakeholders mentioned in BR001 2. Users - will be associated with either of the stakeholders Entities can be of following types: Financial institutions SME & MSME Businesses Corporates Research Institutions Start-ups Venture Capitalists Each company will have its own page with related information listed. Users: Web portal will have following type of users: Super Admin Users [ Will have access to all the web portal functions/ code/databases] Page Admin users [ Will have access to all the web portal admin functions Normal Users [ Web users will be normal users. Further roles can be defined under this category] Supporting Documents: Comments: Considers Status: Open 3 mins

User stories User stories are short, simple descriptions of a feature told from the perspective of the person. As a user, I can backup my entire hard drive User stories can have conditions User stories can be split up Use them to drive discussions Helps customer understand the user journey. 3 mins

How to use wireframes Use wireframes for driving discussion Do not overdo the wireframes they are a tool for visually representing ideas use them wisely While explaining wireframes use user stories 3 mins

How to get requirements alignment & Sign-off? Have the right crowd Include the business sponsor On having alignment create a document and circulate it to get approval Get Sign-Off from the customer on the BRD 3 mins

What is Functional Requirement Document It’s a techno-functional document which provides a systems perspective of the business requirement FRD should help you identify modules and structure your solution Helps you capture finer details of the solution 5 mins

How to Build FRD? Use the BRD as a baseline from here on Start identifying and separating requirements on following basis: Front end implementation and server side Data requirements Business Logic External systems Reporting User management…etc. Involve senior developers and also create technical architecture document, Database Designs..Etc. Identify data flow, system flow and map it with the business process you have documented in the BRD Make sure that each of your functional requirement is mapped to the business requirement 5 mins

Example Voice of Customer:- I want a software on my mobile for calculating profit on a land deal. Build a BRD and FRD 20 mins

Updating BRD Your BRD might change as a result of clarification keep it updated Always keep clarifications on emails Don’t commit time or cost to any of new enhancements until a complete analysis and feasibility has been done At the end of the Feasibility and Analysis get a Sign-off on all the changes. 5 mins

BRD vs FRD BRD FRD What BRD highlights "Business Requirements" - i.e., high-level business goals of the organization developing the product or solution with the help of IT. FRD highlights "Functional Requirements" i.e., functionality of the software in detail Why A formal document illustrating the requirement provided by the client It describes at a high level the functional and technical specification of the software Who Created by a Business Analyst (usually) who interacts with the client Usually created by Business Analyst under the supervision of technical expert, for instance System Architect Objectives To arrive at a consensus with stakeholders Depict each process flows for each activity interlinking dependencies To explain how customer/business needs will be met with the solution Holistic view for each and every requirements, steps to built When Always Projects > 50 MD’s ~ 400 HRS 5 mins

Next Trainings How to do Estimation? How to create project plan? How to manage DDT?