The recent surge in virtual meetings necessitates an entirely new set of desirable behaviors. But how do you keep participants engaged and material useful and on topic remotely, when it's hard enough to do that with everyone in the same room? The key is keeping value delivery front and center. Here are some tips and best practices for virtual meetings that will help you continue to deliver value.
Implementing agile often means throwing out the rulebook when it comes to how teams work, how projects are organized, and even what the office floor plan looks like. This can be a difficult transition, but it's nothing to fear if you can anticipate the challenges and plan accordingly. Here are six of the greatest challenges teams face when implementing agile, along with some tips on how to avoid them.
With the traditional waterfall method of testing, achieving quality and faster time to market is difficult. Agile testing has emerged as an alternative, where development and testing take place simultaneously instead of operating in their respective silos. Let’s look at what it means to perform agile testing, what practices are necessary, and how agile testing can benefit your software releases.
There is a lot of interest in organizations around a transformation to agility. However, the focus is usually on agile development, so it may not be clear how software testing is done in agile. If you're responsible for leading your testing teams, don't let them be left behind. Here’s how you can make testers part of the transformation, too—step by step, because this is agile, after all.
People have different cultural backgrounds, habits, beliefs, interests, capabilities, knowledge, skills, and temperaments. When put together on a team, they can’t always be governed by a rulebook to become self-organized. The dynamics among them have to be understood to recognize the anti-patterns first. Here are six anti-patterns that must be avoided and remediated to help teams move toward self-organization.
Traditional project management and agile project management are two contrasting styles that are often pitted against each other, each with unique values and downfalls. The best methodology to use for a specific project largely depends on the nature of the project and its requirements. Consequently, it’s important to understand the premise of each of these styles and the attributes that differentiate them.
Fixed-price projects are a challenge to manage when using agile practices, as software teams need the flexibility to change what they are building based on customer need, and that often alters what can be done within a fixed budget. However, there are ways to achieve agility even within a fixed-budget constraint. Here are three ways to make a fixed-price project a win for all parties involved.
Refinement is time spent during the current sprint discussing and elaborating product backlog items so that they are ready for future sprints. Unfortunately, many teams do not unlock the full potential of refinement. Backlog items should be sliced, and a solution should be proposed, reviewed, and discussed. If your team is having trouble getting started, here are 18 questions you can use to trigger refinement discussions.
When you’re designing a dashboard to track and display metrics, it is important to consider the needs and expectations of the users of the dashboard and the information that is available. There are several aspects to consider when creating a new dashboard in order to make it a useful tool. For a mnemonic device to help you easily remember the qualities that make a good dashboard, just remember the acronym “VITAL.”
Tech support is notorious for having a bad reputation about their service, both on the receiving side and the serving side. Fortunately, the situation is improving, particularly in innovative organizations that are adopting an agile approach to tech support. Agile is helping customer service teams prioritize tasks, collaborate, and continuously improve. What can you do to be agile in your organization’s tech support?