In a classic “waterfall style” project, requirements gathering is typically the first stage in the project lifecycle. It occurs during the initiation or planning phase when project stakeholders work together to identify, document, and understand the needs, goals, and constraints of the project.
In an “agile” process, requirements gathering is an ongoing “iterative” process, often accompanying each sprint cycle. Requirements may often be modified in this process, as the outcome of each previous sprint feeds into the next.
Regardless of the project management style, requirements gathering is a crucial stage lays the the foundation for the entire project or sprint by clarifying what is expected and what needs to be delivered. The information gathered during this phase is used to define the scope, objectives, and constraints of the project.
Different Types of Requirements
There are many different types of Requirements involved in developing digital solutions.
- Business Each business or organisation has its own internal business rules, goals and strategic objectives. We will work with your business to articulate your business rules and the desired outcomes and goals that the digital solution aims to achieve, such as increased revenue or improved operational efficiency. We use “User Stories” to articulate these requirements. In this process we will help uncover and make explicit some of the “ business rules” help to define and refine the business requirements. in order to ensure that that the set of Business Requirements comply with and successfully implement these rules
- Stakeholder Businesses are made up of individual and corporate stakeholders within the business the managements, site administrators, content creators IT departments etc. Business often have important external stakeholder, such as funding bodies, sponsors and their customers. outside of the business. We will work with internal and external stakeholders to detail the specific features and functionalities essential for individuals or groups within the organisation, and secondary stakeholders ensuring the digital solution aligns with their needs and preferences. We use “User Stories” to articulate these requirements.
- Solution A chosen solution often entails its own set of requirements, creating a recursive relationship where the selected approach gives rise to specific criteria and needs. Solution requirements provide explicit instructions for developers, encompassing both functional aspects (what the system should do) and non-functional elements (how well it should perform) to guide the development process effectively. We use “Gherkin format” - a human readable formal language developed as part of the behavioural Driven Development framework - to articulate these requirements.
- Transition Prerequisites Transition requirements encompass the conditions and criteria that must be met to facilitate the successful implementation and integration of the digital solution, covering aspects like testing, training, and support structures during the transition period.
Let’s look at a concrete example , in order to flesh out the nature of the different types of requirements.
- Desired Business Outcome:
- Increase overall attendance by 25% for the upcoming arts festival.
- Key Performance Indicators (KPIs):
- Achieve positive feedback from at least 90% of attendees through post-event surveys.
- Increase sponsorship revenue by attracting new sponsors through enhanced visibility.
- A dedicated online platform to showcase and sell their artwork.
- Interactive spaces for live demonstrations and workshops.
- Accessible and aesthetically pleasing venue layouts.
- Variety in artistic genres and performances.
- Customised sponsorship packages with prominent branding opportunities.
- Data on audience engagement and reach for sponsors.
- Functional Requirements:
- Website and mobile web-applcation for event schedules, artist information, and interactive maps.
- Online ticketing system with secure payment options.
- Virtual gallery for artists unable to attend physically.
- Non-functional Requirements:
- Creative and visually appealing design elements across all festival materials.
- Accessibility features for attendees with diverse needs.
- Testing and Quality Assurance:
- Thorough testing of the website, online ticketing system on mobile and desktop.
- Rehearsals and technical checks for live performances.
- Orientation sessions for artists on how to use the virtual gallery.
- Briefing sessions for event staff on handling different scenarios.
- Implementation Plan:
- Staggered setup of festival website to accommodate artists' setup needs.
- Coordination with marketing .
- Post-Implementation Support:
- Dedicated support team during the festival for quick issue resolution.
- Post-event analytics and reports for future improvements.