Plan and Organize

Almost Anything

 

Product Managers, Engineering Managers, IT Managers, and others use Obo Organize for product planning, sprint planning, story pointing, prioritizing, and personal Kanban. All with fast feedback that builds buy-in and improves results.

 

 

Organize quarterly plan 10.28.20

 

 

Product & release plans

Obo Organize is a quick and flexible way to to plan and communicate what will be delivered in upcoming releases, such as Spring Release, Summer Release, Fall Release, etc. Items are typically Items are features, epics, or other functionality your planning.

Items can be anything, from high-level initiatives to Jira issues and anything in between. Planning and getting stakeholder feedback with Obo Value Surveys works best when items are of similar size, scope, and effort. Think of items that represent trade-offs: You wouldn't choose between launching a completely new product line (BIG!) and adding a Cancel button to a modal in some feature (little). 

During planning, as you consider options, use the IN section of a bucket for must-haves and likely-to-haves. Use MAYBE for items on the cusp, or items that are stretch goals for that milestone.

 

 

Organize quarterly plan 10.28.20

 

 

 

Organize Rel Plan 10.28.20

 

 

Roadmaps with "why"

Obo Organize is a quick way to create high-level roadmaps that explain the "why" behind product decisions. In this use case, buckets represent time periods or releases, such as Rel 1, Rel 2, and Future, shown here. Items are features, objectives, initiatives, or other functionality you're planning.

Use the IN section of buckets to indicate plans and MAYBE for stretch goals. 

Run Obo Value Surveys to stakeholders and use the Obo Value to guide decisions. If stakeholders disagree, show them the results of Obo Value Surveys so they understand how others prioritize the features, objectives, initiatives, or other functionality on your roadmap.

 

 

 

Organize Rel Plan 10.28.20

 

 

 

Cost Sizing Table

Organize sizing plan 10.28.20

 

 

Story points

Beats planning poker. Import items from Jira for a single sprint using a JQL filter such as Status = Open, Sprint = 82, Issuetype = Story.

Click the $ icon on the top nav bar to edit the Cost Sizing Table. Set up your t-shirt sizes correspond to story points, person days, person weeks, or whatever sizing you use. You can change the name or values for any field.

Create buckets for item sizes, such as XS, S, M, L, and XL. Discuss item sizes with the team, and drag and drop items into their corresponding size buckets. Set all item costs from each bucket with a click in the more menu for the bucket. Update Jira Story Points with your results by clicking on the Jira icon at the top of each bucket.

 

 

Cost Sizing Table

Organize sizing plan 10.28.20

 

 

Prioritized GTM plan

Use Obo Organize for your go-to-market (GTM) plans based on priorities from multiple internal stakeholders.

Run Obo Value surveys to determine priorities for GTM for different releases and products. 

This video shows how we used Obo Organize for managing our transition from Beta to GA (general availability).

Priority 10.26.20

 

 

See how priorities change over time

Customer and internal stakeholder voting systems don't account for take trade-offs. Obo Value Surveys clarify trade-offs and provide a statistically valid stack ranking and absolute value (on a 0-10 scale) of the items you're prioritizing. 

Use Obo Organize buckets for different points in time, run surveys to customers and internal stakeholders, and see how priorities and values change over time. It's a great way to get rid of stale ideas that stakeholders said they wanted, but now they'd rather have more important features.

Priority 10.26.20

 

 

GET A FREE TRIAL