Business Analysis, Timeline, Estimation & Priorities Business analysis

-- particles
WEEK 1 DISCOVERY
  • Introduction
  • Review business processes and understand business needs.
  • Interviews with stakeholders, documentation study, contextual research
  • Definition of use-cases
WEEK 2 FUNCTIONAL & TECH ANALYSIS
  • Working on the feature list
  • Prioritization of the features
  • Definition of MVP
  • Technical assumptions
  • High-level architecture
  • Recommended technology stacks
  • Hosting approach (cloud/on-premise)
WEEK 3 PROJECT PLAN
  • Project Plan
  • Project approach
  • Timelines – combined in a high-level project plan (i.e. how many sprints we will have, key milestones, etc.)
  • Team and resource plan (weekly FTE plan)
  • Budget – estimation
  • Project risks

Business Analysis Workshop Deliverables

USE-CASES

Use-case is a representation of a user journey through the product.

FEATURE SET

Prioritized list of features. We turn product expectations into actionable, detailed deliverables.

MVP DEFINITION

We spend a lot of time gathering all of the project features and requirements. We then prioritize the core part of the feature set for the 1st release.

SOW

The scope of work contains a detailed description of the work process and deliverables.

TECHNICAL APPROACH
  • Technical assumptions – Platforms, code base, OS needs, end-user devices, etc
  • High-level architecture – Custom created solution diagrams
  • Recommended technology stacks
  • Hosting approach (cloud/on-premise)
PROJECT PLAN
  • Project management approach
  • Timelines – how many sprints we will have, key milestones, etc.
  • Team and resource plan (weekly FTE plan)
  • Budget – estimation
  • Project risks