|
How to Train Agile Product Owners Using Financial Terms Prioritizing stories for an upcoming sprint can lead to confusion and miscommunication between the product owner and agile teams. But putting that exercise into financial terms, such as purchase, budget, cost, and investment—a set of words that everyone understands, no matter what their area of expertise is—gets everyone thinking about value.
|
|
|
Is Your Product Owner an Overloaded Operator? Overloaded operators exist when an operator or operation has different meanings in different contexts. This usually applies to variables and sets, but it can be true for people, too. These people try to do the work of many different roles—and usually fail. If you have an overloaded people operator, analyze the work and try to divide it up.
|
|
|
Would Santa Claus Make a Good Product Owner? The elves working on Project Santa—you know, the big delivery that happens every December 24—have decided to go agile. But Santa, the product owner, is busy and not always available to answer questions or provide guidance. What kind of suggestions and improvements should they address in their retrospective?
|
|
|
Product Owner, Product Manager, or Project Owner? If you really want to get the benefit of Scrum, you have to make the mind shift to product ownership, not project management or project ownership. The product owner role is often thought of as being a requirements specifier, when in fact a good product owner is a value maximizer, and a great product owner is a product maximizer.
|
|
|
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.
|
|
|
Do Your Demos Smell? In the agile world, there is a concept of “smells,” or symptoms that things aren’t going well. Introduced by Kent Beck and expanded on by practitioners, smells now describe problems involving adoption, coaching, design, code, and teams. When we see these symptoms, we can identify opportunities to improve.
|
|
|
Snapshot: A Team’s First Steps into Shared Ownership Karen Favazza Spencer writes of the time her team members had to modernize and expand the capabilities of their legacy system. In this situation, Karen took on the role of ScrumMaster, implemented several helpful agile techniques, and empowered the team to share leadership of the project with management.
|
|
|
Identifying and Improving Bad User Stories A written user story is a very short narrative—a sentence or two—describing some small piece of functionality that has business value. User stories are intended to foster collaboration and communication, but writing these short narratives poorly can negate agile’s flexibility. Charles Suscheck and Andrew Fuqua explain some common failure patterns that will help you focus on the right role, value, and business functionality when writing stories.
|
|
|
A Product Owner’s First Glimpse of Agile Kent McDonald introduces us to Arthur, a middle manager and product owner in a medium-sized insurance company who has been assigned to take on an agile project. For those unfamiliar with agile, the terminology and techniques of agile approaches can seem strange and often a little silly when not accompanied with an explanation as to why those techniques exist. Kent explains the challenges product owners like Arthur face and how to make product owners understand agile better.
|
|
|
Hoarding: How to Prioritize Features to Clean Up the Clutter Hoarding is an incredibly common—but usually unnamed and invisible—phenomenon in corporate software development. If you’ve been doing agile for a while, you are no doubt aware of the cost of hoarding and you’ve probably removed much of it, but what happens when you aren't doing agile yet? Clarke Ching explains how to counter hoarding by prioritizing the right features.
|
|