fbpx
let's talk

Collecting software requirements. Real life story

CEO of SPDLoad

Share:

4 min read

I would like to share my experience of collecting the requirements for four projects. Despite my first project being unsuccessful it taught me a lot about creating digital products. In the majority of cases when founders are collecting software requirements they often rely on their own conclusions rather than deeply researching their potential market. 

I am going to use this article to show you the mistakes I made, so you can avoid them! 

How did I collect my product requirements?

When creating my first product I was creating a solution for a problem that only existed in my own mind. I had not done the necessary research to ensure that this wonderful idea actually had a market wanting to buy it. Due to the lack of research I undertook, I would not even count this experience when discussing the collection of product requirements

I approached my second product more responsibly, having already received the primary requirements from industry experts. Using the internet to collate necessary research I tried to determine who would need this solution. I discovered that my potential customers were representatives of the automotive industry.

For my next product, I went a step further, by first finding the demand for my product before working on its realization. Determining who the client was first, allowed me to sign a preliminary contract on this basis so that I could develop the business. 

The following two products had already been made to a high standard. I had started with the validation of an idea followed by a deep competitive analysis that identified all the potential advantages as well as issues. I also studied statistics and necessary materials on the industry and entered into a dialogue with 100 people who fell into my target audience. An MVP was then developed to test out the hypotheses I had formed.  What is MVP?

Why do you need software requirements?

meme if you collect software requirements? you will not fail

The biggest mistake

The need for collecting proper requirements became apparent immediately after the first one and a half to two months of working on my first product. I realised when you do not yet have a full understanding of what your product should do, you cannot effectively explain it to your target audience. 

This was the biggest mistake I made when developing my product. I also found that when the requirements are not fully detailed this often leads to issues with budgeting and timing.  

Preventing a lack of data

So you are looking for an investor for your business, you have a great idea, you understand who needs it and have studied all the statistics as well as having analysed all similar solutions currently on the market. The investor agrees that you have a great idea and is ready to invest but do you know how much investment you will need? How long you will need to complete your product? and how long it will take to see a return?

 

You cannot guess the answers to these questions and this is where you need a specialist like me to help. From my experience, it is almost impossible to get money from an investor until you have the answers to the questions above. So, how to find investors and deal with them?

Discussing the software requirements

What does it mean to prioritize application requirements?

Variability and inaccuracy

When you work on collecting requirements, you have a very big problem – this is detailing. As an example, one of the requirements might be to create a user registration page. 

The details of this requirement will be regarding which systems we can use to authorize and register new users. Do new customers need to provide you with an email and/or phone number? Should the sign-up be verified via SMS or email? There can be a lot of variations around this which,  greatly affects the flow of your product, your understanding of the customer and the budget.

Details are everything

With my first two products there was no detailing, which later became a big problem. In one situation we wanted to increase the speed of recognition of objects when the car was moving through the snow. 

We discussed this requirement with the team and gave ourselves a deadline of 1-2 weeks. A week passed with no results because in the process of analyzing a lot more details we had not previously considered cropped up. What type of snow? what kind of lighting? what was along the edges of the road? what speed was the snow falling at? what was the speed of the car? did the snow stay on the windshield? 

The latter question proving to be one of the most difficult queries. If we had detailed all these questions earlier we would have realized that our budget was not big enough to complete this product.  

Once you have a deep understanding of the details of your product, you then need to work on prioritization and organizing your timeline. If you do not spend time on these things in advance, halfway through the development process you will suddenly realize you have run out of either time or money or maybe even both! 

My mistake was that I prioritized tasks based solely on my budget. Despite there being little written about it I believe prioritization should be done by all interested parties including customers, stakeholders as well as the team

Step chart of collecting software requirements

How do you collect software requirements?

A lot of time has passed since I created my first product and I have since gained a lot of experience and knowledge. 

As we speak I am currently collecting requirements for both internal products and for those of my clients. When we work with people we always explain to them why it is so important to collect all the necessary product details and requirements before anything else. 

After collecting all necessary requirements we can then communicate with our customers on how realistic their expectations are with regards to budgeting and timescales. With that information, we can then prioritize the most useful areas to work on. 

Remember it is important to liaise with stakeholders and explain to them your process of working however, their word should not be definitive.

Posted by

Max Babych

Max Babych

I am CEO of SpdLoad

I launched SpdLoad almost 7 years ago and now it has 20+ successful products in SaaS and Marketplace industry and several own products. I am an expert in Marketing, Lean Methodology and Customer Development approach.

Do you like our article?

Show us, how much :)

Article rating 0 / 5. Reviews: 0

Leave a Reply

Your email address will not be published. Required fields are marked *

Recommended posts

Offshoring vs Nearshoring: How to Choose What’s Best for Your Business?

Offshoring vs Nearshoring: How to Choose What’s Best for Your Business?

Over the past few decades, outsourcing has become a huge part of business management. It has proven to be an excellent business…

read more
50 Best Project Management Software & Tools

50 Best Project Management Software & Tools

Today technology has become synonymous with efficiency. And to increase this efficiency, organizations have tried different approaches. They try strategies to combat…

read more
Top Software Companies in Seattle

Top Software Companies in Seattle

Seattle is one of the most tech-savvy cities in the US. Its cultural and economic diversity have already nurtured the best software…

read more
How to Nurture Leads During Your MVP Launch

How to Nurture Leads During Your MVP Launch

Launching a product can be a tricky endeavor. That’s why it’s important to be thoughtful with each step of the process. An…

read more
19 Tools And Resources to Build an MVP From Scratch

19 Tools And Resources to Build an MVP From Scratch

How much does it cost to build an MVP? 10, 20, 30, or even 100 thousand dollars? The answer will surprise you….

read more
Knock out COVID-19: 9 Tips To Manage Your Remote Startup Team Efficiently

Knock out COVID-19: 9 Tips To Manage Your Remote Startup Team Efficiently

Coronavirus has turned on the shutdown mode for a whole world. Technology giants have already sent employees home and switched to remote…

read more
Lead Generation Landing Page Is Must For Any Startup And Here Is Why

Lead Generation Landing Page Is Must For Any Startup And Here Is Why

The lead generation landing page is a must-have for your MVP. Why? Let me explain in 50 words. Your landing page is…

read more
How much does it cost to build an MVP? 4 options to fit your budget

How much does it cost to build an MVP? 4 options to fit your budget

The main thing about creating an MVP is that just having a groundbreaking idea is not enough. The key to success is…

read more
Risk Management For Startups – The Definitive Guide

Risk Management For Startups – The Definitive Guide

Anticipating for the future is not always easy for startups. While the future can be bright, it can be rife with risks….

read more