Skip to main content

Business analysis

We help define your business needs to build the right product.

Our business analysts (BAs) bridge the gap between your business goals and technology. By translating objectives into functional well-defined software requirements, we ensure your product is correctly focused. This is key for complex applications.

Why business analysis is the key to building the right product.

At Osedea, we have the expertise to not only build your product correctly, but to ensure that we’re also building the right product from the start. We know from experience that complex projects benefit from having a dedicated BA on the team. Without this resource, you may find yourself without documentation, lack of logic, and with missing functionalities. BA with Osedea entails:

  • A dedicated person who takes time to analyze your business challenge from different perspectives and defines the end goals before presenting possible solutions
  • Digging deep to understand pain points and remove ambiguity
  • Defining a ubiquitous universal language understood by all teams to refer to the product
  • Understanding all components and parts of a problem (seeing the big picture, how the pieces are connected, identifying the contradictions, links, constraints, etc.)
  • Extracting requirements and define the scope
  • Helping make sense of business logic

    We define requirements to ensure that the final solution solves a need, driving value for users and the organization.
    Shed light on complex challenges, adapt solutions based on needs, and encourage innovation.
    BA increases efficiency on projects. Seeing the big picture is what allows us to connect the dots.
    One dedicated person throughout the agile process.

    The business analysis cycle

    Our four-step, circular process begins with an analysis of the current situation. By envisioning the product’s future, we lay out the specifications, implement, and evaluate.

    Analysis

    chevron

    Specification

    chevron

    Implementation

    chevron

    Evaluation

    chevron

    Our BA toolbox

    Our BAs offer the following

    Data models, mapping and flows

    Requirement analysis is often done through different modelling techniques. Visual models help all stakeholders involved to look at and understand data (a picture is, after all, worth a thousand words).

    Use cases

    A use case is a tool used to identify, clarify and organize requirements. It focuses on how actors (users) interact with a system to reach a goal.

    User stories

    A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective.

    Workshops

    We use a combination of workshops, interviews and observation to uncover what will make your product tick.

    Stakeholder matrix

    A technique used to identify and analyze all stakeholders (e.g. users, sponsors, managers, etc.), to determine their involvement, interest, influence and communication expectations in the project.

    Document analysis

    An elicitation technique where existing technical documentation (e.g. technical specifications, design specifications, technical audits) and non-technical documentation (e.g. user guides, documentation from prior projects, lessons learned gathered) is reviewed to gather a high-level picture of what the business entails and what the current state of the system is.

    Data models, mapping and flows

    Requirement analysis is often done through different modelling techniques. Visual models help all stakeholders involved to look at and understand data (a picture is, after all, worth a thousand words).

    Use cases

    A use case is a tool used to identify, clarify and organize requirements. It focuses on how actors (users) interact with a system to reach a goal.

    User stories

    A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective.

    Workshops

    We use a combination of workshops, interviews and observation to uncover what will make your product tick.

    Defining requirements

    Business requirements

    Set of high-level goals, objectives, outcomes that the organization envisions when launching a specific initiative.

    Stakeholder requirements

    Stakeholder needs to be met, provided the business requirements are successful.

    Solution requirements

    Functional and non-functional requirements of the solution.

    Transition requirements

    Requirements to facilitate the transition between the current situation and the situation to be reached.

    Why our approach to business analysis stands out

    Our BAs work within a tech context to support all teams by asking the right questions throughout the product cycle.

    UX-UI oriented discovery

    BA work complements design. BA will find and analyze competitors and extract what could be better from them to add to your product. The result? Detailed features and epic documentation to provide a solid and detailed estimation for development.

    Supports technical implementation

    We link BA to the development phase/ This differentiates us from other agencies. Rare to have BAs embedded in dev teams. Clients get a dedicated person who can anticipate questions regarding development (edge cases, technical aspects a client might not see)

    Valuable as a standalone service

    Our BAs offer standalone research and have experience iterating on functionally-dense and complex solutions. If a functional review is needed, BA can do a technical audit.

    UX-UI oriented discovery

    BA work complements design. BA will find and analyze competitors and extract what could be better from them to add to your product. The result? Detailed features and epic documentation to provide a solid and detailed estimation for development.

    Supports technical implementation

    We link BA to the development phase/ This differentiates us from other agencies. Rare to have BAs embedded in dev teams. Clients get a dedicated person who can anticipate questions regarding development (edge cases, technical aspects a client might not see)

    Valuable as a standalone service

    Our BAs offer standalone research and have experience iterating on functionally-dense and complex solutions. If a functional review is needed, BA can do a technical audit.

    “You describe the user stories with no ambiguity. Anyone can jump in and work on them since there are little to no questions. Lots of details are provided in the user stories.”

    Product owner at A.S.Hayes | consulting inc.

    “You describe the user stories with no ambiguity. Anyone can jump in and work on them since there are little to no questions. Lots of details are provided in the user stories.”

    Product owner at A.S.Hayes | consulting inc.

    How much does it cost?

    We get it. Budget is important to you (and choosing the right digital partner can feel daunting). That's why our process means taking the time to map out the activities we believe will make your project succeed so you can make an informed decision. We ensure regular touch points along the way to make sure your voice is heard and see faster ROI.

    Ready to talk about your project?

    With our tech skills in your corner, anything is possible. Let us design or develop your next epic digital product. We bring the right people, processes, and tools to build value for your business.

    What type of services are you looking for?

    Don't worry, our team will help define the services that will make your project successful.

    What is your budget?

    Tell us about your project.*

    250 characters left.