I want to share with you the points from the wonderful video by Oscar Hartman "From plans to business. How to create an IT product that will fly? "
I also advise you to write down points when watching video tutorials - the material is assimilated better and more efficiently in this way.
SO, HOW SUCCESSFULLY AND EFFICIENTLY TO CREATE AN IT PRODUCT?
- Set a deadline to launch MVP (minimum viable product).
- Feature cut (cutting unnecessary functions). More features is not always better. Stronger execution of a small number of functions that really distinguish us from our competitors is much more correct than the unsuccessful waste of time developing a huge pile of functions that no one would potentially need.
- Testing hypotheses. You can try to run ads on the product with buttons, but without functionality (non-working product blank). See what people want to use - and do it first.
- Do not ignore international experience. Explore the market before launching the project. Learn which architectures, technologies, frameworks, tools are used by the competitors. Do not reinvent the wheel, use the best practices of other people.
- Do not ignore the early pain - you need to reject squeamishness and eat a frog from the very beginning - do an unpleasant but important job of creating a project architecture, a strategy for working with data. Do not forget about it, doing only a pleasant job from the beginning - design.
- In parallel, prepare all the processes necessary to launch the project, which should converge to the deadline date at one point. Do not forget about all the processes.
- It is better not to outsource the initial stage of development of an IT product, but to do it with the help of your own team.
- Use the SCRUM product development methodology (read the book on SCRUM by one of its creators, J. Sutherland)
- A week before the launch of the product, you need to do a readiness test.
- Make several effective deadlines before the final deadline - in this case you don’t have to work in a panic during the last week.
- There must be a deadline culture. If you regularly move the deadline forward, the company will go bankrupt sooner or later.
- Discipline - to subordinate ourselves to a system that we have created ourselves.
- Try to do MVP in 50-90 days. If MVP is done for more than 90 days, people can be demotivated and you will never start a project.
- IT does not have to be a black box for you. Even if you do not have an IT company, you still need to understand at least the general concepts of IT.
I undersign to each point from this video - we will launch the next MVP faster and with even more discipline!