5 Things You Can Do To Fix Your Sprint Planning

If you are on one of those teams that has made a habit of dragging unfinished work from one Sprint to the next... YOU NEED TO STOP! 

When you get to the end of a Sprint and have work that isn't done, you can't show it to the stakeholders in the Sprint Review. If you don't show it to Stakeholders in the Sprint Review, you can't get feedback. And if you can't get feedback, you can't inspect and adapt, and you negate the entire point of working in a Sprint. 

This video offers five things that you and your team can do right now to stop carrying over unfinished work and start enabling Scrum to provide you with the results you and your organization were hoping for when you headed down the path to agility. 

If you liked this video, please subscribe and let me know so I keep adding more. 

If you are interested in attending one of my upcoming CSM or CSPO classes, just follow this link: https://tinyurl.com/yc5k84z5

If you'd like to subscribe to the drunkenpmradio podcasts: https://soundcloud.com/drunkenpmradio

And if you'd like to contact me, you can find all my links

right here: https://linktr.ee/mrsungo

Tracking Flow Metrics w Atlassian Analytics

I've done a few podcasts recently on tracking flow metrics instead of velocity and why it is a better (but not perfect) way of estimating what will be done in the future.)

In this episode, Derek Huether and Sam Tsubota from Atlassian demonstrate how to pull that info straight from Atlassian Analytics.

The interview will work best in video

But there is an audio version too

Can Teams Actually Achieve Predictability? w/ Troy Magennis

Before the pandemic hit, one of my favorite parts of the summer was going to the Agile Conference and doing podcast interviews with the speakers and thought leaders who were there. Each year, one of the very best moments of each Agile Conference was when I would get to sit down and talk with Troy Magennis. 

It’s been two summers. 

I miss talking to Troy.

So I reached out and he was kind enough to spare some time for an interview. 

During the conversation, we cover a number of topics, including:

• Is it actually possible for a team to become predictable? 
• What gets in the way of predictability? 
• What is BlockedApp and why did he create it?
• Which constraints are the most important ones to start with? 
• Who is responsible for acting as the scientist of flow? 
• Why are we still so focused on utilization and output instead of results?
• Why do we all need to know CPR?

Click here to check out the interview