Resources > Articles

How Usage Analytics Support Agile Development

Post Author
  • Keith Fenech is vice president of software analytics at Revulytics and was the co-founder and CEO of Trackerbird Software Analytics before the company was acquired by Revulytics in 2016. Prior to founding Trackerbird, Keith held senior product roles at GFI Software, where he was responsible for the product roadmap and revenue growth for various security products in the company's portfolio.

How Usage Analytics Support Agile Development

As we enter the spring trade show season, the mantra “go big or go home,” characterizes the directive for product managers preparing for events. Whether it’s helping executives make big splashes with product announcements, facilitating live demos that leave big impressions, or simply mastering the newest jargon so we can tally its usage for our amusement during executive keynotes, this mantra extends across our space.

But chances are, as you’re walking show floors over these next few months, meeting with customers one on one, or talking with users in educational sessions, you’re more concerned with finding the small things—the details and feedback you can leverage to make tweaks here and there to drive irresistible product releases. 

This is the time of year when I think the value of agile development is really on display. With its focus on delivering working software in iterations, agile accelerates product delivery to give executives cool stuff to talk about, or even demo, at big events. And by those same means, it lends developers and teams the ability to more easily fix or change things according to customer feedback.

But it doesn’t always work. Cultural roadblocks are often the chief culprits, as organizations may find it difficult to adopt the flexibility that agile demands. However, as you seek to further evangelize and gain greater success with agile development in your organization, elevating the importance of something concrete can help: usage data. 

Developers and teams surveyed by VersionOne in its State of Agile report indicated that their organizations adopted agile methodology in search of three benefits: to accelerate product delivery, enhance their ability to meet changing priorities and enhance their teams’ productivity. Let’s take a look at how software usage analytics can help achieve these agile goals.

Accelerate Product Delivery

In agile development, work takes place in cycles and is tested in two- to four-week periods to create a product increment. The goal is to develop shippable product increments, according to Agile Velocity, a leading agile advisory firm based in Austin, Texas. 

Software usage analytics help speed these development cycles. Product managers can measure effectiveness and adoption in a live install base, gaining feedback across an enormous number of parameters in real time. Having the ability to segment data by operating system, machine architecture, platform type, language, geography, etc. and collecting usage data in real-time from the latest release, empowers managers to make fast, data-driven decisions on where to focus the next agile development cycle.  

This allows the team to quickly prioritize and facilitate everything from small changes, like moving a button or changing a color scheme, to enabling bigger changes in workflow or function. 

Manage Changing Priorities

One of the chief reasons organizations adopt agile development methodologies is to better accommodate changing priorities—whether those changing priorities are driven by customer demands, sales requests, marketing needs or other stakeholders and influencers.

Having usage data helps validate requests coming in through various sources, and enables you to make a strong case for or against including a change, improvement or even legacy functionality in a development cycle. Consider how often you field requests to support a legacy feature that is incompatible with an upcoming release. Being able to quickly identify which customers are leveraging that functionality and how, allows companies to make insight-driven decisions about moving forward. Getting a complete picture of use lets you determine whether it makes sense to funnel development resources toward porting the feature onto the new platform, or whether functionality in the new release will suffice, while gaining knowledge to create data-driven offers that encourage customers to upgrade.   

Increase Productivity

By automating feedback collection, usage analytics can facilitate the productivity increases borne of agile development in two ways. 

First, with a combination of usage analytics and in-app messaging, you can test your assumptions in real-time within hours of actually deploying new functionality. Usage analytics allow you to pinpoint where in the workflow you need more user feedback and reach the user within the context of that workflow using in-app messaging, soliciting targeted and relevant feedback. This saves time and resources of an already taxed team.

Second, ensure that the user feedback is valid. Often, in personal customer outreach, those who are willing to provide feedback tend to sit at two ends of the spectrum: they are either very happy, or very unhappy, with your products. In turn, there is a tendency to report only on what worked well or failed, painting an incomplete picture to inform further development. By leveraging usage analytics, you can pull the experiences of a broader customer community and get unbiased feedback along the spectrum of product use.

Data-Driven Agile Processes

Agile Velocity frames the product development dichotomy well. Often the assumption is that customers already know what they want, developers know how to build it and nothing will change along the way. In reality, customers often discover what they want, developers discover how to build it and many things change along the way.  

Software usage analytics accelerate and help you evangelize agile development, maximizing your ability to manage competing interests and all the pressures associated with product cycles to deliver products that resonate with customers and features they can’t resist.

Author

  • Keith Fenech is vice president of software analytics at Revulytics and was the co-founder and CEO of Trackerbird Software Analytics before the company was acquired by Revulytics in 2016. Prior to founding Trackerbird, Keith held senior product roles at GFI Software, where he was responsible for the product roadmap and revenue growth for various security products in the company's portfolio.

Author:

Other Resources in this Series

Most Recent

A dashboard on a website showcasing product management measurement
Article

Measurement-Driven Product Management

If you are a vice president, director or team leader for a product management function, one of the biggest challenges you face today is how to demonstrate the team is making a significant contribution to top line or bottom line targets. If you can’t measure your team’s effectiveness, or if you are focused on the wrong metrics, your headcount and budget allocation could be at risk.

Product life cycle: Introduction, Growth, Maturity, Decline
Article

23 Metrics Mapped to the Product Life Cycle

Learn what to measure and how to avoid vanity metrics during each stage of the product life cycle: development, launch, growth, maturity and decline. Also learn the difference between a mission and objective and how to identify which stage your product is in.
ROI of being market driven. An image with illustration dollar signs
Article

The ROI of Being Market-Driven

Market-driven companies are more profitable, twice as fast in getting new products to market, and have higher customer satisfaction levels.
Article

23 Metrics Mapped to Each Stage of the User Journey

23 metrics for the user journey, which is the path a user takes while interacting with your product (sometimes called a flow funnel).
A person holding up a sign that say who is responsible
Article

Product Marketing or Product Management

Roles Before Titles The job titles of product marketing manager and product manager are confusing enough to start raging debates about who does what. Organizations often transpose the job titles, adding to the confusion. This article

OTHER ArticleS

A dashboard on a website showcasing product management measurement
Article

Measurement-Driven Product Management

If you are a vice president, director or team leader for a product management function, one of the biggest challenges you face today is how to demonstrate the team is making a significant contribution to top line or bottom line targets. If you can’t measure your team’s effectiveness, or if you are focused on the wrong metrics, your headcount and budget allocation could be at risk.

Product life cycle: Introduction, Growth, Maturity, Decline
Article

23 Metrics Mapped to the Product Life Cycle

Learn what to measure and how to avoid vanity metrics during each stage of the product life cycle: development, launch, growth, maturity and decline. Also learn the difference between a mission and objective and how to identify which stage your product is in.

Sign up to stay up to date on the latest industry best practices.

Sign up to received invites to upcoming webinars, updates on our recent podcast episodes and the latest on industry best practices.

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.

Subscribe

Subscribe

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.