|
The Agile Alphabet, Part 1 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.
|
|
|
Kickoff Meetings Give Your Agile Projects a Running Start 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.
|
|
|
Examining Cross-functionality Bias on Software Development Teams 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.
|
|
|
Warning Signs That Your Agile Effort Has Lost Its Focus 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.
|
|
|
7 Qualities of High-Performing Agile Teams 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.
|
|
|
Continuous Improvement Activities beyond the Retrospective 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.
|
|
|
3 Ways Distributed Design Teams Can Stay Agile 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.
|
|
|
Continuous Digital: A New Mindset for New Work Large companies traditionally have run software development projects so that after delivery, the project finished and the team dissolved. In the digital age, one might think the experience of running and delivering projects would be an advantage, but the legacy mindset and practices of corporate IT projects are actually a hindrance. Digital work needs to be ongoing, which requires a different management approach.
|
|
|
What Kind of Agile Coach Should I Hire? Having your organization make the mental shift necessary to adopt agile is the first important step in an agile transformation. But once you decide you want to change, now what? Should you attempt your agile adoption yourselves or hire an expert? Joel Bancroft-Connors details the benefits and downsides of going it alone and of using contract, consultant, and full-time agile coaches so you can decide what's best for you.
|
|
|
The 4 C’s of Managing Distributed Agile Teams Scrum works well for collocated teams, but working with distributed teams brings its own different challenges. There should be some controls in order to prevent instability, ambiguity, and tension from turning into chaos. As the ScrumMaster is the servant leader of the team, here are four important initiatives the ScrumMaster can take to guide their teams—the four C’s of managing distributed agile teams.
|
|