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.

 
1 favorite thumb_down thumb_up 3 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

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 2 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Madeeha Khan
    By Madeeha Khan  ~  2 months ago
    reply Reply

    Hi Nupur, Can you please update your profile. As of yet, it is just 1 line given there.

    Hi Nupur & Nilesh, Can you please share any video/ presentation as a speaker.The links you provided above shows a website with content. It looks like an article. Please visit talk acceptance process.

    I feel that this ICE metrics seems more like quite traditional planning, reporting and documentation. Can you please help me in understanding it aligned with agile way.

    • Nupur Waikar
      By Nupur Waikar  ~  2 months ago
      reply Reply

      Hi Madeeha,

      Thanks for your response.  In process of updating the required fields.

      About your query on ICE metrics, traditionally we developed software, tested and sent to customer. then came Agile where we developed product iteratively by getting customer feedback regularly and then released the software.

      However even though today we have develop software by engaging customer there is no way to measure the customer engagement in terms of where the feature is exactly heading towards. We measure product success in terms of revenue after the product is released. Also the measure of how the feature performed is very rare.

      My idea is to measure the feature(not the entire product) acceptance by the customer while the feature is being baked and not wait until end when we see the revenue metrics. Using this metrics scrum teams and leadership can decide is it even worth investing further and makes sense failing fast and pivot.

      Agile provides us an opportunity for early feedback. Our idea takes it further to next level and make the same customer feedback measurable in terms of the ICE metrics.

      • Madeeha Khan
        By Madeeha Khan  ~  2 months ago
        reply Reply

        Thanks Nupur.