Treat this list as a menu, not a buffet. Pick three items and make them your high priority targets. Focus on effects that connect best to your strategy, and, ultimately, to your organization's mission. You need to know where you want to go before you can chart a course to get there. We've broken the goals into three categories, but you can mix and match across or within categories as you please.
6 steps to perfecting an open source product strategy
The future of building great products lies in breaking down the boundaries between business and technical thinking.
Input goals and output goals
The other week someone introduced me to the idea of “input goals” and “output goals”, by Oz Chen. Oz writes about “personal development and content strategy”, so…
How to build a roadmap in 3½ steps | HackerNoon
<em>When done right, the product roadmap reduces uncertainty about the future and keeps product teams focused on the highest priority product initiatives. But how to build it effectively?</em>
Team Objectives – Overview | Silicon Valley Product Group
After many years of being a very vocal advocate for the OKR (Objectives and Key Results) technique, in the majority of companies I meet, I have stopped recommending the practice. That’s because, in so many companies, even though conceptually the technique is simple and sound, it ends up proving a waste of time and effort,...
What Is Open Source Strategy? — Open Tech Strategies | Blog
There is a lot of documentation out there on how to do open source well at the project level. Historically, many projects have been started by developers, often on their own initiative, and the first non-technical questions they faced tended to be about project coordination (like "What collaboration tools shall we use?" or "What will our code review practices be?") and about community management (like "How do we decide who has commit access?" and "How do we integrate newcomers smoothly?"). Because developers hate to solve the same problems over and over, there is a wealth of detailed and varied material addressing those sorts of questions (we've even written some ourselves, but it's just a drop in the bucket of what's available). Taken together, this literature thoroughly answers the question "How do we execute the best tactics for developing open source software?"
From Open Source Software to Open Source Strategy
How the Smartest Executives Are Using Open Source Techniques to Optimize Corporate Strategy
Great engineering teams focus on milestones instead of projects | Jade Rubick - Engineering Leadership
Programs are more complicated than projects which are more complicated than milestones. Instead of projects, focus on milestonesMost engineering organizations focus on delivering projects. You can get better results by focusing on milestones instead.
Why open source: 25 reasons to embrace it | Ben Balter
Open source isn't a fad. Here are twenty-five economic, moral, and personal reasons your organization should embrace it.
Setting an Open Source Strategy
The majority of companies that use open source understand its business value and identify its advantages in efficiency, flexibility, interoperability, and speed of innovation. Yet only half of these companies report practicing basic open source management, such as community development, code maintenance, and the like, according to the latest Future of Open Source survey.
Complexity and Strategy | HackerNoon
I struggled with how to think about complexity through much of my career, especially during the ten years I spent leading Office development. Modeling complexity impacted how we planned major releases, our technical strategy as we moved to new platforms, how we thought about the impact of new technologies, how we competed with Google Apps, how we thought about open source and throughout “frank and open” discussions with Bill Gates on our long term technical strategy for building the Office applications.
OpenAI technical goals
OpenAI’s mission is to build safe AI, and ensure AI’s benefits are as widely and evenly distributed as possible.
4 keys to developing your mission or values openly
How can your mission-driven organization develop its mission openly? Chris Grams explains.
A Taxonomy for Open Source Software
I’m working on a structured taxonomy for classifying open source projects across multiple dimensions: domain, role, technology, audience, layer, and function.
A beautiful constraint – summary
A beautiful constraint. How to transform your limitations into advantages. By Adam Morgan & Mark Barden. Summarised by paul_arnold@me.com – Strategic facilitator, planner and trainer. Th…
Tools for Managing Open Source Programs
The road to strategic use of open source starts with a carefully planned, organized, and empowered open source program office to guide and manage its creation, distribution, and use. But that’s just a first step. To get such an office underway and running smoothly, you need the right tools. These mission-critical tools will be used to track goals and metrics in departments from engineering and legal to executive leadership, PR, and marketing, and give employees all the resources they need to gather data, provide snapshots of performance, and manage the daily use of open source within your company.
Ten Rules for Open Source Success - Hintjens.com
Biography | Portfolio | GitHub Books | Videos | Slides | Stories | Wiki Contact