5 Tips on How to Build Agile Teams in the New Workplace.
As business leaders look for ways to become more agile in the workplace, we're diving into how they can effectively build agile teams for any given project.
Given the pandemic-driven, drastic change in the workplace, business leaders should rethink how to build and optimize agile teams.
The widespread adoption of collaborative technologies, along with the growth of remote work strategies across an entire organization, gives new meaning to the word "agile". Most organizations originally used the agile teams' concept for software development, but it's also appropriate for numerous business activities, including marketing strategy development, HR assistance during open-enrollment periods, and CX improvement in the contact center, just to name a few.
When thinking about how to build an agile team, redefine the definition from a software or product development methodology to a more flexible approach to any problem-solving in the organization. What's more, broaden the thinking around who should be on any given team, because with collaboration technologies and work-from-anywhere strategies, the possibilities are limitless.
The following are five tips for business leaders on how to build agile teams in the new workplace.
Read more about: How to locate and hire the right offshore development team?
As you're building an agile team for any project, start with the end goal. What are you trying to achieve, and what skills, technology, and hours do you need to meet the goal? Only then can you build the team.
Skills from team members may range from customer engagement experience to legal expertise to software development. Given the project's demanding timeframe, you may need a team spanning multiple time zones to extend the workday. Or with work-from-anywhere now widely accepted, perhaps some employees would select to work odd hours. Given that the team will be working in different time zones or off-hours, you'll need team collaboration workspaces to keep everyone engaged and updated on progress.
Once you've selected the team, the members need proper leadership to get started. Depending on your business culture, employees may be shy about sharing ideas ("What if they don't like them, or if I don't get credit for them?"), sharing workload ("If I want it done right, I have to do it.") or asking for help ("I'm out of my league, but if I ask for help, I'll look stupid.").
Set the ground rules to build a strong foundation. Make sure the team knows that change is constant and that they can't map out the path to the end goal. They need to work as a team, be flexible and accepting of change, report on progress in short intervals, and check their egos at the door.
In-person meetings certainly have value during projects, but employees are often more productive working from home offices -- provided they have the necessary technology. For example, collaboration capabilities are imperative to success. The ability to launch an on-the-spot video or screen share, use a digital whiteboard to brainstorm or exchange ideas with team members via perpetual chat in a team workspace, can drastically improve a project's creativity and timeliness.
Think of how much more responsive to change employees can be with the right technology enablers. For instance, use the technology to help put structure around the project. There should be regularly scheduled meetings, as well as the ability to start an ad hoc meeting. Project management automation can remind people at regular intervals to update the team in the workspace. This eliminates the tendency to work in a bubble rather than collaborating with the team.
Agility, by definition, is the ability to move - or change - quickly and easily. Therefore, agile teams can't get bogged down by failure. Rather, they need to embrace the fact that failure will occur, sometimes at multiple points along the way. This is usually a good thing because we learn from failure and improve through it. And by breaking projects into short pieces, it's easier to uncover and resolve failures along the way.
Good leaders will use failure as a teachable moment.
Even though failure along the way can be good, ultimate success is the goal. Business leaders and employees have to rethink what defines success.
For example, one company added AI-enabled virtual assistants to guide customers through a self-service knowledge base in a very quick turnaround at the start of the pandemic. During the project, the confident team decided to open the new technology to a trial audience and found terrible ratings. Why? Because they only identified four spots along the customer journey when customers needed to escalate to a live agent, and they realized there were actually eight spots.
So, there were two points of failure: missing four escalation points and opening the technology to customers without telling them it was a trial. As a result, they slammed the company with low ratings, affecting overall customer satisfaction scores.
Through that failure, though, they were able to improve the self-service program. They developed a new process for customer testing of new technology with focus groups, versus randomly making it available. As a result, they found another two points of escalation they hadn't yet uncovered. And in the future, they know how to gather customer feedback without affecting their ratings. Once they released the revised program to customers at large, their ratings increased even more.
Ultimately, the project was successful, and the team should be rewarded. But individually, business leaders should call out those who made and fixed the points of failure.
Robin Gareiss, Metrigy Research
In a no-risk discovery we look at how your work moves between your systems today and show what one connected system would do differently. You pay only if you proceed. Or see how we approach it.
More on the same problem:
An agile team is small, cross-functional and organized around a clear goal rather than a department. Its members can make most decisions without escalating, report progress in short intervals, and treat change in requirements as normal. The team works in the open, with visible tasks and regular check-ins, and it reviews its own results and adjusts how it works. Trust and candor matter more than process: members ask for help early and share unfinished work for feedback rather than protecting it.
Most guidance puts an agile team between five and nine people. Below five, the team lacks the mix of skills to finish work without waiting on others. Above nine, coordination costs rise, meetings get longer and quieter members disengage. A larger effort is better split into several small teams, each owning a piece of the goal, with a light coordination layer between them. The right number is the smallest group that holds every skill the work needs most weeks.
At minimum, a team needs someone who owns the goal and sets priorities, the people who do the work, and someone who keeps the process running and removes blockers. In software these are often the product owner, the developers and the scrum master, but the pattern applies in any function. The important point is that the roles are about responsibility, not seniority. Titles can stay as they are; what changes is that the team, not a manager, decides how to reach the goal.
Remote agile teams need deliberate structure to replace the hallway conversations an office provides. Agree on working-hour overlap across time zones, hold a short daily check-in on video, keep a shared board where every task and its owner is visible, and use a persistent team chat channel for questions. Record decisions in writing so people in other time zones can catch up. Invest in the tools, since a team that cannot share a screen or whiteboard on demand loses the speed that makes it agile.
The most common mistake is adopting the rituals without changing the authority. A team that holds standups and sprint reviews but still waits for a manager to approve every decision is not agile; it is a traditional team with more meetings. The second mistake is assembling the team from whoever is available rather than from the skills the goal needs. Start with the end goal, choose the members for it, set ground rules about change and candor, and then let the team run.
"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.
Say who you are and ask. A person replies within one business day.