You know that limiting work in progress (WIP) is a good idea. Now, do you know how many decision do you and your teams have in progress? What’s the cost of having too many decision in progress? How does it affect bottlenecks, long lead, feedback cycles, and leads to increase in defects?
Do we always need a big (enough) planning meeting? Can we plan-on the go? How would it work? Can we make do with Product Owners who understand the Product and work with the teams all the time? Are teams that deliver small features and integrate continuously good enough to get away with continuous planning? Here’s an interesting take on continuous planning.
How do you keep your Product roadmap healthy? Does it sound more like a guarantee to your stakeholders or is it a high level plan to enable growth? Should you have epics and user stories on your roadmap or not? How does roadmap and product strategy come together? Have a look.
How do you improve your product iteratively? How do you even know you are making it better? What sort of analytics do you apply to measure and understand this? It’s tough especially for the product that you haven’t launched yet. How do you test the future before you get there? Here are some good tips.
You’ve spotted a few areas where you’d need your team members to brainstorm and improve. Or maybe, your team members have identified a few areas they need to improve on. You can use the bicycle game to identify what’s causing these issues to appear and solicit ideas from the team members to improve. Here’s how it works
Imagine a line. On the left side of the line is what you’d call as “the real work”. The work which adds value we provide to the world. What’s the % of your work that falls on this side of the line as compared to the “bureaucratic silliness” BS that we need to put up with. A quick and interesting read.
Is it enough that you’re able to track the progress of your tasks as a result of your Daily Scrum? What’d you miss if you make this your primary goal? Everyone stands in a circle and answers three questions dutifully – what can possibly go wrong? Here are some good tips and anti-tips to do a quick health check on your Daily Scrums.
Let’s say you go to a conference or a big meetup, real or virtual. How do you know you’ve gained value out of it? What’d you look for? What’s your user story and acceptance criteria? Here’s an interesting take on this. It is written in the context of attending a conference but it can be applied to other learning methods as well.
AGILE
Why You Must Reduce Decisions in Progress?
How Does Continuous Planning Work?
Do we always need a big (enough) planning meeting? Can we plan-on the go? How would it work? Can we make do with Product Owners who understand the Product and work with the teams all the time? Are teams that deliver small features and integrate continuously good enough to get away with continuous planning? Here’s an interesting take on continuous planning.
jrothman.com
PRODUCT OWNER
Avoid These Product Roadmap Mistakes
romanpichler.com
Product Analytics Tips for Product Owners
TEAM
Have You Tried The Bicycle Game?
Do You Know Your BS Line?
Tips and Anti-Tips for the Daily Scrum
SCALING
What’s new in LeSS More?
GENERAL
User Stories for Learning and Continuous Improvement
Share this: