Discovery Project

proposal for:
Name of your Client

Copyright @ Srijan Technologies

How to use this document?
Create a copy of the document.
Make necessary edits, like changing the logo and updating the name of client info
Share it across your team for a review
Send your awesome discovery presentation to your client
Business Background
<Write a few lines about the client, business/domain, their presence globally etc>

3
Key Challenges
It's important that we understand what are the key challenges/problems which the client is
willing to solve. For instance, this sample proposal is for the use-case when the client is:
● Unhappy with the current CMS - Want to Migrate to Drupal 8 from other
versions of Drupal and other CMS
● There are some limitations with current CMS and a lot of Tech debt has
accumulated - scalability, maintainability & extensibility.
● Unhappy with current user experience(front end users, backend editorial users
etc..)
● Want to migrate from a traditional website to a CMS
● No longer supported by community, e.g. Drupal 6
● Want a new Look and Feel - Complete change in UI/UX & existing
application/platform

4
 Discovery Process Workflow

Define Discovery Scope & Designate Team Define Outcomes &

Prerequisites Agenda Calendar Designate Owners

➔ Kick-start with pre- ➔ Define discovery scope ➔ Designate a team with ➔ Based on discovery
discovery to capture ➔ Set calendar agenda in clearly defined R&R certain artifacts are

DISCOVERY SOW
business collaboration with ➔ Designate client PO delivered as discovery
problems/challenges stakeholders for the (SPOC) with defined deliverables

CLOSURE
➔ Define discovery pre- entire duration ( ex. 2-4 R&R
requisite weeks)

5
DISCOVERY - Digital
Experience
Pre requisites

Outcome

RAID
 Discovery Pre-requisites
Category Items

Organization Map - Define client organization mapping of all stakeholders

Designs - Application designs/wireframes/ Information architecture if already exists,

should be made available if design is not in scope else wireframes, UI/UX
prototype etc should be the part of discovery

Application & Infra - Application & codebase access

Access - Schema access
- Site map of the applications
- Infra access, if required
- Application, code walkthrough etc

Any third party - List of third party services and microservices integrated with the web sites
integration

7
 Discovery Pre-requisites
Category Items

Usage Analytics / - Different types of user and personas, with any workflow or access control
Benchmarking - Existing application usage analytics (GA reports etc)
- Performance or other benchmarking reports

- System or application architecture Blueprint

Existing Architecture - Infrastructure architecture
- All 3rd Party integrations with system, if any

Key pain areas - List all the challenges/limitations in the existing system
- Existing defect analysis or existing tech-debt like trends of unstable
features/modules etc.

8
Discovery Outcomes
Deliverables Outcome

Product Canvas - a concise yet content-rich tool for conveying what your product is and how it is strategically
positioned

Identification of POCs - often POCs are required especially for 3rd party integrations
- all POCs to be identified of unknown and complex areas, with needed to be planned as part
of discovery

- Infrastructure & Deployment Strategy

- Solution Architecture
Architecture
- Content modeling, DB schema and Migration Strategy

- Identification of Components and Templates

9
Discovery Outcomes
Area Outcome

NFR - Identify all non functional requirements

RAID Log - Identify all Risks, Assumptions, Issues and Dependencies before hand

- High Level Product Backlog to be captured in excel during discovery and later to be
managed in Jira (Project Management Tool)
- Backlog estimation will be done using T-shirt sizing/Man-days
Product Roadmap
- Story Map

- Release Plan

10
Discovery Outcomes
Area Outcome

Staffing & budgeting - A staffing & budgeting proposal for the development phase of the project, considering if Srijan
were to deliver this project

Governance - A detailed Agile/Scrum process and calendar for running the development phase of the project
will be delivered covering any customer specific customisations, as needed.

QA Strategy document - Detailed Test Strategy

- Scope of QA automation if any
- Includes suggested tool-set in consultation with customer’s IT team

11
 RAID Log
Details Type Severity/Probability Impact

Designs for the new websites are not Risk High/High Overall deviation in the timelines
ready yet AND may not be available and budgeting
during the course of the Discovery
project

14
DISCOVERY - Team

Client PO

Dev Team
R&R of Client Product Owner
● Co-owner of backlog along with Srijan’s Product
Owner
● Responsible for sign-off on ‘product backlog’
● Help define and stick to calendar for the duration of the
Discovery across all client stakeholders
● Responsible for getting sign-offs from all internal
stakeholders
● Responsible for negotiating expectations (reasonable / “TOO CLICHE BUT THE MOST
unreasonable) of internal stakeholders IMPORTANT PARTICIPANT IN THE
DISCOVERY PROCESS IS THE
CLIENT.'‘

16
Team outlook

<Name> <Name> <Name>

Client Success Partner Business Analyst Delivery Manager

<Name> <Name> <Name>

Solution Engineer UX Designer
Technical Architect
SRIJAN TEAM R&R

Responsible for
<Name>
Client Success Partner Discovery project outcomes & client success

Responsible for
<Name>
Business Analyst Writing epics & stories along with “acceptance criteria”(detail
of some user stories as needed), document POCs required,
release planning

Responsible for
<Name>
Delivery Manager Account Governance, resource management, define & release
the work plan
SRIJAN TEAM R&R

Responsible for
<Name>
Solutions Engineer Product evaluation and solution architecture

Responsible for
<Name>
Tech Architect Defining technical architecture and related documents

Responsible for
<Name>
UX Designer Create meaningful sketches, mockups, and wireframes
Cost, Duration, Terms
Investment requirement from <Client Name>

Estimated duration of the project

Payment terms
 Cost, Duration, Terms In case of fixed cost discovery,
put the total cost, no break up
required

ONSITE/OFFSHOR
TEAM DURATION E RATES/DAY DAYS TOTAL
Week 1 Week 2
Client Success Partner 100% 100% Offshore $800 10 $8,000
Technical Architect 100% 100% Offshore $350 10 $3,500
Delivery Manager 100% 100% Offshore $800 10 $8,000
Business Analyst 100% 100% Offshore $280 10 $2,800
Solution Engineer 100% 100% Offshore $350 10 $3,500
UI/UX Engineer 100% 100% Offshore $350 10 $3,500
TOTAL $29,300

● Cost: $ 25,800
● Duration: 2 weeks
● Payment terms: 50% in advance and 50% on completion

Note: Applied Offshore (India) rates to this engagement. Any onsite stay and per-diem expenses to be charged additionally on actuals
21