Contents <ul><li>Disclaimer </li></ul><ul><li>What is technical discovery (definition) </li></ul><ul><li>Why is needed (purpose) </li></ul><ul><li>How do we go about it (process) </li></ul><ul><li>What does it produce (products) </li></ul><ul><li>What if we get it wrong (risks and impacts) </li></ul>
Disclaimer <ul><li>This deck was put together to capture in simple terms (in a nutshell) what technical discovery is. Its content is targeted primarily towards people from non-technical disciplines (who are involved in the discovery process of a project) with a view to educate them on this subject so: </li></ul><ul><ul><li>technical discovery is not a “black box” to them </li></ul></ul><ul><ul><li>they can appreciate its importance and how it affects and is affected by the other streams in the discovery process </li></ul></ul><ul><li>The material is deliberately not branded, to facilitate easy reuse in whole or in parts for derivative works. To this end it is distributed under a Creative Commons License: Creative Commons Attribution-Share Alike 3.0 License . </li></ul><ul><li>Under this license you have to attribute that the derivative work is based or using parts from this deck. An acknowledgement with my details as per the footer of the deck would suffice. If you reckon this license is not suitable for your purposes, you may contact me to explore alternative licensing options. </li></ul>
Technical discovery - definition <ul><li>Technical discovery is the technical stream in the discovery process in a project. It happens in parallel with other work streams (e.g. information architecture,creative and visual) in the discovery phase of a project. </li></ul><ul><li>Technical discovery is the activity of identifying the problem context i.e. the business functional and non-functional requirements, the business system landscape (systems, owners, users, processes, interfaces, policies), and any other factors including scheduled changes to the above during the course of a project, assumptions and available technologies that altogether serve as constraints (either soft or hard) in shaping the solution to be delivered which must fulfill both constraints and requirements. </li></ul><ul><li>The exit criterion for technical discovery is gathering of sufficient information to produce a technical approach which gives the direction for the architecture of the solution. The architecture turns into more detailed design during the build phase. </li></ul><ul><li>All discovery streams together should result in a sufficient understanding of the problem to be solved and the constraints around it, to be able to enter the build phase of a project. </li></ul>
Technical discovery - purpose <ul><li>The purpose of the technical discovery process is to: </li></ul><ul><ul><li>identify requirements (both functional and non functional) of architectural significance. </li></ul></ul><ul><ul><li>prioritize and balance requirements (i.e. creative vision: what we want to achieve vs. technical capabilities and constraints: what is possible (scope) within timeline and budget). </li></ul></ul><ul><ul><li>feed into the planning process an initial view on scope, tasks, dependencies and estimates. </li></ul></ul><ul><ul><li>produce an initial feature matrix and map this to a program road map, envisioning the development and growth of the solution, in line with business strategy and objectives. </li></ul></ul>
Technical discovery - process <ul><li>Technical discovery is about investigation of the 'big picture' and analysis of the rationale and principles underpinning the findings. The following methods are typically employed: </li></ul><ul><ul><li>workshops with key stakeholders i.e. project sponsor(s), executive management, involved departments (communications, IT, finance, marketing etc.), third party vendors if applicable and primarily end users. </li></ul></ul><ul><ul><li>collation of documentation provided about systems (own or third party), processes and policies. Where direct documentation is not available indirect methods are used e.g. analyzing server logs /analytics, reverse engineering interfaces of existing systems, reviewing existing code bases as appropriate. </li></ul></ul><ul><li>The outputs of the above methods are assimilated into a collective view which defines the solution context and scope. Any gaps identified (known unknowns) must either be resolved through further investigation or working assumptions to allow the work to progress must be adopted. </li></ul><ul><li>All assumptions must be communicated clearly and signed off by the client, as they may impact the project scope, timeline, costs and risks, affecting overall delivery . </li></ul>
Technical discovery – outcomes & outputs <ul><li>The main outcome of technical discovery is reaching a position where </li></ul><ul><ul><li>one or more solution options are proposed to the client, with enough level of detail and confidence be able to select one option and enter a build phase to deliver it. </li></ul></ul><ul><ul><li>the duration, steps (inc. milestones and sign off checkpoints), costs and risks of the build are understood and agreed with the client. </li></ul></ul><ul><li>The key outputs of the technical discovery process are: </li></ul><ul><ul><li>technical approach / high level architecture document. It encompasses the big picture as identified during discovery and consists of multiple context and solution views from conceptual, to network topologies as appropriate. </li></ul></ul><ul><ul><li>technical project plan – the path to be followed during build </li></ul></ul><ul><ul><li>technical spike(s) / proof of concept employed to evaluate and derisk technology selection and integration </li></ul></ul>
Technical discovery – risks & impacts <ul><li>A technical discovery can be incorrect (not correct analysis of assets, miscommunication with stakeholders, non validated assumptions) or incomplete (people or systems that should have been involved in the big picture haven't) </li></ul><ul><li>The impacts can be: </li></ul><ul><ul><li>solving the wrong problem (deliver within constraints, but fulfill requirements captured vs. actual requirements). System is underutilized or abandoned. </li></ul></ul><ul><ul><li>fail to solve the problem (solution is inappropriate / does not meet constraints /not viable) </li></ul></ul><ul><ul><li>fail to deliver on spec, schedule, budget </li></ul></ul>
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.