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.
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.
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.
Introducing a full agile framework can be daunting and cumbersome. Instead, try beginning with the method's core focus: continuous improvement. Retrospectives are the starting point of your agile journey and can help you solve the most immediate problems in your process, leading you down the road of process improvement.
Program planners in IT organizations have a dilemma: On one hand, their agile teams tell them that if requirements are defined up front, agile teams cannot operate; but on the other hand, the program’s budget and scope need to be defined so that resources can be allocated and contracts can be written for the work. How does one reconcile these conflicting demands?
Prakash Pujar writes about his team's experience adopting some of the best agile practices to make their process extra lean and increase efficiency by increasing throughput—all without any change to the agile framework his team was following before and after. Here, he talks about some of the lean practices that worked for them.
This article addresses a process where a team moved from a traditional waterfall model to using agile elements in order to deliver a product to a government agency. It talks about typical problems that come up in a transition to agile, complications from distributed teams, and the advantages and disadvantages of the process for government or nongovernment clients.
Agile is growing up and is now officially a teenager. It has moved from being a somewhat rumbustious child with some overzealous followers and a skeptical management crowd to something that is generally accepted by the mainstream IT community and particular management. Has the agile community lost something? Are the founding members and early practitioners evolving the practice? Is this good? Well, the answers are yes, yes, and maybe.
Using metrics such as cumulative flow to monitor throughput and quantitative thinking may not seem very humanistic, but by depersonalizing the work being done, we can focus our energies on solving actual problems instead of conducting a daily witch-hunt and shaming people into high performance.
Sarah Johnson explains the role of writing in an agile world and how to educate your team members. Remember, agile takes into account that each situation is unique, and you need to determine what makes the most sense for your particular Scrum team.