Too many business software deployment projects start prematurely. Against that backdrop it’s little wonder that many such projects run over time, grow in complexity, go over budget and don’t deliver the expected results. From requirements capture and analysis to documentation and scope definition, Neevsys place project deliverables in focus. For most projects, our deliverable is the project scope baseline. We define the project scope, develop the work breakdown structure, obtain approval and deliver what’s needed to finish planning and begin work.
While there is no single perfect methodology for identifying and analysing a project’s requirements, there are a variety of tasks and activities we select from to ensure that when the rubber hits the road, we’re on our way to a successful technology deployment outcome.
In requirements gathering, our user experience researchers gather information to lay groundwork with variety of tasks and activities we select from to ensure that we’re on our way to a successful project deployment outcome. Our requirements gathering process may include:
- Field Research—Interviews and observations in the user’s own environment to ground the user experience research in the context of use.
- Focus Groups—A series of structured group interviews, often with hands-on tasks involving new designs, to explore concepts and user opinions.
- User Modeling—Analyzing the characteristics of the key audiences for a product, website, or service, and creating characters or “personas” that depict examples of people who fit those profiles.
- Information Architecture Analysis—Evaluation of the information space for a product or website and identifying the components, taxonomy, and relationships.
- Task Analysis—An inventory and prioritization of the tasks that users perform with a product or application.
- Participatory Design—A series of design workshops, led by Neevsys experts, in which a team of stakeholders work together to explore and evaluate design ideas. Stakeholders may include users, designers, developers, marketers, executives, and anyone else who may provide valuable perspective on the nature of the proposed application and ensure that their requirements inform the design.
Once the requirements are gathered, they’re little more than a laundry list of items. Some requirements appear in duplicate, some conflict with others and some are too broad or too vague to understand. Here, time is spent analyzing the requirements. We review them for clarity and completeness, resolve conflicts and work to detect omissions. Next, we organize them by category and finally we prioritize them. Our objective is to generate clear, precise requirements.
Quantifying them makes each requirement actionable, measurable and testable. During this process we decompose each requirement to a level of detail that’s sufficient for design, execution and testing. Our goal is to identify mutually agreed upon acceptance criteria. Later, others will use this information to determine whether or not the requirement is satisfied
The final phase of our requirements gathering process is the creation of a requirements document. This document – with appropriate flexibility built‑in – sets everything out that’s relevant to the project including its scope, priorities, time‑frames, resources, aims and the assignment of roles and responsibilities.
Facilitates Schedule Estimation
Define baseline for cost estimation
Fosters better design
Establishes acceptance criteria
Reduces rework and waste