When Product Owners cause Scrum Events to go Bad
Have you ever seen a Product Owner cause Scrum events to go bad? I have, and it’s not pretty. Read on to learn what NOT to do if you’re a PO.
Have you ever seen a Product Owner cause Scrum events to go bad? I have, and it’s not pretty. Read on to learn what NOT to do if you’re a PO.
Negative feelings and emotions are often the root cause of fearing failure, but sometimes it’s all right (and even beneficial) to fail.
In my nearly 20 years as a Business Analyst, I have witnessed many different myths come and go about this role. 20 years – 20 Myths Debunked!
How do you tell if your Scrum Team is broken? Here are 10 symptoms there might be something wrong…
Each event of Scrum has a specific audience and purpose. While skipping some might be tempting, you might want to read this before doing so.
Not delivering a “done” increment at the end of a Sprint can cause many negative consequences. It’s a bad habit and won’t make anyone happy.
Here are five more bonus tips for retaining your very best employees; they’re a few more things you can do to keep your best employees around.
The problem of Agile requirements going wrong is endemic; this is the third of a four-part series on what can go wrong, and how to fix it.
In Agile, defects can be handled in different ways – so what should you do when you discover a bug? Find out how to handle defects in Agile.
I have been an IT consultant for many years, and I have worked with many, many Product Owners at various different companies in all sorts of industries. Through painful experience, I know what NOT to look for in a Product Owner. Let me help you avoid the pain that I have experienced by sharing 7 …