Developing a product that’s valued by your customer is pretty much the bread and butter of Agile project management. To achieve this, you need to be sharing project progression and prototypes with your stakeholders (and end-users, if separate) at every iteration of your project.
The Importance of Customer Feedback in Agile Projects
Whether you’re producing a ground-breaking app for digital natives or a new CRM for your client’s operations team, preferences over accessibility and functionality will vary hugely. As a result, it’s essential that throughout your project, preferably after every Sprint, you share new features with your customers to determine whether:
Features are actively providing value and not simply convoluting the product
Features are accessible in terms of design and functionality for your stakeholders and importantly, your end-users.
By inviting this customer feedback before the final product is launched, your team can save time and money on pushing unnecessary features forward. What’s more, you’ll end up with a more valuable and refined product, accurately tailored to your target audience.
Did you know that a whopping 98% of respondents to the VersionOne 2016 State of Agile Report shared that their organization had realized success from taking an Agile approach to projects? As the first Agile principle, customer satisfaction and feedback are central to that success.
3 Strategies for Integrating Customer Feedback
Accessing and integrating user feedback – without overburdening your project with an endless list of features – can be a challenge.
Fortunately, there are a number of strategies you can take to gather feedback effectively while preventing your project from over-extending.
1. Access Regular Customer Feedback
Before you’re able to integrate user feedback, you first need to access it. To do this, project management strategists suggest taking a three-step approach to accessing feedback from stakeholders:
Access: First, teams must find and identify a set of target customers that can be relied upon to provide accurate and timely insight, for example in the form of a well-maintained customer panel or advisory board.
Listen: Once a customer panel or advisory board has been secured, teams must build skills to actively listen to them. This should go beyond a single focus group or survey and should feature regular interaction, throughout the project, either in person or via online collaboration tools. Customers should be probed on their real needs, pain points, desires, and objective feedback on early designs and prototypes. This will also help to cut back on unnecessary features.
Communicate: Ensure that what is learned through this listening process is clearly converted into prioritized use cases that explain the value of each feature, by communicating user insights to the entire project team.
2. Integrate Customer Feedback with Sprints
The customer feedback collected should then be integrated at every project Sprint, alongside stakeholder feedback (if separate to the end-user group.)
One way to achieve this is by taking a Scrum approach to Agile project management. If you’re new to Scrum, the approach involves a Product Owner who communicates evolving business goals and customer feedback to the development teams.
In Scrum, the Product Owner retains a bird’s-eye view of the project and meets with the development team and ‘Scrum Master’ on a daily basis, to share customer feedback and insight. Customer feedback, alongside stakeholder goals and needs, will then form each project Sprint.
Following each Sprint, Scrum teams hold a Sprint Review, to present on what’s been completed to stakeholders. This process pushes team accountability and ensures that each Sprint’s completed tasks align with the project’s customer goals.
3. Allow Stakeholders to Manage Feature Prioritization
While integrating customer feedback, it’s vital that the product doesn’t go overboard with every feature requested by your customers.
A key way to do so is by utilizing a workflow that puts your stakeholders in the driving seat for feature prioritization. This can either be done via a physical scrum wallboard or via an online collaboration tool.
Creating a Physical Scrum Wallboard
In order to manage feature prioritization collaboratively with their stakeholders, Jonathan Roger, Operations Director and Certified Scrum Master at software development company AndPlus, explains that they create a physical board for their Scrum task cards:
“One way that we keep track of scope with our clients is by using different colored task cards on our project management wallboard to represent items that were added after a release plan was created,” Roger shares.
“This makes it visually easy (for both us and the client) to identify items or features that were added after the initial project scope, so need to be traded with another feature of equivalent development hours in order to stay within budget, or postponed to a later release.”
This allows AndPlus to put feature prioritization in the hands of their clients while keeping the project from growing beyond its scope and budget.
Integrating via an Online Collaboration Tool
Software development team Praxent also takes a visual approach to scope management and have developed their own online collaboration tool to share with clients.
CEO and Founder, Tim Hamilton, shares that the Praxent team developed a custom reporting and analytics dashboard, to place feature management in the hands of their clients:
“Our dashboard provides a play-by-play on feature development progress, allowing clients to see the impact it would have on production should they decide to shift direction or re-prioritize” Hamilton shares.
“Additionally, we provide them with data on how far their budget dollars will stretch, allowing them to control feature scope as they choose to add or swap in new features.”
While not all Agile teams will have their own custom-made dashboard to play with, there are many online collaboration tools available, allowing teams to take a similar transparent approach to Kanban project management.
Limit the number of tasks allowed within each Sprint
Look for a tool that allows you to share your project roadmap with your client transparently, then limit the number of features created within each Sprint.
By laying out all tasks in a project Sprint, including time estimates for how long you expect each task to take, and sharing this roadmap with your client, you can define a limit on the number of feature tasks per Sprint.
This way, you can provide your client with the ability to manage feature prioritization, as they can swap features in and out of each Sprint. This will enable transparency over how the changes will impact on the budget and schedule.
For further strategies and advice on taking an Agile approach to project management, download our free white paper, Staying Agile: 5 Best Practices in Software Project Management.
Although regularly embracing customer feedback can feel like a daunting prospect to some software teams, with these simple strategies, it doesn’t have to be.
Do you have any experience in engaging customer feedback within Agile project management? We’d love to hear your thoughts and questions below!
MeisterTask
Agile Task Management Made Simple
