A sprint review is an essential part of the agile process, where the team can demo new features and functionality. But the demo is only half the story. The sprint review is also an opportunity for productive conversation and feedback between the team and stakeholder, which will lead to a better product.
320 items found
Backlog refinement sessions offer many benefits, but there are also well-intentioned activities—or antipatterns— that can be detrimental to the team. Here are five backlog refinement antipatterns to avoid, from focusing on estimates to removing requirements too quickly.
Project leaders must cope with many uncertainties, from requirements to schedules. These uncertainties can’t be removed but they can me managed and often mitigated. Here are some strategies and actions to address risks, reduce ambiguities and retire unknowns.
We can’t schedule innovation, but we can schedule and fund discovery—an essential part of building products that matter. How do we make the case for discovery as the true path to innovation? Make it tangible and frame it in non-specialist language.
Many project practitioners focus on execution and think their responsibilities start with the kickoff meeting. But before then, a good intake process can ensure a project is truly ready to begin. And, yes, it should involve not just portfolio or program leaders, but also project managers and teams.
To build better applications, citizen developers need to learn how to analyze and design for enterprise risk requirements as a part of capability development.
In agile product development, we try to work on fewer things and stick with them until we finish. Rapid priority shifts are expensive and demoralizing. But that’s not always clear on the go-to-market side, so we need stories like the Hungry Man Parable to build better understanding.
Scope creep can plague projects where timelines are established at the start, or budgets and resources are fixed. However, it should not be a problem for projects operating with agile principles. Rather than resisting change, an agile team welcomes it, and figures out how to adapt to it. Here's how.
Question: Last week, I was told that there will now be a business analyst (BA) working with my project team. To be honest, we have all the roles filled. Why are we being assigned yet another person to deal with? Isn’t it enough that they also want us to work with a second team to produce the tangible portions of this project, while we do the software and other soft deliverables? Can I refuse to accept this person into the group?
Faced with a project that had no defined scope and no project manager, this practitioner took on the role. Since then, he has completed dozens of similar projects and worked out a reliable general process with five steps.