Requirements gathering is the process of eliciting requirements from stakeholders and refining their quality. Early stage requirements gathering is focused on stimulating creative ideas. The middle stage is about adding assumptions and constraints to focus on the core value of your project or initiative. Late stage requirements gathering involves resolving inconsistencies and getting working prototypes in front of stakeholders. The following are common examples of requirements gathering.
KickoffRequirements gathering begins with a kickoff meeting that explains an initiative to stakeholders including elements such as a business case and mission statement.At first, some stakeholders may have few ideas. Brainstorming is a common early stage technique that encourages people to throw out the first ideas that come to mind.
Interviews led by a business analyst that are designed to explore requirements.Asking users to state their expectations for the project in the format "As a role, I'd like to capability, so that I can goal". For example, as a manager I'd like to be able to reassign tasks so that I can manage employee absences.
Asking users to document business rules. For example, "if a customer leaves their session idle for 30 minutes then their session expires."Non-functional requirements in areas such as design, infrastructure, architecture and technology may be contributed by a variety of subject matter experts. The example, "The site shall use brand colors according to the brand style guide."
WorkshopsMeetings that work through open questions and issues. For example, requirements may be inconsistent or infeasible.Getting stakeholders using simulations or working prototypes tends to lead to better requirements. Stakeholders often have new ideas when they see things implemented.The ongoing process of prioritizing, maintaining and refining requirements. In order to reduce project risk, it is common to implement a small number of requirements in short release cycles. In this case, requirements are viewed as a backlog that may grow with time. This can be a positive thing as it allows all ideas to be captured while only implementing the best ideas you have for each implementation cycle.
This is the complete list of articles we have written about business analysis.
If you enjoyed this page, please consider bookmarking Simplicable.
The common types and formats of requirements.
The difference between functional and non-functional requirements explained.
The difference between requirements and specifications.
The difference between functional and behavioral requirements explained.
A few examples of non-functional requirements.
A definition of requirements traceability with examples.
The common types of customer requirements.
The difference between functions and features.
The common types of requirements elicitation.
A definition of requirements management with examples.
The common types of needs analysis.
A list of business analysis techniques and deliverables.
The difference between business analysis and business architecture.
A few examples of common process gaps.
A definition of best in class with examples.
The common types of data analysis.
Common types of technical feasibility.
The common types of specification.
TrendingThe most popular articles on Simplicable in the past day.
Recent posts or updates on Simplicable.
© 2010-2023 Simplicable. All Rights Reserved. Reproduction of materials found on this site, in any form, without explicit permission is prohibited.
View credits & copyrights or citation information for this page.