© Expert Decisions Inc.– All rights reserved. 1 1

© Expert Decisions Inc.– All rights reserved. 1

Hit the user needs!1


• Expert Decisions Inc. was incorporated in Alberta 2003

• University of Calgary spin-off company

• ReleasePlanner™ is a cutting edge platform for optimized product management

• Based on 2010 US patented technology

• Has been proven successful with 500+ customer and trial projects

Who we are?


The imbalance in feature usage

Almost two thirds of all features are (almost) never used. This implies• Wasted development effort• Increased maintenance effort• Customers overwhelmed from (almost)

never) user features.

45% Never 19% Rarely 16% Sometimes 13% Often 7% Always

Question: What would happen if one of the key features was not offered?

Should this be changed? YESHow this can be changed: Apply EDI technology suite!

Standish Group Study Reported at XP2002 by Jim Johnson, Chairman


Our technology suite

Customer NeedsAnalysis

CollectivePrioritization

Optimized ProductPlanning

Optimized ProductDevelopment

ProductEvaluation


Our tool suite



Developing the right product Systematic process based on - Collective wisdom- Objective data- Power of

optimization

… in the right way


How does it work? - Dashboard

For the current plan:Which features are inwhich releases?

Which project set-up steps

still need to be done?

For the current plan:What is the projectedexcitement of thestakeholders with this plan?

Ranking of most controversial features

Effort – valueprofile of all featuresin consideration


Customer needs analysis & collective prioritization


Feature priority and disagreement analysis

- What feature are most attractive?- What features are least attractive?- What features are most controversial?- What feature are least controversial?


Most controversial features – Where to focus your discussion

For a given feature:Spider graph with priorities assigned by stakeholders


Optimized product planning


Where the data comes from? Import and export of data from synchronization to issue management system JIRA or equivalent


How does the optimized plan looks like? For the two upcoming releases, all the features involved per release as well as their assumed effort consumption are shown (visible from mouse-over)


How much will stakeholders like your plan?

Profile of projected excitement of stakeholders with the given plan


Product evaluation


How much do stakeholders like the proposed features?

Prioritization of features per criterion.Display of features with simular priority


Subscription-based services for:Unique Selling Proposition of ReleasePlanner™ 2.0 in the context of Analytical Product Management:

WHY EDI? - WHAT DO WE OFFER?

• Offering optimized and diversified planning alternatives

• Consideration of quality criteria as part of the planning

• Integration of operational and strategic planning

• Comprehensive support of re-planning (both operational and strategic)

• Risk analysis capabilities

• Ability to accommodate many types of complex logical dependencies


Intelligent Surveying: • Stakeholder (including customers, users, sales representatives, managers) based

prioritization of (future) features, ideas, projects, services, cost drivers, processes, architectures and more.

• Prioritization of defects.• Feature elicitation and discussion.• Retrospective evaluation:

– How frequently have existing features been used?– Have the features increase customers’ satisfaction?

• All types of analytics such as: criticality, variance when comparing between groups of features, groups of stakeholders.

• Consensus building: Which features have high versus low consensus?Effort Estimation: • Stakeholder/Expert-based estimation (based on 3-point estimates).Monitoring:• Monitoring of projects (e.g., status of feature implementation).

Use case scenarios VeryBestChoiceLight - 1/2


“ Principle 1 of change for gaining competitive advantage in the era of smart:

Decisions will be based not on “gut instinct,”

but on predictive analytics. “

Use case scenarios VeryBestChoiceLight - 2/2

Ginni Rometty, Chairman President and CEOIBM, 2013


• Resource optimized product and service road-mapping• Release planning for management of technical debt• Release planning in consideration of complex feature dependencies• Release planning in consideration of quality criteria• Issue management and optimization with compatibility to JIRA• Optimized user excitement analysis• Release planning for multiple products• Optimized features for sprints in Scrum• Better sprints and releases from interactive optimization• Cyclic re-planning to accommodate change in features and other

project parameters• Pro-active risk analysis for making release decisions• Interactive optimization

Use case scenario ReleasePlannerTM


• Developing the right product = Essence of business success!• Decisions need to be based on objective data and transparent rules • Pro-active rather than reactive mode of operation!• Many features implemented get almost never used• Features expected from the user are not offered • Treating feature dependencies can be tedious and time consuming• Optimized response to changed market or resource conditions• Convince others by justifying your plan• Plans generated to not make optimal usage of resources available

Why this is important?


?Guenther Ruhe

[email protected]

Questions

Contact:


Documents

© Expert Decisions Inc.– All rights reserved. 1 1