Dream it, Build it, Fix It.

Apparently, “Dream it, Build it, Fix it”, was a slogan Bill Gates came up with while he was the CEO at Microsoft, now you know it came from one of the richest men on the planet. So what’s wrong with copying one of the most successful entrepreneurs. Luckily we can! We have the processes in software development like Scrum and Agile practices which help us to replicate his vision.

I was spurred on when I recently heard the words “Dream it, Build it, Fix it” and wanted to write a short article…

Today’s dreams are tomorrow’s reality.

While you don’t want to rush in, you shouldn’t spend more time than necessary, but get this wrong, and you’ll lose money. Mr Dan Peña, who you would be wise to listen too, might suggest – Do your due diligence, ensure it’s moral, ethical, legal and you either want to be first or doing something different to the competition.

Get your vision written down. What will it do for the customers, what it means or/and does for employees and is to you the product owner?

Build it

You’ll need your team for that. When starting out to write this article I didn’t plan for this to be a guide to finding the right people, but, now I’m considering this might be a substantial part for any want to be entrepreneur. So, how would I do it? The choices that come to my mind right now; get a company, find a team on a platform like upworks or build your own team. I would go for the first two options; getting them to provide a fixed quote for your project and take the cheapest.

Unless they can produce the product in 2 weeks, I would insist on using a Scrum based approach. If you don’t know how this works then get yourself onto YouTube (I also provided a link above) and take in a couple of 3-minute introductory videos, which is all you’ll probably need to understand the process. Don’t use a company that is not willing to work this way, because you can’t trust them to do this using telepathy. It’s like source control, you absolutely need it and because it’s your intellectual property, you’ll want to own the repository. A great analogy I’ve heard and love is that that a developer who doesn’t use it is like a surgeon who doesn’t use gloves (just picture that for a while).

Fix It

Nowadays even Microsoft realised they have to be faster. Since your using Scrum in your project, you should have the ability to release a new version of your product every iteration/sprint, which could be every 1, 2 or 3 weeks depending on the length you choose. Key here is ensuring the deployment process has been automated. Did you remember to add that to the contract? Checkout GitLab for inspiration on this matter.

Good luck with your projects and when in doubt follow the Agile Manifesto.