In Agile world today, organizations are solving problems by building Epics/Features in iterative fashion. The release frequency may vary from every day to every quarter depending on the organization’s size & business demand. There are few business or product management artifacts which are referred pre(to show need of the feature) or post(to know the revenue of the product) epic execution. What if there’s a way to gain more information on feature’s acceptance by the market or target customers in an iterative fashion while the Epic is being developed. Every organization has processes in place to collect very rich data by having customer demos & calls, beta testing or various other avenues. However this valuable information may not be available under one umbrella.

Hence, this experimental model that can help every Epic(scrum teams, leadership & other stakeholders) to understand progress of the Epic/feature from business side while it is being developed. Also, decisions, like if the version v1 of an Epic is released then is it worth investing in v2 . Let’s call it Iterative Customer Engagement & Adoption Metrics.

The metric is updated regularly (quarterly or monthly) while the Epic is being baked & could be reviewed by the stakeholders anytime. This will provide a live Epic health that gives confidence and motivation to the development teams as well as to the leadership to make strategic decisions.

Iterative Customer Engagement & Adoption Metrics consists of following parameters. The parameters may vary based on your release frequency.

  • AWARENESS: How many new customers have been informed and are aware about the upcoming Epic.
  • INTEREST:How many new customers have shown interest to upgrade/buy the product just to use your feature ?
    .
  • PRESENCE:How many customers have attended at least one of your demos?
    demos in last quarter.
  • CONTRIBUTE: How many new requirements have been added or updated in the Epic based on customer feedback.
  • BETA: How many customers contributed in BETA testing specifically for your Epic.
  • ADOPTION: How many new/existing licenses acquired | Expected v/s realized growth | How many customer escalations have been raised specifically to your Epic

We will discuss the benefits of this model in more detail during the talk. This will help the entire agile community as well as business community to be more efficient in making decisions.

 
 

Outline/Structure of the Presentation

Objective : 5 mins - Challenges in understanding the feature health. Why the need of iterative ICE.

Message : 30 mins: Present the ICE model with the benefits to services and product industry

Conclude: 5 mins : Summarize the need and the benefit

Q & A : 5 mins

Learning Outcome

Know the Single source of truth about how customers perceive your feature sprint by sprint without saying anything about it.

Importance of reading customer pulse regularly by credible data points.

Impact of development not paying attention on the business side.

Target Audience

Scrum Teams, Leadership, Management, PO, SM, PM,

Prerequisites for Attendees

A basic knowledge about software development life cycle

schedule Submitted 1 year ago

Public Feedback