The article will focus on how to collect product requirements, conduct interviews, and the discovery phase of software development. This material will be useful for those who do not know where to start, afraid of losing time, or not to take into account important things. For each step the theoretical aspects are described and their application in practice in the real project conditions.
To say that IT-companies routinely conduct full discovery on new projects is to exaggerate, if not to lie. The market is gaining more and more trust from customers. If your company wants and can take over the discovery phase, this advantage will distinguish you from the competitors.
The project’s life path starts with the Discovery phase and goes to the Delivery phase.
Table of Contents
You can visit this website to check more information about the discovery phase.
On the last point – everyone understands approximately when the project should start, when to enter the peak and when to finish. Just make sure that you didn’t have to start yesterday, but to finish – not tomorrow at lunchtime.
There is no single scheme of how to run the discovery, but there are effective scenarios. For example, the Double Diamond design process:
Your partner is company X, where many processes are still not automated and are performed manually. And yes, there are already several systems at its disposal, which allowed company X to do its job:
In case these products did not exist, you should still be performing the above tasks of the phase.
Team: two designers and a business analyst. Later on, architects and quality engineers joined us.
To begin with, agree in the team what Discovery will consist of and what artifacts should be obtained at the output. Choose and duration of sprints, decide on the tools, choose the format. When you are done, give it all to the customer for approval.
This is the easiest stage, but it is better not to neglect it.
Benefits for the team:
Benefits for the relationship with the customer:
An understanding client will be happy to offer you a list of candidates for an interview. If not, ask him yourself.
Even the most remote idea of the functions of the listed people will allow you to create “interview cards”. These are general questions about their work, which you will have to ask one way or another. Always leave a space on the card for clarification or information that could not have been provided.
Benefits for the team:
Benefits for your customer relationship:
Company X, for various reasons, did not support the idea of interviewing users of the frontstage-site. You thought that there would be enough information from the support team. In the context of the enterprise project, it was probably justified. But if you have the possibility to find an external user of the product, do not neglect it.
As for the employees, with a couple of letters, you have managed to get both the list of interviewers and their positions. You have communicated:
Once again: the interview with end-users is very useful. And full Discovery will not work without them.
Let’s say that you conducted an interview and began to navigate in the customer’s business. How to structure the obtained information?
Remember the Double Diamond scheme. Each problem is a request for improvement (opportunity).
Web development companies usually propose these features and you can order the discovery phase.
Welcome to the complex industry of tech startups! You’ve got a revolutionary idea, a small… Read More
E-libraries have become a remarkable tool for teachers in today's educational landscape. Offering vast collections… Read More
In case you have been fired from your job and you believe that it was… Read More
In an era dominated by technology, where emails, instant messaging, and social media have become… Read More
Keeping your PC cool is essential, especially during intense gaming or video rendering tasks. Proper… Read More
Artificial Intelligence (AI) is totally transforming how businesses operate. It promises incredible efficiencies and capabilities.… Read More