Talk in English - US at PHPCon Poland 2019
View Slides: https://a.mefi.be/phpconpl19
Short URL: https://joind.in/talk/ff008 (QR-Code (opens in new window))
Being a Lead Developer is a fun, interesting and responsible adventure. Becoming one is not something that happens from one day to the next. It is something that you grow into by raising your voice, taking action and responsibility. I've learned many things working as a Lead Developer, but I'd like to share 6 things, which were the most important for me.
Comments are closed.
Very nice! I will include few of given tips in my work.
Insightful and well devlivered.
Interesting talk with a lot more than only six things that every leader should be aware of. Sensable and well presented.
There is one point that I disagree with. Maybe the author may give it another, closer look. The part about the MVP. AFAIK MVP in product development means "Minimum Viable Product", not "Most Viable Product" as slide no. 43 is saying. The mistake may have something common with sport, where the popular term is Most Valuable Player.
The clue of MVP is to handle the business concerns, and provide as much value as we can, with the minimum of the cost at the same time. The end product is not the key, value is. In the early phase we don't have many thoughts about the vision of the end product. What we only have, are a few assumptions that we are going to turn into value and deliver as some features, then gather early feedback to choose the direction for our product.
Look at Dropbox. They are struggling with the hard technical problem (security, sync, source availability and so on). Before they finished the prototype, they decided to make a video with explanation what problem and how they are going to tackle, and that was their MVP.
The next slide looks like misunderstanding, what Henrik Kniberg explained with the example of bike, scooter and car. I recommend his article: https://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp
Going back to the talk itself, there was no time for questions from the audience. It seems like presentation may fit more to 55-minute timeslot than 40.
Thanks for the great comments so far!
@kkreft Thanks for the detailed review! It is only a typo on the slide, I've fixed it, I was speaking about minimum viable products indeed. Also I didn't know what was the moderator saying in Polish at the and of the talk, but now I know it was "no time for questions", it explains a lot. I have to improve that, last time I was way more faster and finished 10 minutes sooner. Thanks again for the review!