Process Improvement

We know that teams and individuals who take ownership of their work outperform—often by 50 percent—those who don’t. And in agile, team ownership is a key principle. However, leaders often struggle with letting their teams own their work. Leaders are afraid that if they trust, their teams will fail. So leaders must create a culture of trust and help their teams take ownership. But what if the team builds the wrong product? Teams must align with the strategy and purpose of the business as well as with value to the customer. Finally, the organization must deal honestly with ambiguity.

Free? Is anything free these days? Based on her experience working with organizational leaders and her research into what drives organizational performance, Pollyanna Pixton shares six ideas—and the keys to their effective implementation—to help assure the success of your agile teams. As a bonus, her suggestions won’t cost you a thing. Pollyanna’s first free idea is how to create a culture of trust—the keystone of open collaboration—within your team and organization. The second free idea is about ownership—how to give it and not take it back.

Many organizations are childlike. They blithely plan the project as if nothing will go wrong. And then, when something does go wrong, they are shocked and dismayed. Risk management is not just worrying about your project, and it is not about running away from risk. Risk management for software projects is all about when you make decisions and when you take action. How do you deal with uncertainty? When do you decide to deal with a risk while it is still just a risk, and when do you decide to wait to see if the risk does turn into a problem and manage it then?

Are you an agile practitioner who wants to take agility to the next level? Are you looking to gain real value from agile instead of simply more talk? Even though many are using agile methods, not all are seeing big returns from their investment. David Hussman shares his experiences and describes a short assessment that you can use to identify both strengths and weaknesses in your use of agile methods. Creating an assessment helps you look at the processes you are using, examine why you are using them, and determine whether they provide real value.