Author: Hayden Smith 2021
This lecture highlights some key principles in trying to rapidly develop and execute on software solutions you see in relation to a given problem. Some aspects of these approaches may be incompatible with more fundamental software engineering principles discussed in the course - don't get the two mixed up
Â
This lecture would not ordinarily fall into this course - It's simply a bonus lecture for a lighter end of term.
An MVP is a minimum viable product that can demonstrate the fundamental value of a proposed solution without investing resources to build out an entire system.
Â
The sole purpose of an MVP is to validate assumptions, not to build good technology. Good technology can come later.
Â
It's like the smallest "demo" of something that still makes clear what the bigger idea is.
Â
These are all part of a cycle, too. Sometimes learnings in planning or building send you right back to ideation etc.
Every MVP is a demonstration that seeks a product-market fit
Once you confidence that you've ideated correctly, it's time to bring your solution to life. Ways to do this include:
Â
This stage allows you to identify challenges with your approach, or alternatively to talk to potential consumers with something tangible to learn what works and what doesn't prior to building
If you are confident you know what needs to build - it's time to build it. Get your checklist together:
What technology should you pick? Whatever you're most comfortable with.
After you build something you will learn a lot just from hearing about people using it. However, this won't tell the full story.
Â
Consider using data collection tools like Google Tag Manager or Segment that allow you to collect aggregated identity or event information about users of the solution, and then pass to a number of third party providers that typically:
Â
Â
Â