We work together to define the project’s high-level scope by breaking down the business requirements into a user flow diagram and the product backlog. Based on the user stories, we design interactive low-fidelity mockups for usability testing with prospective customers to evaluate and refine the scope.
Backlog consisting of short requirements written from the users’ perspective
Evaluate together with prospective users using interactive prototypes
High-fidelity prototypes and design assets for front-end development
Prepared for continuous releases and incorporating customer feedback
Backlog is a single source of truth for the work that needs to be done
A great definition of scope guides the team’s direction through clarity and focus
Diagram that visualizes the path a user takes through an application to complete a task.
A prioritized list of work for the development team that is derived from the roadmap and its requirements.
Wireframes that include the most basic content and visuals and are either static or interactive.
Testing method used to find out how potential users perceive and use the product based on observations.
High-fidelity prototypes that are interactive and contain most of the necessary design assets; UI library components for designers and UI elements in code for developers.
Hi, I’m Paweł Ferens, Head of Engineering here at Score and I can tell you more about the main purpose and benefits of this phase.
The define builds a solid foundation for us to start the Develop phase.