Implement and Monitor Key Performance Indicators (KPIs)The post will focus a concise checklist summarizing key action points for that activity to reinforce learning and provide a quick reference guide.
Browsing CategoryEnterprise Agile
Evolving Agile Portfolios Through Continuous Feedback Loops
Let’s face it—when Agile’s applied at the portfolio level, things get a bit more complicated. Sure, you’ve got Agile teams sprinting away, but zoom out to the portfolio level, and you suddenly have layers of competing priorities, multiple stakeholders, and a heck of a lot more ambiguity around where to focus. This is where feedback loops, not just at the team level but fully integrated across the portfolio, can be game-changers. …
Scrum Master’s Role in Navigating Stakeholder Pressure: Facilitating Conversations and Upholding Scrum Values
Let’s talk about the role of Scrum Master when the pressure starts mounting. If you’ve been in this game long enough, you know that stakeholder pressure is almost a given. A feature needs to be out yesterday or a sales team promises a new capability without checking in on the team’s readiness. It’s easy to feel caught in the middle, especially when everyone’s eyes start turning toward the Scrum Master to “make it happen.” But here’s the thing: a Scrum Master’s job isn’t to give in to every demand or pressure the development team to cut corners. It’s to safeguard the team and maintain Scrum values, even when the heat is on….
Define the product vision statement
Define the product vision statementThe post will be about navigating Challenges with the various Product Owner activities
With regard to the challenges, the objective is to discuss potential challenges and considerations associated with the activity, including common pitfalls and obstacles. Offer practical advice on how to address these challenges, ensuring readers are prepared to tackle them effectively.
Facilitate Goal Setting for Sprints
Facilitate Goal Setting for SprintsThe post will focus on measuring success: Outcomes and Indicators for that activity. Objective: Describe indicators of successful activity completion, incorporating both qualitative and quantitative measures.
Scrum in the Real World: Handling Stakeholder Pressure and Urgent Releases
Scrum in the books and Scrum in the real world? They can feel miles apart sometimes. On paper, the framework is clear about how we work: every sprint delivers something valuable, with each backlog item hitting the Definition of Done before it’s released. We aim to maintain quality and avoid pushing out anything half-baked….
Market and Customer Insight Strategy
Market and Customer Insight StrategyThe post will focus on expert advice, outcomes and Indicators for that activity. Including expert insights, real-world applications & practical advice to guide Product Owners in integrating these activities into their strategies.
Who Decides Quality? The Role of Developers in Maintaining Standards in Scrum
In a Scrum environment, developers are often in the spotlight to deliver faster, ship sooner, and keep the wheels moving. But when you zoom in on quality, who really gets to decide if something is ready for release? It’s easy to assume that stakeholders—those investors or executives—hold the final say. After all, they’re the ones waiting on delivery. But let’s clear this up from the start: it’s the developers who carry the responsibility for maintaining quality. They’re the folks in the trenches, writing the code, testing the features, and ensuring that what leaves the team’s hands is something they can stand behind….
Evolving the Portfolio Kanban: Designing a System that Reflects Agile Growth
When it comes to running an Agile portfolio, a lot of emphasis is placed on the work itself—delivering value, managing priorities, and making sure your team is always moving forward. But one thing that often gets overlooked is the system we use to manage the work. The Portfolio Kanban system can easily fall into a “set it and forget it” trap, where teams create a basic board, configure WIP (Work-In-Progress) limits, and then assume the system is good to go. In reality, just like everything in Agile, the Kanban board itself needs to evolve….
Conduct Continuous User Research
Conduct Continuous User ResearchThe post will focus advice for beginners, with targeted advice for newcomers, drawing on the wisdom of experienced product owners.