Prune The Product Tree

Hey Everyone -

We set a goal for focusing on one framework each month. I was about to let the goal go sliding by, but Ari gently reminded me that we set goals in order to achieve them. So, this month I want to focus on  Prune the Product Tree also known in the Game-storming Community as  Prune the Future
You probably know the basics:  Prune the Product Tree enables participants to capture how a product or service should grow by organizing their ideas (such as features or projects) using organic metaphors. It enables Agility by emphasizing evolution and growth with a balanced infrastructure and feeds roadmaps by capturing time. 
So, in this framework of the month, I want to focus on two things: post-processing your results and designing your online forums so that results are easy to process. 

Post-Processing Results

The results of  Prune the Product Tree  are fed your roadmaps and backlogs, with longer term items going to the roadmap and shorter term items flowing into backlogs.

The question then becomes: how do you identify the patterns? That's easy! You simply download the results from multiple forums and look for the patterns. To illustrate, let's explore how we helped the Scrum Alliance identify ways to improve their services. 
We started the project by engaging a global team of Certified Scrum Trainers (CSTs) in giving feedback in five separate  Prune the Product Tree forums. We then downloaded the results. Let's look at three specific items from two different forums:


Tree A
Form Partner Relations
Form official partner relations with other not-for-profits to cross-promote, offer joint conferences, whatever else might be helpful. 
Tree B
Collaborate with other compatible organizations.
Agile Alliance/ APLN / PMI / and others.  How can we increase the successful adoption of Scrum and other Agile practices?
Tree B
PMI connection
Continue to expand the Scrum connection to PMI.  Formalize relationship between SA and PMI

Although three different people in two separate forums created these apples, it is easy to see that these Apples refer to essentially the same goal: expanding relationships between the Scrum Alliance and other organizations. We therefore merged these into a single project: "Agile Community Relations". 
Playing multiple forums with key stakeholders, such as sales, service delivery and product development teams, and merging these results with multiple forums with customers, partners, suppliers and industry experts is the best way to increase confidence in taking action against your results. 

Making Post-Processing Results Easier

region  is a user-defined "geofence" that you can use to determine the placement of items. To make results easier to post-process, use Regions that align to your planning interests and planning time horizons. Let's focus on interests. 
In the Scrum Alliance project, we defined the following regions:

Looking at the Apples above, you can see they were placed in the regions "Reach of Scrum" and "Other Growth Opportunities". These were both reasonable choices, and their placement further guided our post-processing. 
You'll find that using Regions will make post-processing forum results fast and efficient.

Our framework of the month series is designed to provide practical advice on using key frameworks. What framework would you like to see us cover next? Email Luke at!