How to Help Executives Understand Agile
For agile transformations to succeed, they must have top-down support from executives who really understand what it means to be agile.
For agile transformations to succeed, they must have top-down support from executives who really understand what it means to be agile.
I can’t tell you how many times I have seen Scrum go wrong. If you want the perfect recipe for screwing up Scrum, you’re in the right place.
You can build a high-performing team by setting them up for success, coaching and guiding them along the way – then get out of their way.
There are only three official roles in Scrum, but there’s widespread confusion about the roles and what each one is responsible for.
In blog two of three, I cover five more ways a Product Owner on a Scrum Team should not behave. Watch out for these behaviors or traits.
The problem of Agile requirements going wrong is endemic; this is the first of a four-part series on what can go wrong, and how to fix it.
Having a vision aligned to the strategy of our product is like having a north star to guide you. Without one, you will probably fail.
Does your organization have multiple Agile teams? If so, do you think they should all operate in the same way?
As an agile practitioner and consultant, I have seen 10 attributes and behaviors that lead to poor Product Owners. Check them out.
It’s a known fact that poor requirements can cause projects to fail. When using Agile, these problems can be even worse. Learn what to avoid.