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.


User stories

Backlog consisting of short requirements written from the users’ perspective

Feedback from users

Evaluate together with prospective users using interactive prototypes

User interface guidelines

High-fidelity prototypes and design assets for front-end development


Ready for Agile

Prepared for continuous releases and incorporating customer feedback

Synchronizes priorities

Backlog is a single source of truth for the work that needs to be done

Delivery velocity

A great definition of scope guides the team’s direction through clarity and focus

Core activities

User flow diagram

Diagram that visualizes the path a user takes through an application to complete a task.

High-level product backlog

A prioritized list of work for the development team that is derived from the roadmap and its requirements.

Low-fidelity mockups

Wireframes that include the most basic content and visuals and are either static or interactive.

Usability testing

Testing method used to find out how potential users perceive and use the product based on observations.

Design system

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.

A verified definition of the scope will guide the team into the right direction.

Hi, I’m Dariusz Żelasko, I'm the Chief Technology Officer here at Score and I can tell you more about the main purpose and benefits of this phase.

Contact me on

What's next?

The define builds a solid foundation for us to start the Develop phase.