Overview
Documenting business requirements details the business solution for a project including the documentation of customer needs and expectations. It becomes the foundation for defining project scope and assessing the timescales and resources necessary to complete the project.
Has a client ever complained that what you delivered isn’t what she ordered? Has someone changed his mind altogether about the deliverable when you were partway through a project? Have you received conflicting requirements from different clients? Undertaking a focused and detailed business requirements analysis can help you avoid problems like these.
The process involves several steps. It starts by identifying the key stakeholders and then collecting data that captures their requirements. We then analyze the data using a technique called Quality Function Deployment (QFD). The final analysis and conclusions are put into a Business Requirements Document which in turn is used to launch a project.
Session Focus
This session immerses participants in a simulation to create a product and/or service that delivers what the customer truly wants. Participants will identify, collect, analyze and document customer requirements for this new product and/or service to create the Business Requirement Document (BRD).
Who Should Attend?
Program managers, marketing managers, functional managers, engineering, technical services, design engineers, product managers and product engineers who participate in the process, providing the inputs and as well as to write (or oversee/approve) the Customer Requirements Document (CRD) and/or create the Product Requirements Document (PRD).
Key Outcomes
- Understand the role and responsibilities of the individual(s) collecting the requirements.
- Understand the product or service by placing yourself on the receiving end of the process as a customer.
- Create a research plan.
- Understand the difference between a requirement and a specification.
- Identify the customers and customer segments.
- Learn various methods and tools to identify customer requirements.
- Determine the processes for collecting customer requirements.
- Apply the requirements process to ensure clarity in understanding customer requirements.
- Understand the customer’s requirements and expectations.
- Understand the product or service by placing yourself on the receiving end of the process as a customer.
- Translate the requirements.
- Complete the Customer Requirements Document (CRD).
- Analyze customer ratings from past experiences.
- Translate customer requirements into degrees of importance.
- Determine the design requirements.
- Analyze customer ratings from past experiences.
- Integrate competitive information effectively.
- Prioritize all customer requirements.
- Identify the requirements that must be built into the new and/or improved product or service.
- Finalize the “House of Quality” matrix.
- Integrate Quality Function Deployment (QFD) into the New Product Development process.
- Analyze and create solutions to create products that the customer will want.
- Develop the Product Requirements Document (PRD).
Course Duration
3 Days
