Tracking outcomes and impact of released features

[Boleslaw Nowak]

Hello!

Trying to figure out a solution for monitoring of the released features that we release every week, and thought I'd ask for advices and how do you work with those.

As of current we do it quite manually which has its obvious flaws, with the biggest one being hard to maintain, and read - as it just grows to a gigantic Confluence table.

Wondering if you have any good patterns within Jira that serves this purpose of monitoring of the tasks - for 3-4-5-6months to evaluate the tickets impact, or any other good tips that work for you.

Currently my only idea is to make a board and filter the `Released` tickets by some kind of a label, and then work from there, but this doesn't sound like a perfect solution.

Cheers!

[Dave Mathijs]

Hi @Boleslaw Nowak I'm not sure I understand your question completely.

The title says: "Tracking outcomes and impact of released features".

When a feature is released, it normally has a version.

When a customer reports an issue for that new feature, you specify the Affects Version in the issue detail.

You can build a JQL to list issues related to a specific version.

Am I missing something?

[Boleslaw Nowak]

Hey @Dave Mathijs think its more of general question - how do you track and evaluate the features that got released.

Let's say we release something like "Change the button colour from blue to green" - the feature goes live, but after it's released its always good to track and measure the results of this change - let's say in this case it would be clicks - you get data about the number of clicks from GA or any other tracking tool - but then you want to somehow document/connect it to the released feature. 

So this is something that I'm struggling with atm, what would be a manageable way of doing this post-release evaluation. 

[Dave Mathijs]

Now I understand, thanks for the clarification!

Well, there are different methods possible:

1. You could define what success looks like before releasing the feature. Are there any specific goals objectives you want to achieve? E.g. higher conversion rate, improved user satisfaction (review score)
2. Are you using analytics tools?
3. You can define a pre-release baseline and compare it post-release
4. Collect direct user feedback through a survey of feedback form
5. Conduct post-release reviews to identify technical issues, bugs, ...

These are just a few possibilities.

[Boleslaw Nowak]

Feel we still dont fully understand each other ;)

I know how to collect the data itself - for my case its GA and some internal statistics.

Thing I'm trying to learn more about is a good approach to handling this data, and how to document it in an efficent way.

As I mentioned currently I'm doing it in a Confluence table - but this quickly grows huge and is hard to maintain, and was thinking if there's some smart way to log those results (data statistics) into Jira