Comprehensive software reviews to make better IT decisions
Scrum Destroyed the Product Owner Role
When trying to implement Agile as a defined process, Scrum turned BAs or other roles into order takers with the title “product owner.” This undermines the entire value proposition of product management. The product owner should be the CEO for their product or product family, building, managing, and leading to ensure that the product or service under their charge meets the needs of the consuming audience.
In Build a Better Product Owner, we define four key capability areas needed for successful product ownership.
- Vision correlates directly to value realization.
- Ensure your product aligns to your organizational goals and priorities. Is that mission/vision actionable? If not, it’s a gap.
- If the enterprise vision is clear, any level of employee can feel empowered to make decisions that align with business objectives/outcomes.
- Business outcomes and capabilities drive value prioritization.
- You don’t have to have prescribed authority to be a leader. Leaders stand up for what is right over what is easy.
- Are you giving the team every opportunity to shine/deliver their best work? The more teams use their superpowers, the greater their level of engagement, quality of work, and satisfaction.
- The best leaders view their role as a facilitator to the team’s success.
- Product owners make decisions. This mindset change needs to happen to make the product management model successful.
- Leadership is the primary capability area with strongest cultural resistance and may not be a quick win.
- Product Lifecycle Management
- Creating an environment of learning. Agile isn’t fail safe, fail fast. It isn’t a failure when you learn and improve.
- As long as product exists, the product management function is needed. At end of life, product management focuses on retirement and/or replacement.
- Read Build a Better Backlog to better manage your backlog and include tech debt and operations priorities.
- Value Realization
- Develop KPIs that are aligned to the value proposition for each proposed change. Assess satisfaction through usage monitoring and end-user feedback.
- Verify your product’s fit for purpose. Does it allow the end user to receive the value they expected?
- Manage each product as if it was its own business with profit and loss center. Define the cost of acquiring a new consumer, onboarding internal users, and increasing product usage.
- Create a simple business model to define the positioning and the value your product will deliver. Build an end-to-end financial model and plan for the product and all related operational support.
The biggest cultural shift for most organizations is that the product owner owns prioritization and sequencing decisions for all product changes. Product owners by proxy hinder your Agile transformation and the empowerment to be successful. In “Why we Need to Rethink Product Management in an Agile Practice,” posted on June 4, 2020, Anthony Marter does an excellent job highlighting how the Scrum definition of the product owner role does not provide the leadership and ownership needed to truly manage a product or service. As with low-value business analysis, product owners as order takers reinforces the cultural divide and belief that the delivery team does not own decisions or is not empowered to recommend improvements.
This can be further perpetuated in teams that rely solely on the Scrum backlog being updated in their delivery management tool (e.g. Jira, Azure DevOps, GitHub, Trello, Zoho Sprints, DreamCatcher Agile Studio, Rally, Yodiz, VersionOne, VivifyScrum). Even if the product owner is using a product management platform (e.g. Aha!, ProductPlan, Productboard, Airfocus, Targetprocess, ProdPad, Roadmunk), there is far more to product management than just backlogs and simple roadmaps (backlogs grouped into releases over time).
- The product owner must own the product and make the final decisions.
- Good product owners consider their stakeholders and delivery team recommendations, but in the end, make the decision.
- Don’t let the simplicity of Scrum turn your product owners into proxies and order takers. There is little value to a Scrum product owner who simply updates a backlog on behalf of the real product owner (stakeholder making the decisions).
- Use the capability model in Build a Better Product Owner to overcome the limited role experienced in too many Scrum teams.
Want to Know More?
- Build a Better Product Owner
- Strengthen the product owner role in your organization by focusing on core capabilities and proper alignment.
- Transition to Product Delivery
- Stop delivering projects. Start delivering products.
- Implement Agile Practices That Work
- Improve collaboration and transparency with the business to minimize project failure.
- Build a Better Backlog
- The quality of your product backlog is key to realizing the benefits of Agile.
- Understanding Scrum: Why Do Product Owners Have Three Ears?
Is it true that everything that can go wrong will go wrong? Don’t bet on it to not.
So you’ve gone Agile. You do daily scrums, retrospectives, and all the “right” Agile ceremonies. But still your organization isn’t quite convinced. It is now critical to balance the drivers and goals of both Agile and traditional thinking in order to achieve organizational success.
While Microsoft is not a prominent player in the RPA space now with its Power Automate solution, compared to Blue Prism, UiPath, and Automate Anywhere, its latest acquisition of Softomotive, maker of WinAutomation, demonstrates Microsoft’s dedication to mature and expand its RPA offerings.
Test data management tools offer you the ability to provision, mask, and govern the access and use of your test data, alleviating these manual, laborious and error-prone tasks from your testing, operations, and DBA teams.
No matter how good your product roadmap and backlog are, they are only as good as your audience’s ability to understand your vision and priority.
The scrum master is like the conductor of an orchestra, ensuring that every piece fits together at the right time to create something greater than the sum of the parts. You don’t have to know how to play each instrument, but you do have to understand what each part contributes to the overall masterpiece.
Tools are important to product teams, but only when they support solid people and processes.
Agile systems delivery (implemented through Scrum) is quickly becoming an accepted norm in IT. But using Scrum successfully in an organization requires a deep understanding of how it works and why. For example, many of our members don’t understand the importance of selecting a Product Owner who has three ears.
Aha! introduces scenario planning to give product owners the ability to create and compare multiple release approaches based on team capacity and backlog priority.