Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How a project is born. Intro to Discovery Phase

1,603 views

Published on

The presentation explains why discovery phase is required before implementation

Published in: Software

How a project is born. Intro to Discovery Phase

  1. 1. 1 HOW A PROJECT IS BORN Intro to Discovery Process by Kate Semizhon Solution Architect AUGUST 3, 2015
  2. 2. 2 INTRODUCTION Kate Semizhon • Solution Architect at Sephora • With EPAM since 2006
  3. 3. 3 START OF NEW PROJECT
  4. 4. 4 MAGIC PROCESS Design Develop Test Release Plan Discover Design Develop Test Release Waterfall Agile Repeat
  5. 5. 5 YOU FOLLOWED BEST PRACTICES AND FAILED? • One in six IT projects • cost overrun of 200% • schedule overrun of 70%. • 1/3 of all projects were successfully completed on time and on budget.
  6. 6. 6 KEY REASONS FOR PROJECTS FAILURE 50% 15% 17% 14% 3% 1% Poor requirements definition Poor scope control Inadequate risk management Communication problems Lack of qualified resources Other http://media.govtech.net/GOVTECH_WEBSITE/EVENTS/PRESENTATION_DOCS/2008/Best_of_NY/Defining_Business_Requirements_-_ESI.pdf
  7. 7. 7 You didn’t do discovery No requirements understanding You are building wrong architecture
  8. 8. 8 WHAT HAPPENS WHEN WE DO NOT UNDERSTAND WHAT WE ARE BUILDING
  9. 9. 9 A Common Myth Myth: • an analysis or discovery phase is surplus to requirements and just a way to waste a little money while delaying the project launch Truth: • The discovery phase reduces the risk of failure, to ensure you launch with the right tools, to cement developer relationships and to maximise the potential of getting off to a flying start.
  10. 10. 10 Discovery Team Solution Architect Product Manager / Business Analyst Project Manager* Dev Team* QA Team* * Optional
  11. 11. 11 Discovery Timeline Project Goals Statement Project Requirements are Provided Business Requirements Evaluation Develop System Architecture • Develop Baseline Architecture • Develop Target Architecture • Gap Analysis • Impact Analysis • Implementation and Data Migration Strategy Develop Discovery Artifacts • High Level Functional Requirements • High Level Solution Architecture • Impact Analyzes • Project Schedule or project plan • Performance Expectations • Non Functional Requirements Formal stakeholders review and sign off
  12. 12. 12 SUMMARY Discovery phase • Analyzed network requirements • Added missed Non Functional Requirements • Simplify requirements for integration with loyalty system No Discovery Phase • Longer Dev Cycle • Issues during deployment • Support Issues
  13. 13. 13 THANK YOU!

×