The discovery phase of any project is both exciting and critical to the project’s success. There are several key points that you need to keep in mind as you navigate this process. The first thing you need to understand is who the players in the project are and what their motivations are for the project. Leaving out a key stakeholder in the resulting product is one of the easiest ways to doom your project to fail. The better the quality of the input you have at this early phase the better chance you will have of creating a well accepted deliverable. The next task you should tackle is to gather the goals for the project. Specifically, what does the company expect to get for the money they are about to layout. This seems like a common sense task, but you would be surprised how many teams to straight to building the system. Even if you are following an agile methodology I believe that this is critical. Inventorying the resources that already exists gives you an idea what you are going to have to build and what you can leverage at lower risk. This list should include documentation, servers, code repositories, databases, languages, security systems and supporting teams. All of these are “resources” that can effect the cost and delivery schedule of your project. Finally, you need to verify what you have found and documented with the stakeholders and subject matter experts. Documentation that has not been reviewed is actually a list of assumptions and we all know that assumptions are the mother of all screw ups. If you give the discovery phase of your project the attention that it deserves your project has a much better chance of success. I would love to hear what other people find important for this phase. Please leave comments on this post so we can share the knowledge. del.icio.us Tags: Project discovery,documentation,business analysis,architecture
