- What are requirements?
- Requirement development phases
- Elicitation techniques
- Functional vs. nonfunctional requirements
- Defining user stories and use cases
- Mapping data input and output requirements
- Validating requirements
Skill Level Beginner
- [Neelam] Well begun is half done. Or a good beginning makes a good ending. Nothing is more true when it comes to developing requirements. Requirement management sets the tone of your project. Done effectively, it can significantly reduce your product risk, keep your team motivated, and result in a satisfied customer, but many factors must come together to make that happen. Different stakeholders and their requirements must come together to articulate the vision of a product. The requirements need to elicited, specified, and analyzed as use cases, user stories, and data models. They need to be estimated, prioritized, and validated through prototyping. I'm Neelam, and I want to share some very useful tips and techniques for all these activities that can help you succeed as a team member, manager, business analyst, or customer to a software development team. So let's begin developing effective requirements.