Meta-Cast

In this episode, Bob and Josh wrap up their three part series on collaboration.  In doing so we tackle the final step an organizaiton takes in becoming truly agile.  Learn how to enable your entire company to agile through world class collaboration.  We cover tips and tricks that each of us has used in the past to help our companies in this area.  What tips can you share?

If you missed either of the discussions on first and second level of collaboration, they can be found below:

Level One

Level Two

In this episode, Bob and Josh discuss the challenges presented to a product owner and team when stories classified as "non-product" work land in the backlog.  These stories typically include architectural work, research spikes, and other technical challenges like these that end users may never see and/or notice.  

We present the common problems teams run into and offer a few suggestions for how your group can execute on these just like all of your "normal" stories.

How do you and your team handle these stories?  We'd love to hear. 

Bonus Content!!!

In this episode, Bob mentions a couple of articles he's written on this subject.  Here they are..

Technical Product Ownership

Technical User Stories - What, When, and How?

In this speedcast Bob and Josh help you recognize a good scrum master from a bad scrum master.  We also chat about our new audio setup and how we expect it to drastically improve our audio quality.

Let us know what you think about our audio quality and what you view as the key qualities required to be a good scrum master.

In this episode, Bob and Josh continue discussing the three levels of collaboration.  After tackling collaboration inside an agile team in our previous episode, we dig into how to scale collaboration across all of our agile teams.  We may get sidetracked by a debate about what a healthy sprint review looks like, but we end up circling back to the topic of cross-team collaboration.

Let us know how you collaborate across all of your teams.  We'd love to hear your tips and tricks.

In this episode, Bob and Josh kick off a series discussing the three levels of collaboration in an agile organization.  Level one focuses on maximizing collaboration inside of each agile team.  Learn the warning signs that indicate a need for you and your team to focus on improving your collaboration, along with ways to make that improvment happen.

As always, we want your feedback and any tips/tricks you may have that could help other teams increase their collaboration.

In this episode, Bob and Josh talk through common agile transition failures.  We provide solutions to many of these problems so that you and your team can succeed in your implementation of Agile.  We also discuss the concept of starting with Kanban instead of Scrum.  

As a continuation from Episode 67's goal of demystifying story points, Bob and Josh dig into estimations.  When should you do them?  How long should they take?  Who should do the estimations?  

Take a listen and let us know what you think.  How does your organizaiton handle estimations?

What are story points?  

Why would we use them?

How do we pick a unit?

Can I make my teams all use the same numbers?

How do we get started?

We answer all of these and more as we dig into the hotly debated world of story points.  Like user stories, story points are often talked about, but seldom clarified.  Our goal with this podcast is to give you the tools you need to make story points useful in your organization.

Please let us know how you use story points in the comment section.

In this episode, Bob and Josh respond to a listener request from @sjoerddruiven about the future of agile.  We dig into our hopes for agile's future and also some realistic concerns and fears for where it could end up.  What are your fears?  How can you help shape agile's future?

In this episode, Bob and Josh discuss various ways to plan, and execute, your sprints in a strategic manner.  Many teams suffer for a microscopic view of their current sprint and struggle to properly plan for and execute on the next sprint.  We share a few tips and tricks on how to prevent that from happening.  What tricks do you use?