Hi Naresh,

Here are my responses, as promised.

Question:

Where can I read more about your experience?

Response:

Quick Story - 1:

• The team: PO, developers and Scrum master.
• Product owner was unsure about how to prioritize when there were multiple user stories having same business value and urgency.
• Decided a mechanism to log product usage in a table for future so that they can prioritize enhancements on most used features first.
• Product Usage Metrics logging started.
• Over a period of time, PO used data from this table to prioritize enhancements in more creative ways than earlier intended. (Like prioritizing highest paying customer used feature first, some other time, prioritizing for customer whose subscription is going to expire in current month) - See Graphs in next section

Quick Story - 2: (Continued from story 1)

• Developers expressed happiness when a customer told them how much time he saved because of a new feature.
• Thought we could aggregate and display this data (time saved x no. of times a feature is used) in a live dashboard to motivate developers.
• Did it. Developers now look forward to know how they impacted the customers.

Quick Story - 3: (Continued from Story 2)

• When the team had multiple solutions to go for an enhancement, they decided to perform A/B testing.
• Put all the solutions into beta env and tracked usage metrics alongside bug statistics. 
• Correlated bug data with usage metrics to see which solution was used most.

Question:

Can you please provide more details around which specific product usage metrics you plan to cover?

Response:

The product usage metrics I am going to cover are:

1. No. of Hits Per Feature Per Period (and variations of the same)
2. Time Saved Per Feature per release  (To motivate developers)
3. Bugs per 100 hits per solution (For A/B testing)

Question:

Do you have any samples you can share?

Response:

I have the following handmade graphs. I will demo Grafana dashboards in my talk.

Please let me know in case i need to change/add/delete something.

Thank you.

Regards,
Kiran

Hi Naresh,

Thanks for going through my proposal.  Can you please give me a day's time so that I can come up with a small writeup with points that answer your questions?

Thank you.

Regards,
Kiran

Hi Aino,

Thanks for taking a look at my proposal and letting me know your feedback.

I am going to share 3 quick stories, 3 minutes each. 

I confess the word 'interactive' is a bit of a stretch :)  I can reword it or remove it if you suggest.  There are two places where interaction with the audience will happen:

1. As a intro to the topic, i plan to ask a question, for which audience can respond and i can take 2 or 3 responses.

2. Q&A slot at the end

To answer your question about time for learning outcomes, yes, each story will deliver a learning outcome.

Please let me know if this looks okay or needs some modification.

Thank you.

Regards,
Kiran