The document discusses recommendations for conducting an effective project discovery phase. It begins by introducing the speaker and agenda. It then defines the discovery phase as the initial research done to scope and plan a project. Statistics show that around half of projects experience issues like going over budget, missing deadlines, or not achieving goals due to factors like unclear objectives or poor planning. The document hypothesizes that performing a high quality discovery phase can help align deliverables with business goals and increase project success. It provides examples of artifacts that could be developed during discovery, such as objectives, scope, risks, and architecture. Finally, it offers tips for discovery like taking notes, visualizing information, and finding the true decision maker.

1. Project
Discovery phase

2. Hello!
I am Igor Rekhman
And I am here to share with you simple but effective
recommendations on preparation and execution of a Project
Discovery phase
2

3. Agenda
● Project discovery phase fundamentals
● Painful projects statistic
● Quality discovery catalysts
● Suggested artifacts
● Recommendations for BAs
3

4. Core concepts
What? When? Why? Who?
The discovery phase is a research you need in order to scope
and plan your project.
4

5. Projects by numbers
● 33% fail to meet original goals/business intent
● 53% experiencing scope creep
● 47% fail to complete in time
● 42% go over initial budgets
● 33% budget loses due to project failure
5
Source: PMI’s Pulse of the Profession® 2018

6. Why projects fail?
● Business is out of sync with project requirements
● Unclear business objectives
● Poor estimation during the planning phase
6
Source: PMI’s Pulse of the Profession® 2018, PwC 15th Annual Global CEO Survey
Spoiler: it is not complete list!

7. Effectiveness hypothesis
Quality project discovery phase increases project success by
aligning realistic deliverables with clear business goals.
7

8. Quality
discovery?
Vision. Focus. Skills. Balance.
8

9. What
it is all
about?
9
Objectives
MVP / MRA
Scope
Risks &
Assumptions
Roadmap
Infrastructure
plan
Vision &
Context
Architecture
Team
Composition

10. Tips and Tricks
Take notes
10
Visualize info
Be ready to
explain project
to 7 years old
Remember:
MVP is a test!
Do not lie!
Find true
decision maker
Follow rules,
but be a human

11. 11
Thanks!
Any questions?
You can find me at skype: igor_rehman