Developing great solutions requires great requirements. While requirements are the primary responsibility of the business analyst, achieving the right solution requires collaboration with the technical team. Part of the collaboration is understanding how the role of the developer and business analyst can align their efforts and expertise. Setting expectations for each project participant is a key component to an effective process.
This class provides an overview of the business analysis role and a detailed review of the requirements provided to the development team. It is helpful to understand the categories of requirements, the interaction during solution scoping, and the types of deliverables and the communication formats used for each type of requirement.
- How the role of business analysis benefits the development team.
- Tips for collaborating with the business analysis professional.
- What is business analysis.
- What is a requirement.
- The types of requirements that are being elicited and communicated so developers can design and implement the best solution.
- How to identify the solution options and solution scope.
- How to proactively utilize business analysis deliverables.
- What is business analysis?
- Review the major tasks performed by the business analyst
- Review project participants and their roles
- Increasing the value add of business analysis to development
- What is a requirement? (business vs technology)
- Requirements categories and organization
- Business requirements (Context and decomposition diagrams, process descriptions, data, business rules)
- Solution requirements (Functional and Non-functional)
- Technical requirements
- Transition requirements
Determining the Solution Scope & Use Cases
- Developer’s participation in defining solution scope
- Discuss design options
- Identify technical priority of the desired functionality
- Break complex projects into phases or iterations
- Review who uses the software
- Use case descriptions
- User stories
Consuming Business Analysis Deliverables
- Review additional BA deliverables available to developers
- Entity relationship diagram
- Workflow diagrams
- AS IS vs TO BE
- UML Activity
- Interface requirement documentation
- User interface – Prototyping
- System interface documentation (checklist)
- Set expectations for feasibility, standards, and design
- Non-functional or supplementary requirements documentation
- Review questions BAs ask about non-functional requirements
- Transition requirement documentation