- What is a Discovery Phase in IT Projects?<\/a>
- Discovery Phase Deliverables:<\/a><\/li>
- Two Types of Discovery Phases<\/a>
- Organic Discovery<\/a><\/li>
- Intentional Discovery<\/a><\/li><\/ul><\/li><\/ul><\/li>
- How Does Discovery Phase Benefit Software Projects?<\/a>
- Benefits of a Discovery Phase<\/a><\/li><\/ul><\/li>
- IT Discovery Steps: What Happens After Filing a Formal Request? <\/a>
- Step 1. Document the Available Project Information<\/a><\/li>
- Step 2. Assemble the Discovery Team <\/a><\/li>
- Step 3. Hold a Set of Workshops<\/a><\/li>
- Step 4. Finalize Discovery Phase Deliverables<\/a>
- Discovery Phase Deliverables:<\/a><\/li><\/ul><\/li><\/ul><\/li>
- To Conclude <\/a><\/li><\/ul><\/div><\/div>\n\n\n\n
What is a Discovery Phase in IT Projects?<\/h2>\n\n\n\n
A discovery phase is a pre-development phase of an IT project, designed to clarify requirements and develop a product roadmap.<\/p><\/blockquote><\/figure>\n\n\n\n
Discovery phase typically includes a set of meetings where you and your vendor get a \u201cheadspace\u201d to formalize your software product vision and put down all the necessary functional and non-functional requirements. It\u2019s a critical step for determining the optimal approach to software development. <\/p>\n\n\n\n
At Edvantis, we consider the discovery phase as an optional step (with the exception of the Fixed-price Project service model<\/a>). You may opt out of the discovery phase if you reach out to us with a well-defined project vision: formalized technical requirements, detailed scope of work, and a preferred tech stack and team composition.<\/p>\n\n\n\n
However, if you\u2019re still ironing out the deets, doing IT discovery can help you systematize all the ideas and organize them into product development plans. <\/p>\n\n\n\n
A well-performed IT discovery research helps you frame:<\/p>\n\n\n\n
- \n
- Main problem statement <\/li>\n\n\n\n
- Scope and boundaries of the proposed solution <\/li>\n\n\n\n
- Team and tech stack you\u2019ll need for the project <\/li>\n\n\n\n
- Risks and bottlenecks that may derail your efforts <\/li>\n\n\n\n
- Preliminary roadmap for product development and delivery <\/li>\n<\/ul>\n\n\n\n
Discovery Phase Deliverables:<\/h4>\n\n\n\n
![\"\"](\"https:\/\/www.edvantis.com\/wp-content\/uploads\/2023\/01\/Discovery-Phase-Helps-to-Frame_-1-1024x370.png\")
<\/figure>\n\n\n\nTwo Types of Discovery Phases<\/h3>\n\n\n\n
If you have ever organized a sit-down session with your team (or an outsourcing partner) to collect data for the project and prioritize different requirements, you\u2019ve already done some form of IT discovery. <\/p>\n\n\n\n
There are cases, however, when either you or your vendor have to formally request the discovery phase to explore the project specifications in greater detail. <\/p>\n\n\n\n
Respectively, the discovery phases can happen in two ways: organically or intentionally. <\/p>\n\n\n\n
Organic Discovery<\/h4>\n\n\n\n
Organic discovery occurs when both you and your IT outsourcing partner acknowledge that there is a need for clarifying project requirements and begin to exchange information. It is a natural part of co-creation \u2014 one of the key principles of how we work at Edvantis<\/a>. <\/p>\n\n\n\n
Co-creation in IT stands for proactive knowledge sharing and involvement of your IT partner in both the ideation processes and development process. Rather than trying to get all answers in-house, businesses tap into the vendor\u2019s outside perspective and technical know-how to gain innovative suggestions and unbiased assumptions. <\/p>\n\n\n\n
Intentional Discovery<\/h4>\n\n\n\n
International discovery, on the other hand, is a more formal request, typically voiced out by the vendor when they need to collect extra data around the product specs, deliverables, and other business requirements. <\/p>\n\n\n\n
Formal discovery sessions are the cornerstone to the successful delivery of Fixed-price Projects<\/a> \u2014 scoped, end-to-end outsourcing engagements with a set list of deliverables.<\/p>\n\n\n\n
The formal discovery process relies on structured business analysis activities such as: <\/p>\n\n\n\n
- \n
- Stakeholder and end-user interviews<\/li>\n\n\n\n
- Product scoping and feature prioritization <\/li>\n\n\n\n
- Product architecture analysis or design <\/li>\n\n\n\n
- Backlog preparation <\/li>\n<\/ul>\n\n\n\n
The above actions help both parties develop a shared understanding of jobs-to-be-done and provide a time and budget estimation for the development. <\/p>\n\n\n\n
How Does Discovery Phase Benefit Software Projects?<\/h2>\n\n\n\n
IT discovery phase is meant to set proper expectations on both sides pre-engagement and align the two companies on the shared objectives. So that at the end of the planned software development life cycle<\/a>, you, as a client, would walk away with a product that fully meets your requirements. <\/p>\n\n\n\n
From an outsourcing partner perspective, discovery is a crucial step to minimize the risks of:<\/p>\n\n\n\n
- \n
- Budget overruns <\/li>\n\n\n\n
- Extended timelines <\/li>\n\n\n\n
- Sub-par product quality<\/li>\n\n\n\n
- Unscoped work <\/li>\n\n\n\n
- And subsequently \u2014 unmet expectations <\/li>\n<\/ul>\n\n\n\n
At Edvantis, we host client discovery sessions for all Fixed-price Projects. But this step can drive positive outcomes for other types of engagements too.<\/p>\n\n\n\n
Benefits of a Discovery Phase<\/h3>\n\n\n\n
When it comes to software development outsourcing and project co-creation process, there are several important benefits.<\/p>\n\n\n\n
- \n
- Sharper business case and solutions vision. <\/strong><\/strong>Structured analysis helps uncover all project risks and requirements and translate your lofty \u201cvision\u201d into a set of concrete steps, requirements, and deliverables. These, in turn, can be effectively communicated to everyone on your team. And subsequently, used to determine the optimal service model<\/a>, team composition, scope and priority of work, and work breakdown structure<\/a>. <\/li>\n<\/ul>\n\n\n\n
- \n
- Lower chances of budget and timeline overruns.<\/strong><\/strong> Per PMI 2021 survey<\/a>, 38% of IT projects exceeded budget, and 45% fell behind schedule. Software projects have become significantly more complex, whereas the practices of requirements gathering and formalization remain underused. Discovery phase provides room and structure for defining the scope and subsequently mitigating the risks of overruns. <\/li>\n<\/ul>\n\n\n\n
- \n
- Risk assessment and mitigation. <\/strong>Apart from gaining a list of project requirements and deliverables, you can also use the discovery phase as an opportunity to get a second opinion on your tech architecture and tech stack. An experienced IT partner will draw attention to any weaknesses in your infrastructure capabilities, possible incompatibilities, and potential tech or operational constraints. By having this data, you can identify potential project risks and take proactive steps to mitigate them. <\/li>\n<\/ul>\n\n\n\n
IT Discovery Steps: What Happens After Filing a Formal Request? <\/h2>\n\n\n\n
As we go through the engagement process<\/a> together, we naturally talk about project details, filling in the knowledge gaps and achieving a common project understanding.<\/p>\n\n\n\n
However, when IT discovery is formally requested or occurs within Fixed-price Project service model <\/a>(or both), Edvantis initiates a four-step procedure:<\/p>\n\n\n\n
Step 1. Document the Available Project Information<\/h3>\n\n\n\n
You may already have some well-thought-out requirements or large-scale ideas in mind before our meeting. We\u2019ll need to capture that vision to: <\/p>\n\n\n\n
- \n
- Know what questions to furtherly ask you<\/li>\n\n\n\n
- Assemble the optimal discovery team <\/li>\n\n\n\n
- Select relevant case studies for references<\/li>\n\n\n\n
- Define the initial scope of the project<\/li>\n<\/ul>\n\n\n\n
During this step, we aim to evaluate your ideas, initial requirements, research results, past experiences, reference cases, etc. Your input will drive the discovery phase, so open and proactive communication is essential. Based on this knowledge exchange, we\u2019ll transcribe your idea into specific software requirements \u2014 then suggest the optimal path forward for delivery. To ensure secure information exchange, we encourage all clients to countersign NDAs prior to doing any IT discovery activities.<\/p>\n\n\n\n
Step 2. Assemble the Discovery Team <\/h3>\n\n\n\n
Based on the project type, we’ll appoint the right discovery team.<\/p>\n\n\n\n
Although team composition varies from one project to another, the following people are typically present:<\/p>\n\n\n\n
- \n
- UX Designer <\/strong>\u2014 helps collect and formulate non-functional requirements around product performance, usability, and main user flows.<\/li>\n<\/ul>\n\n\n\n
- \n
- Business Analyst<\/strong> \u2014 assists with functional requirement gathering, clarification, and formalization. Helps spell out the requirements for every behavior and function of the proposed solution. <\/li>\n<\/ul>\n\n\n\n
- \n
- Software Architect<\/strong> \u2014 assesses the current technical environments and infrastructures. Proposes the best-applicable software architecture design and technology stack. <\/li>\n<\/ul>\n\n\n\n
- \n
- Account Manager <\/strong>\u2014 <\/strong>facilitates discussions with stakeholders, manages expectations, and proactively addresses any questions or concerns at this stage. <\/li>\n<\/ul>\n\n\n\n
Since the discovery phase is a two-way engagement, you will also need to contribute to the conversation. From your side, the following people should assist Edvantis\u2019 discovery team and be available for client discovery sessions:<\/p>\n\n\n\n
- \n
- Key stakeholders <\/strong>\u2014<\/strong> typically product management team or a dedicated Program Manager. Though we also frequently work with partners on the c-suite level. To keep the discussions productive, only involve stakeholders with decision-making power for this particular project. <\/li>\n<\/ul>\n\n\n\n
- \n
- Business users <\/strong><\/strong>\u2014 involve end-product users if you haven\u2019t previously collected and prioritized a list of requirements. <\/li>\n<\/ul>\n\n\n\n
- \n
- CTO or Senior Software Architect <\/strong><\/strong>\u2014 their knowledge is essential for clarifying technical requirements. <\/li>\n<\/ul>\n\n\n\n
Depending on your project requirements, we may add specialists with niche expertise to the discovery team (QA Engineers, SRE Specialists, DevOps Specialists, etc.). <\/p>\n\n\n\n
Step 3. Hold a Set of Workshops<\/h3>\n\n\n\n
Now it\u2019s time we schedule a series of virtual or in-person workshops with your team. They usually involve a general overview session, led by an expert from your end, and a follow-up Q&A session, where we pose further questions. We can also hold optional design and technical sessions. IT discovery workshops typically last between two and six hours. <\/p>\n\n\n\n
The number and length of meetings will depend on your project’s complexity, what you have presented initially, and how many knowledge gaps you need to fill. <\/p>\n\n\n\n
For efficient workshop sessions, we follow such general guidelines: <\/p>\n\n\n\n
- \n
- Break down lengthy online discovery sessions into smaller ones to avoid burnout<\/li>\n\n\n\n
- Schedule meetings according to the participants’ time zones<\/li>\n\n\n\n
- Use secure virtual collaboration tools that fit all participants<\/li>\n\n\n\n
- Thoroughly document each meeting and save it for future references<\/li>\n<\/ul>\n\n\n\n
- CTO or Senior Software Architect <\/strong><\/strong>\u2014 their knowledge is essential for clarifying technical requirements. <\/li>\n<\/ul>\n\n\n\n
- Business users <\/strong><\/strong>\u2014 involve end-product users if you haven\u2019t previously collected and prioritized a list of requirements. <\/li>\n<\/ul>\n\n\n\n
- Key stakeholders <\/strong>\u2014<\/strong> typically product management team or a dedicated Program Manager. Though we also frequently work with partners on the c-suite level. To keep the discussions productive, only involve stakeholders with decision-making power for this particular project. <\/li>\n<\/ul>\n\n\n\n
- Account Manager <\/strong>\u2014 <\/strong>facilitates discussions with stakeholders, manages expectations, and proactively addresses any questions or concerns at this stage. <\/li>\n<\/ul>\n\n\n\n
- Software Architect<\/strong> \u2014 assesses the current technical environments and infrastructures. Proposes the best-applicable software architecture design and technology stack. <\/li>\n<\/ul>\n\n\n\n
- Business Analyst<\/strong> \u2014 assists with functional requirement gathering, clarification, and formalization. Helps spell out the requirements for every behavior and function of the proposed solution. <\/li>\n<\/ul>\n\n\n\n
- UX Designer <\/strong>\u2014 helps collect and formulate non-functional requirements around product performance, usability, and main user flows.<\/li>\n<\/ul>\n\n\n\n
- Risk assessment and mitigation. <\/strong>Apart from gaining a list of project requirements and deliverables, you can also use the discovery phase as an opportunity to get a second opinion on your tech architecture and tech stack. An experienced IT partner will draw attention to any weaknesses in your infrastructure capabilities, possible incompatibilities, and potential tech or operational constraints. By having this data, you can identify potential project risks and take proactive steps to mitigate them. <\/li>\n<\/ul>\n\n\n\n
- Lower chances of budget and timeline overruns.<\/strong><\/strong> Per PMI 2021 survey<\/a>, 38% of IT projects exceeded budget, and 45% fell behind schedule. Software projects have become significantly more complex, whereas the practices of requirements gathering and formalization remain underused. Discovery phase provides room and structure for defining the scope and subsequently mitigating the risks of overruns. <\/li>\n<\/ul>\n\n\n\n
- Sharper business case and solutions vision. <\/strong><\/strong>Structured analysis helps uncover all project risks and requirements and translate your lofty \u201cvision\u201d into a set of concrete steps, requirements, and deliverables. These, in turn, can be effectively communicated to everyone on your team. And subsequently, used to determine the optimal service model<\/a>, team composition, scope and priority of work, and work breakdown structure<\/a>. <\/li>\n<\/ul>\n\n\n\n
- To Conclude <\/a><\/li><\/ul><\/div><\/div>\n\n\n\n
- Step 2. Assemble the Discovery Team <\/a><\/li>
- IT Discovery Steps: What Happens After Filing a Formal Request? <\/a>
- Intentional Discovery<\/a><\/li><\/ul><\/li><\/ul><\/li>
- Two Types of Discovery Phases<\/a>
- Discovery Phase Deliverables:<\/a><\/li>