|
Why Teams Stop Improving—and How to Jumpstart Their Efforts One of the most important features in agile software development is continuous improvement. However, after an initial burst of inspiration and productivity, teams may stop improving because they believe there are no issues left to address or the issues are too difficult to solve. People need to switch their mental models to keep addressing processes efficiently.
|
|
|
Using Agile Pods to Realize the Potential of Your Team Agile pods are small custom agile teams, ranging from four to eight members, responsible for a single task, requirement, or part of the backlog. This organizational system is a step toward realizing the maximum potential of agile teams by involving members of different expertise and specialization, giving complete ownership and freedom, and expecting the best quality output.
|
|
|
Agile: Don’t Worry, It’s Natural Although the idea of repeatedly exercising the full development lifecycle on smaller chunks of the requirements is newer to the software industry, it isn’t at all new to many other aspects of life and nature. We have been agile practitioners for quite some time, and the software development industry is just catching up. John Ryskowski addresses a few examples.
|
|
|
Mitigating Team Hazards without a Typical Scrum Product Owner A good product owner should be collaborative, responsible, authorized, committed, and knowledgeable. But what do you do if yours doesn’t exemplify these characteristics? This article aims to showcase mitigation plans that can be effective for overcoming Scrum violations due to the fact that you’re not working with a typical product owner.
|
|
|
Overcoming Resistance to an Agile Process Rollout Many engineering leaders and agile coaches believe that transitioning to agile is simply a matter of process training and expert advice. But frequently, it means that deeply ingrained habits need to be changed. This article identifies eight steps that address the wider organizational shifts implied by agile and will help create buy-in from your team.
|
|
|
Slipping into ScrumBut ScrumMasters don't like to talk about their own troubles or failures, even though they say it’s good to fail. They don’t like to admit it happens to them, too. Sometimes it just creeps up. If you've started relaxing your Scrum principles and feel yourself slipping into ScrumBut, take hope: You and your team can recommit.
|
|
|
Why Communication Is Key to the Agile Process We should all be much more active about improving our communication skills to be better at our jobs, but also (and more importantly) to make the most of the people around us. Whether you’re giving or receiving information verbally or through writing, no matter what your job is, communication is key.
|
|
|
Management Myth 33: We Need a Quick Fix or a Silver Bullet A new approach to projects or a new tool is not a quick fix or a silver bullet. Too often, you have ingrained, systemic problems that require a cultural change. That doesn’t mean a new approach or a new tool won’t help. It can. But you also need to adjust the environment that caused the problems in the first place.
|
|
|
A Different Approach to the Agile Product Backlog When one organization first shifted to agile, the team had trouble with maintaining the product backlog. No one could agree on priorities for items, they didn't know which item should be groomed next, and the backlog wasn't transparent to everyone. This team found a better method that works for them.
|
|
|
How Women Can Help Build Better Agile Teams The IT industry is dominated by men. But you shouldn't hire more women just to lessen the gender gap. The ultimate goal is better teams, and it just so happens that hiring more women tends to help build better teams anyway. Companies should reexamine what traits they value in job candidates.
|
|