It’s the end users that all too often end up with the least say in the whole process. The ironic thing is they are – in almost all cases – the most important piece of the puzzle. AndPlus understands this.
We insist on giving end users a prominent place at the table for any project we undertake. Here’s why:
When a new client contacts us to discuss a custom software project idea, the initial inquiry usually comes from a department manager, IT lead, or a senior leader. These people have the big-picture vision, decision-making power, and at least some control over the budget.
When we discuss our development process and how we involve the end users, we sometimes get push-back. They don’t want the end users involved because:
We know from experience that involving the end users in a major software project has many benefits. Leaving them out introduces significant risks.
Why is including end users as stakeholders in a software project so important?
The notion that you can’t spare your end users for a weeks-long software project is not without merit. Often, the users most valuable as stakeholders on a software project are also the most knowledgeable, go-to, high-performing employees. They’re the ones keeping your department running. How do you compensate for lost productivity by taking them away from their day-to-day duties?
In most cases, you don’t need to take them away from their regular jobs full-time. On average, they might be needed for project activities half of the time, or even less. More involvement will be needed in the early stages when requirements are being determined and the product roadmap is being defined.
During the actual development sprints, end users are likely to be needed only during sprint planning sessions, demonstrations, and sprint reviews. Altogether these might average a few hours per week.
A major software project is a significant investment, and end users might be needed full-time for a couple of weeks or more. Many organizations include temporary help in their major software project budgets.
Yes, it can be a pain to recruit and hire sufficiently competent temp help for a few weeks. But it will be worth the trouble if you end up with a better system.
Knowing what we know about the value of end users in a software project, we insist on their involvement early and keep them involved in some capacity throughout the project. Here are some of the areas where we need end-user involvement:
We need the end users to tell us who they are, what they do, how they work, and their pain points. We want to know about their physical environments and their current tools’ shortcomings.
We spend a large chunk of time with end users determining what the system requirements are. We make sure they are complete, correct, and consistent.
From the requirements’ specification, we team with end users to find the absolute minimum feature set that will constitute version 1. Opinions can vary widely on what the MVP looks like, and we work hard to get buy-in from everyone while keeping that initial version manageable. We also need user input to define what features to add later, and in what order. That is the product roadmap.
Now the user experience (UX) designers get involved and begin designing the user interface. Users are needed to review and provide feedback on the prototypes. This feedback is immensely valuable. It helps keep us on track to providing a software solution that is both useful and usable.
Before each sprint, we gather with the users and other stakeholders to prioritize backlog items that will be included in the sprint. We want to make sure we are working on the things that will be of most value.
At the end of each sprint, we have a release candidate demonstrate to the stakeholders. We rely on the feedback from the most important people in the room: the end users; the ones using the software when the project is finished.
Clearly, the success of a major software project depends on the involvement of the people that will use the final product. Ignoring them or leaving them out of the process is a recipe for disaster.