Requirements Gathering And Documentation
Requirements Gathering and DocumentationA Comprehensive Approach to Using Voice of the Customer
WHO WE AREWe help companiesconnect withcustomers to createand deliver clear andcompelling products,services, andmessaging. We help todefine the rightproducts and also talkabout them in a waythat makes sense. Andwe deliver actionableplans to bring the newidea to life2NEW PRODUCT IDEATIONInnovation ProcessIdeation SessionsCustomer Advisory BoardsPRODUCT EVALUATIONQualitative ResearchCustomer Sat StudiesCustomer Advisory BoardsCONCEPT EVALUATION& VALIDATIONMarket & Competitive AnalysisQualitative ResearchQuantitative StudiesCustomers PRODUCT LAUNCHProcess MappingCustomer Experience ProgramsOperations & Support PlanningPRODUCT POSITIONING& MARKETINGMessaging & PositioningProduct NamingProduct CollateralPRODUCT DEFINITIONMRDs & PRDsBusiness CasesCustomer ResearchEXPERIENCE DEFINITIONCustomer TouchpointsInteraction InterfacesUsability Optimization
REQUIREMENTS OVERVIEW Gather Requirements– From customers, employees, partners and other stakeholders– Globally Document Requirements– Use and easy to use/understand template– Be comprehensive and detailed Requirements Types– Requirements geared towards either in‐house or outsourceddevelopment– Requirements for internal business systems that support theinnovation, product management and product marketing functions(e.g. CRM, Idea Management, Content Management, etc.)– Requirements for new products– Requirements for new services3
REQUIREMENTS GATHERING APPROACH Review background documentation Create a draft Requirements outline Conduct a series of in‐person working sessions and calls withkey stakeholders, users, and the cross functional team– Use these sessions to gather requirements input; i.e. get the team’sthoughts organized and on paper– Conducted interview style– For internal business systems, shadow employees to documentexperience working with process and tools For new products and services, conduct research with thetarget customer– Interviews, focus groups, user experience/prototype testing Conduct a process mapping exercise with the team to mapthe process and the user/customer experience– Use process flow to determine requirements to support the idealexperience4
REQUIREMENTS DOCUMENTATIONAPPROACH Use an easy to read/understand template– Create a document that facilitates conversation and understandingbetween the business/product team and the technical teams– Keep user scenarios simple and easy for the technology team to relateto– Provide detailed requirements that are actionable Use a hybrid MRD (market requirements)/PRD(product/system requirements) approach– Allow for enough strategy, market and customer data to put therequirements in context– Include the “what” not the “how” Allow for review sessions with the stakeholders and crossfunctional team to ensure requirements were interpretedcorrectly5
REQUIREMENTS GATHERINGInternal Systems6Some examples include:CRM Requirements Gathered global requirements fromstakeholders using interviews, usershadowing and process mapping sessions Documented requirements for new globalCRM system Used requirements to lead vendorselection effortsService Management Tool Documented requirements for servicemanagement tool using cross functionalteam process mapping to identify systemsrequired to support the new service Identified and evaluated pool of servicemanagement tool vendors againstrequirementsIdea Management Tool Conducted cross functional processmapping to document the innovationprocess and system requirements,from idea generation and collectionthrough concept development andscreening to pilot planning andlaunch Identified requirements for a newidea management tool
REQUIREMENTS GATHERINGNew Products/Series7Some examples include:Mobile Advertising Platform Helped Startup team decide onrequirements for new platform Conducted cross functional workshopsand team interviews Leveraged inputs form partners andcustomersEnterprise Code Search Tool Documented requirements for newenterprise code search product Conducted Customer Summit with keycustomer targets to test/validate andgather requirements Worked hand‐in‐hand with engineeringteam to ensure product and technologywere in syncNew Services Business Developed requirements for a newsuite of services for a technologyproduct company Gathered and wrote requirementsfor 5 new services Used process mapping/customerexperience mapping to design thenew services Used requirements to develop toolsand templates to support the launchof the new services
BENEFIT OF THE CLEARWORKSAPPROACH Documentation that bridges the gap between business andtechnology Cross functional workshops ensure buy‐in and capturing of allgood requirements Customer research and input ensures voice of the customer Little resource required from your internal teams8
CLIENT TESTIMONIALS“Clearworks developed comprehensive product requirements for ournew mobile services offering. They picked up on the technologyquickly, were able to drill down to great detail, and incorporated themuch needed user perspective. Our engineers got just what they needto get started on development.”John Finch, VP of Product Management, Zoove"The Clearworks team did an amazing job understanding a complexengineering project, running our customer focus group, and turningthat into a usable product requirements document. I have mentionedto several people that it is incredible your level of understanding of ourproduct with such limited exposure."Dean Pfutzenreuter , Software Architect, Krugle"Clearworks is what every engineering team needs ‐‐ the voice of thecustomer brought into the product development process."Dave Loftesness, President and CEO, Blue Mug9
REQUIREMENTS OVERVIEW Gather Requirements – From customers, employees, partners and other stakeholders – Globally Document Requirements – Use and easy to use/understand template – Be comprehensive and detailed Requirements Types – Requirements
Magic Maze: on Mars Magic Rainbow ball Magic the Gathering Challenger Deck Magic the Gathering Commander Decks Groot Magic the Gathering Commander Decks Klein Magic the Gathering Planeswalker Deck 1 booster Magic the Gathering Planeswalker Deck 2 booster Magic the Gathering Spellbook Magic the Gathering
–Encourage you to treat requirements gathering as a process. –Provide some starting points for you to work from. Basis for talk: –Gathering effective requirements is known to be critical to success. –Using a generic hypoth
COVID-19 safe outdoor public gathering is defined by clause 19. event includes a function. exempted gathering means a gathering referred to in Schedule 2. gymnasium means a gymnasium that is a recreation facility (indoor) and that is open to members of the public, but does not include a
While traditional documentation cannot survive the demands of modern development , abandoning documentation altogether equally unviable. An ongoing, automated processes folds modern documentation into the DevOps framework and prevents documentation from becoming a bottleneck to rapid releases. Just as traditional documentation slipstreamed into
Sect. 3 overviews the role of microworlds in supporting that endeavour. A set of requirements for data gathering with microworlds is developed in Sect. 4. Framed by this set of requirements, some fundamental building blocks for data gathering with microworlds are proposed in Sect. 5. Sec-tion 6 describes a study investigating teamwork using the
Therapy Documentation Requirements -IP No Medicare-specific documentation requirements Accrediting body requirements apply Examples: Plan of care, timely discharge summaries, no use of inappropriate abbreviations, etc. State-specific documentation and supervision requirements apply Inpatient Rehabilitation Facilities (IRF)
Requirements are defined during planning phase and then these requirements are used throughout the project. There are some techniques for gathering requirements. These techniques are interview, prototyp
Business Administration professionals undertake a wide range of complex tasks in a variety of work contexts. They have a high degree of autonomy and responsibility and may provide some supervisory support (particularly at SCQF Level 8). Job titles for Business Administration apprentices could include:
