Skip to main content

Creating Space for Ideas during Roadmapping

Roadmapping sessions can become quite heavy and the balance between bottoms up and top down is a constant juggle game. Here is an exercise that proved to be quite effective in the teams I have supported:

Goal: Add Moonshots to the Roadmap!
Image result for moonshot
"A moonshot, in a technology context, is an ambitious, exploratory and ground-breaking project undertaken without any expectation of near-term profitability or benefit and also, perhaps, without a full investigation of potential risks and benefits." in https://whatis.techtarget.com/definition/moonshot

Time investment: ~1h (depends on the size of the team, this is an estimate for a max 5 people)

  1. Frame what is going to happen! This is an opportunity to take riskier or crazy ideas into the roadmap of the team. As in any type of investment we take a portfolio of items that range from low to high risk, this is the time to explorer riskier items. You will be proposing ideas and the top rated will get into the roadmap. We will rate each idea with starts 1-5, ideas with >=4.0 will be discussed to be added to the roadmap. 2-3 Moonshots will be added to the roadmap.
  2.  Give post-it's to everyone. Timebox 15minutes to think about a moonshot idea, write ONE concise idea that states the hypothesis and potential impact on the post-it.
  3. Once everyone has written, pass the post-it to the person on your left (clockwise). The person will give stars to each idea. 10minutes
  4. Collect all the post-it's and average the ratings and write it the >= 4.0 on the whiteboard. 5min
  5. Read through each post-it with >=4.0 rating timeboxing a discussion of 5 min per each.
  6. Ask everyone to rank the ideas given that only 2-3 will be added to the roadmap. This can be done on the Whiteboard by adding 3-2-1 points. This way of voting allows for ambiguity, each person can put 3 points, 2points, 1 point on items, it can not be redistributed, example: We have Ideas: A,B,C,D,E,F, my favorite is B and then D and finally A, I mark 3 dots on B, 2 on D and 1 on A.
  7. Select the 2-3 top ideas, add to the roadmap and attribute ownership of scoping proof of concept  to the person that suggested it. The ownership should come with a timebox to do it (Typically 1/2 weeks depending on the item).



Tip: You can shortcut the exercise by having each person reading their idea and do an open rating by show of fingers. This should only be done if everyone feels comfortable with the openness of judgement.

Have Fun & Let me know if you used it and what were your results!
Labels:

Comments

Post a Comment

Popular posts from this blog

Is it time to change?

Is it time to change? I have been wondering about this question for a while...  I always thought that there needs to be passion about what you are doing. I am passionate about technology and people, i develop my own experiments about Agile and i like the freedom to do what i think is best for a company, a team, an organisation or a project. But what is to like a job? This seems like an obvious question but  in reality is a fuzzy perception that might not have a clear answer. We spend most of our lives within the work environment, it becomes part of us and one might say professional and personal time can have strict boundaries but we are human beings and as so we build communities, we belong to communities and that's what will trip the "strict boundaries. I think it's really hard to keep separation of concerns when you spend a minimum of 8 hours a day in the same place with the same people. Our mood changes, the exterior world changes, we change, sometimes the day go
1 comment
Read more

Subtle Influence

Sometimes Influence can be very subtle. People are often driven by feedback and visibility, socialising ideas (on a positive manner) might have a dramatic positive impact on the things you would like to accomplish but don't depend solemnly on you. This article comes after discussing it with someone that wanted to gain visibility on a topic. If you are a software engineer like me think about Eventual Consistency and Gossip Strategies . The background idea is if you propagate an idea then you are allowing other people to think about it, mutate it, grow it, make it theirs till it comes back to you polished as if you have never heard of it. If it's a bad idea it can just die or branch into something new, nevertheless this will keep people aligned with your ideas/visions and help you build it as it also became theirs. When is this helpful? Any time :D well let me give you some simplified examples. Once i really wanted to pick up an interesting project on a team but I w
Post a Comment
Read more

Trust Need Space Opportunity (TNSO) Framework

Trust Need Space Opportunity (TNSO) Framework Through out the last few years as a manager i have created a framework to help me position myself to guide others improve and be able to take it to the next level. First let me tell you about some of my mistakes when i first became a manager. My first job as a manager happened very organically, I was on a technical architect role and it was my first job in the uk. Upon joining I got a reality check: all developers were leaving and the projects I needed to put in place wouldn't succeed as there was no one to keep the lights on. I was asked to help recruiting people. I did it but they were reporting to one of those managers that took a couple of excel courses, thinks that knows technology and was extremely directive. The developers that I hired were very unhappy and would come to me to unwind. After a lot of honest conversations with the manager and with the CTO the developers start reporting to me. I thought this was lovely and we w
Post a Comment
Read more