How to Plan a Roadmap in Open Source by T-Mobile Sr Tech PM
•
1 like•159 views
Main takeaways: - Communicate your process clearly to internal and external customers - Tools should serve you, not otherwise (GitHub, Product Management tools, backlogs, etc.) - Keep moving, keep changing
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
More from Product School
More from Product School (20)
Recently uploaded
Recently uploaded (20)
How to Plan a Roadmap in Open Source by T-Mobile Sr Tech PM
- 1. www.productschool.com How to Plan a Roadmap in Open Source by T-Mobile Sr Tech PM
- 2. Join 40,000+ Product Managers on Free Resources Discover great job opportunities Job Portal prdct.school/PSJobPortalprdct.school/events-slack
- 3. CERTIFICATES Your Product Management Certificate Path Product Leadership Certificate™ Full Stack Product Management Certificate™ Product Management Certificate™ 20 HOURS40 HOURS40 HOURS
- 4. Corporate Training Level up your team’s Product Management skills
- 5. Aly Owens T O N I G H T ’ S S P E A K E R
- 6. About Me
- 7. How to Plan a Roadmap in Open Source?
- 13. PacBot Roadmaps in GitHub Idea Board
- 14. Ask me a question AND/OR Tell me how you do roadmap planning.
- 15. www.productschool.com Part-time Product Management Training Courses and Corporate Training
Editor's Notes
- If you’re interested to connect with other Product Managers, aspiring PMs, or those within tech, join our Slack community of over 40,000 professionals. It’s a great place to network and to find interesting content. We host a weekly AMA through our Slack channel on Tuesdays from 11:15am - 12pm PST. We have also recently launched the Job Portal where you can find the latest Product Management opportunities! As members of the Product School community, we'd like to provide you with these resources at your disposal.
- Product School’s Product Management Certificate Path comprises of 3 part-time courses for professionals with strong technical or business background who want to further explore Product Management at software-based companies. During Product Management Training you will first learn Product Management fundamentals to understand the software product lifecycle and what it takes to successfully transition into a product management role. You’ll then be trained to retrieve data, understand its value and make impactful decisions with SQL, data visualization and Tableau. Learn to understand your users to deliver exceptional UX/UI design and develop a robust digital marketing plan. During the Full Stack Product Management Training, you will deep dive into the technical knowledge to enhance your ability to work with agile teams. Finally, Product Leadership Training will elevate your product knowledge to become an effective Product Leader. You'll do an in-depth analysis on how to implement best PM practices on a strategic level to significantly impact your company’s portfolio and revenue. Learn the soft skills to manage product teams and manage stakeholders to deliver performing products.
- As well as individual courses we provide corporate training across the world! If you’d like to upskill your product team this is the best option for you. We have trained employees from multiple companies such as Deloitte, Salesforce, JP Morgan, Bank of America amongst many other companies across all industries.
- “About me” section Project in the desert, uncomfortable, imperfect, real. https://github.com/zasadnyy/catharsis-burningman-2019 2. Importance of community
- The question is How to plan a roadmap in OSS
- The short answer - build a community. Alright, I’m done.
- Not so fast. I have a few more minutes to kill. When my friends saw me post that I’ll be coming here tonight, one of my friends said: You should talk about the importance of customer and SaaS strategy. He sent me the notes and this slide. The other friend said, “just talk about burning man”. I’m not going to go through this slide. This is just another example of wonderful things that happen when you build a community. People will just want to contribute and help. Just as every product being with helping a specific and clearly defined customer segment make progress with in their life we also have relationships with those customers. Now for many organizations these relationships look like a funnel. On one side of the funnel we have a large group of prospect customers and on the other side of the funnel we have a smaller group of actual customers. This is sometimes referred to in a sales concept and is represented as a triangle pointing to the right. Customers move through the triangle from: - prospects - marketing qualified leads (MQL) - product awareness - product eduction - sales qualified leads (SQL) and finally become customers. In a customer CENTERED organization, we actually have a bow tie, NOT a triangle. Becuase when the customers first start using the product it is our job to start driving thier success. Over the last decade, this has lead to the creation of a new role- the Customer Success role. In a customer centered organization you recognize that there is an opportunity to LAND AND EXPAND. That you want to listen to your customers to: - understand how your product drives value in their organization - understand how you could drive more value in the organization (and capture that evidence for your roadmap) - understand other places in an org where you can drive value
- I’m here today to just share what I know. I’m sure some of you have way better solutions. For some of you my suggestions will work wonders, and for some they won’t. And that’s ok. Therefore, after I share my three examples, I’d like to open it up for discussion. Anybody can take 2-3 minutes and pitch us their way of roadmap planning. And we can discuss it. Jazz -> open sourced after using internally for some time. We had 2 different versions internally and externally. We didn’t have open roadmap planning at that point and few customers. So, often time we’d get no feedback or they’d ask us to solve a problem which gave us ideas what other features they’d want. At first, we only had internal customers so the community wasn’t building in github. The meetups weren’t helping much because we were going to the serverless meetups, and many people outside of that world of 35 people in Seattle weren’t very familiar with serverless and didn’t pay attention. After we started going to universities teaching what serverless was, showing how it works using the example of Jazz, then we started getting more traction and more startups started contributing. Serverless still has ways to go. https://github.com/tmobile/jazz-content Next Directory. Identity management tool. Auditing. This project was OSS first. Intel, Microsoft, Hyperledger -> Zendesk. -> https://github.com/tmobile/sawtooth-next-directory https://chat.hyperledger.org/channel/sawtooth-next-directory/ 3. PacBot. -> Also internal first but we didn’t duplicate things this time. We have one source and set it up to push features out into OSS. We started to have external contributors right away. PacBot isn’t a hard sell. Everybody wants to add security to their cloud. Talk about PacBot and what it does…. We were doing roadmap planning internally and we were building community on gitter. We had requests coming from internal channels and externally. To manage it we figured we’d want to communicate our rules of the game (we had to also come up with them).
- Feel free to speak with me and I can point you in the right direction (explain where to apply). Or you can visit www.productschool.com Have a good night!