Articles for category: Delivery

November 22, 2022

Greg Thomas

One Backlog to Rule them All

If you have multiple backlogs, which one does your team know to pull through? How do they know which one is prioritized higher than the other? How do they know which items that cross backlogs might be different than the others? Keep your backlogs simple so that when your team starts to pull from them, they know they are pulling from the right place at the right time, working on the right thing. Essentially what a backlog is supposed to do.

November 21, 2022

Greg Thomas

Your Sprints can be Better

If you don’t think there is any room for your sprints to be better then you’ve fallen into the trap where you think everything is perfect, everything is wonderful, everything is amazing and you could never do any wrong ever, ever again. And as soon as you read that statement you probably thought – “Well they aren’t that great, the board needs some tweaking, I feel like we are sometimes missing items that fall into this exception category and our estimates aren’t always there when I need to report them up to the rest of the company, etc, etc, etc.”

November 15, 2022

Greg Thomas

Product Delivery isn’t all about Introduction

This is a typical Product Lifecycle How long you are in each stage and the decisions you make in each stage vary from one to the other – they affect your thinking at the Product Management, Development, Testing, and Release levels. What’s funny is we talk about these stages when we are putting the product out for initial delivery but when was the last time you sat down with your team to ensure you’re building features designed for growth, practices for maturity, and support for decline. Don’t focus just on the Introduction.  

November 14, 2022

Greg Thomas

The Now vs the Later

Customer bugs will come in, and they will pop up when you least expect it – and no matter the issue, there are always two paths to get it resolved. Now What needs to be done to get the customer back to being on board with your product, using it, loving it, and incorporating it into everything they do?  This is the work that needs to happen immediately to get them back to operations. Later What do you need to do so this doesn’t happen again? Does it mean turfing this feature completely?  Does it mean rebuilding it?  Could other