"How does my offer become functional? Developing a first working product is a bit like a marathon. At first it's fun, then you have to hold on and in the end you suffer and sweat a lot. I know this is not always fun, I'm a third of the way through it myself. But don't worry: At item 7 I'll tell you how to survive this phase. Are you in a certain phase and want more details or need help, motivation or input? Love to help, just chat with me. But first, my overview for what we are dealing with here. ;-)"
1. What is an MVP, actually?
Guess where this comes from: Jup, the term originated at the Silicon Valley. That's the way they are: always on the hunt for innovations that can be implemented quickly. At this stage of product development, we speak of POC (proof of concept prototype) or MVP (minimum viable product).
Brainstorming is key. (pic: pixabay.com)
2. Move forward - instead of seeking perfection.
Speed matters: I remind you of Luke's words at 2:20. It is important that you have a crew around you that embraced the idea and runs the complete walkthrough with you. Do not lose yourself in perfectionism or details, but just keep going forward. Your competitors are not waiting for you, and the world is constantly developing new technologies.
3. Function follows users.
Listen to your people out there: For example, I have a slack group with a few users who keep checking to see if their development needs are taken into account - be it design, wording or features - only then will everything make sense!
Learn from the experience of others.
4. Plan step by step - but always with the end result in mind!
Yes, as weird as that sounds, it is so essential: Project managers must ensure that everyone involved constantly reads and hears where the journey is going. In oder to be able to work in a focused manner, you only have to take the next step with those responsible.
5. Already finished? Then, off you go – to the testing.
You can already try out what's going on, with a neat beta version? Congrats - I haven't quite got this far yet. That's why "My First Testing" will soon be available as a separate tip. But I can already tell you this: I've already asked some startups if they'll help me through the testing phase. #helpeachothergrow So I can try out the item 3 approach, right away... ;-)
Hangout-love is in the air.
7. ... and here, my tips to survive the sweaty phase 3.
Step by step, the machine starts to work.
An agile project also requires agile cost control. First of all, a roadmap including a rough estimate of costs has to be put on the table. Otherwise, there will be no money from the investors - and your project dies before it could start. In agile
projects, you normally work in sprints. For us, these lasted about two weeks each.
It is extremely important to keep track. What was planned? What was effectively implemented? What are the changes for an impact on the further roadmap? What needs to be adjusted? And what impact does it have on development time and
costs? An extremely challenging task for the project leader, who has to keep the overall view.
9. Use existing material.
Especially for the start: Use existing tools. Instead of programming everything yourself, it is an advantage if you know and use what already exists. Be it for billing, user logins or forms – there are already established applications which
you can integrate in no time.
I expect to launch my own MVP in February 2018. For that, I want to learn, together with you, how the future digital consultation around administration can be made easier and more efficient.
Are you interested in helping me in my testing phase? Then let me know and send me your email address, so I can invite you to my slack channel.
More about my testing method (and how it will work out ;-)), you’ll see then, in my other tip.
Digital Hugs, Nina.