How you can build a Scalable & Affordable MVP for your startup?
Tags: Startwithgenesis, Software Development, MVP, Startup, Gig Economy

1. Always have brief documentation of your requirements on hand. ( Writeup)

Photo by Kaleidico on Unsplash

You don’t have to explain a story about the product to him (Intern)over the phone every day, which might lead to a number of misunderstandings. Instead, create a Requirement Documentation.

R equirements document − A document or write up containing detailed requirements for the system being developed. These requirements define the functional features and capabilities that a system must possess.

The document should be concise, without jargon, modular, and provide information about each minor feature. Divide the Requirement in such structure:

Requirement Document Structure

You may use this as a template: Here

2. Create a wireframe ( Mockup )

Photo by Kelly Sikkema on Unsplash

Only you, as the author of the Idea, may imagine how your application should appear and function. Prepare a wireframe that will help any developer(Interns) to visualize what you are thinking. You can prepare wireframes using either pen-paper or an online application such as Figma(free) or Adobe XD(free) before hiring an intern. If you are not comfortable with these tools, you have other simpler options as well like Marvel(1 project free) or Draw.io(free)

Even a scribbled-on-paper diagram will suffice! read more about wireframing here

3. Setup Trello Board ( Not JIRA)

Trello and JIRA are from the same company, but I choose Trello Board for small startups and early users. It is basic and straightforward.

Mention all of your Requirements in the Trello board, based on the modules. Checklist may be used to separate the tasks in a module. This will allow you to monitor the project’s progress.

You can Clone a template from Here

4. Make a Git repository and set up Push on Mail.

Create a Gitlab repository, push a copyright notice inside it(This will keep your work Safe), and add your developer as a member in the repository, and request that the developer check-ins on a daily basis with the appropriate commit message. You may configure a push on mail service so that you will receive email notifications, whenever someone commits on the branch. Here is the process to configure

Copyright Notice, you can copy from here

Bonus : Always try to hire two Interns, and they both should review each other’s work. This is called Peer Review and it will definetly improve the quality of the project

5. Database Design & API Specifications

DBdocs Diagram

This is something you may lack since you are not technically savvy. However, this is really important for the project’s quality. Ask your intern to create these documents before they begin development because it will be impossible for them to focus on this after they begin work.

These documents include but are not limited to,

Database Diagram (ER Diagram): This applies to SQL databases. They can use any tool they choose. Personally, I like dbdocs.

If they are working on NoSQL databases like firebase and MongoDB, ask them to populate the database manually, to visualize the complete system, before developing. API Definition: This is for API specifications. This is only required for projects involving API creation. They can utilize postman to create specifications before developing, other options are Swagger and google sheet.

for postman, refer to this sample, and for swagger, the equivalent sample is given here. And for the Easiest one, Google sheet, clone this document.

6. Transparency

Your intern should communicate their progress on a daily basis. They may share the demo of the project, on a nearly daily basis. You should test and provide comments. Try to put your comments on the same Trello board, discussed in point (3), for the sake of maintaining records.

7. Daily Standup or Daily Status Call

GIf by https://in.pinterest.com/joeymillionz/

I know you’re too preoccupied with your idea and team. However, attempt to obtain at least 15 minutes to have a status call with the intern to hunt down the done, pending, and roadblocks along the route. Discuss what they have done, what is pending and why, and whether or not there is a roadblock.

Interns will be similarly motivated as a result of this.

Clone this sample document: Standup Sheet Format