The project discovery stage is often underrated, yet its impact is significant. Whether you’re launching a startup or running a large, long-term project, there are many cases where the discovery stage is simply vital. In this article, we’ll walk through the common situations where it becomes a necessity—and the key deliverables you can expect from it.
How does the discovery stage go at Trembit and what artefacts are provided?
Based on more than 11 years of Trembit experience, there are a lot of benefits that the business will get at the end of the discovery stage:
- Prepared and complete design of your product
- Formalized requirements, documented in a manner, appropriate for all software development vendors, to obtain the product implementation estimate for project budget calculation
- Prioritized product features according to their impact on business value and efforts for the implementation
- Risk identification and planning
Below you will find the list of entities with examples, produced by the Trembit product team on the Discovery stage for the majority of projects. To see the templates, just follow the link in the article.
- Requirements.
The requirements are identified and formalized. It helps to set clear expectations of the project and define a goal. The product team member researches the field and clarifies virtually all cases with the Customer.
- Architecture vision.
At this step, the gap between business needs and technological solutions is removed. The product Architect or CTO is involved in determining the best solution for the planned project.
- Design.
Upon the request, the product team provides the wire frames, or the design, which is a good launch of the new project. The design, provided by Trembit, contains prototypes for web (including responsive) and mobile applications. We follow standard recommendations for design development for each mobile platform: Human Interface Guidelines by Apple and Material Design Guidelines by Google.
An example of mobile application design.
- Documentation.
Software requirements specification (SRS) is carefully documented, covering all discovered features. Documentation also includes the Product vision file, which is necessary for the business and marketing purposes. Product vision highlights the product advantages. An example of the SRS contents you can find below.
An example of SRS contents.
- Work breakdown structure (WBS)
The team (usually Team leaders) provides the WBS that allows to obtain the understanding of complete scope and delivery. A kind of roadmap is provided with the clearly divided tasks and description.
- Detailed estimation.
Based on the WBS and SRS, the precise estimates are given. You may find the WBS and estimation document example below.
Now, the project is fully planned and ready to start!
