Too often, customers have a “fake certainty” about the problems they want to solve. They might not have defined the real problem, but they have frequently defined the solution anyway. The risk is that we might build the wrong thing. When the product owner works with the customers to define the problem, then works with the team to define the solution, everyone can win.
DevOps is more than adopting the right set of tools; it's a cultural shift that incorporates testing at each stage of the agile project lifecycle. Continuous testing is key to unlocking this culture change because it weaves testing activities into every part of the software design, development, and deployment processes, which helps everyone involved communicate more, collaborate better, and innovate faster.
The world of agile has many terms for concepts, principles, and practices common in the community. Ben Kopel came up with a list of some of the most important words used when practicing agile and organized them into a glossary with one term for every letter of the alphabet. Here's the second half, with N through Z.
The world of agile has many terms for concepts, principles, and practices common in the community. Ben Kopel came up with a list of some of the most important words used when practicing agile and organized them into a glossary with one term for every letter of the alphabet. Here's the first half, with A through M.
Agile projects are ideally a collaborative effort among the team members and with the customers, and the planning process should be a similar endeavor. Everyone should get a clear understanding of the project as well as their respective roles and responsibilities. As the saying goes, well begun is half done. A well-planned kickoff meeting sets the tone for a successful project.
Cross-functionality means having all the necessary people and skills on one self-organizing team. Unfortunately, the execution of cross-functionality is often biased. The main traps we fall into are misunderstanding the value of specialization, hero worship, and not “walking the cross-functional talk” as organizations. Let’s examine each of these pitfalls in the hope that your teams may avoid them.
Agile should be about using tailored practices, techniques, tools, and team organizations that fully align to your business context. But the world of cookie-cutter solutions strongly influences businesses and their IT teams to follow their one-size-fits-all frameworks, methods, and tools. Such an approach often introduces many risks, so beware of the following symptoms that may indicate that your agile team has gone astray.
A high-performing agile team delivers exceptional results time and again, irrespective of the challenges they encounter. While their results may seem magical, lots of effort goes into building such a team, on the part of team members themselves and their leaders. Here are seven common qualities high-performance teams exhibit that you should strive for when building your own agile team.
One of the principles behind the Agile Manifesto is “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” Unfortunately, many associate that practice with performing team retrospectives at the end of a sprint, or periodically in kanban. But if you seek to build a high-performing team, there are more improvement activities you should consider adopting.
Having a design team an ocean away presents some challenges, including misunderstandings that often result from cultural and linguistic differences, occasional time zone conflicts, and difficulty always keeping everyone in the loop regarding decisions that are being made. How do we combat those challenges? Here are three strategies that can help keep your distributed design team on track.