Great 2 Minute Video on the Product Owner Role in Scrum

SSW of Australia has just put out a great two minute video on the role of the Product Owner in Scrum.

Check it out here(might take a minute to load):  http://tv.ssw.com/3244/what-is-a-product-owner

I’ve added it as #4 under Scrum on the ScrumCrazy.com’s list of preferred Scrum resources.

Great blog post on why the Scaled Agile Framework is “Scaled Amateur Hour” and definitely NOT Agile –

Scrum trainer Dominik Maximini has written an excellent, objective, but critical article on the Scaled Agile Framework.  While my own criticisms would probably be both somewhat similar and different to Dominik’s, he’s done an excellent job of laying out the case against SAFe, and I agree with all of his conclusions.

I highly recommend you give it a read.

New and Improved User Story Lifeycle Diagram — Free Creative Commons PDF download!

I had a designer friend update my User Story Lifecycle diagram, and she did a fantastic job!  You can download the PDF here:  http://www.scrumcrazy.com/lifecycle

New and Improved Diagram:

UserStoryLifeCycle_final_lg

The Older Diagram(also still available at the above link):

UserStoryLifecyclexm

Other Good User Story Links

The Summer of Scrum: Ken Schwaber Announces New 2013 Scrum Guide

Ken Schwaber announced today that a new Scrum Guide is coming in the next couple of months.  In my position as a Professional Scrum Trainer certified through Ken’s Scrum.org, I was aware of this earlier this year and I have to say… the Scrum nerd in me is excited!  It’s so great to see that Scrum is evolving, because this is one reason many of the past methodologies and frameworks died out.  It’s also very much in line with the “inspect and adapt” nature of Scrum, so it’s wonderful to see Scrum’s founders and shepherds leading by example.

I also want to drop another hint.  There are some other interesting things happening in the Scrum world this summer that I cannot yet talk about.  Subscribe to my blog to stay tuned!

Scrum On!

Other posts you might be interested in:

It’s Difficult to Give User Story Advice over the Internet

I often get and see questions on internet forums related to helping someone slice their User Stories or Product Backlog Items. This can be very difficult to do, because the slicing conversation really requires so much context around the parties/teams involved, the nature of the business domain, and the technical structure of the system under development. Due to this complexity, this is why I always recommend that Product Owners and Development teams do slicing together in Product Backlog Grooming sessions.

Another problem with trying to provide the needed context to give good advice is that most people work at organizations that have some sort of information security policy that would be violated by providing enough context.

The best route that I’ve seen is trying to come up with a fictional story/PBI/context that demonstrates the key challenge that you’re having without improperly offering too much confidential information.

Another approach would be to have you and your team try Richard Lawrence’s User Story Splitting flow chart.

Anyway, I wish you well, and think about trying some of the suggestions above!

Other Good User Story Links

Daily Scrum Patterns: The Sprint Backlog at the Daily Scrum

This blog post is part of a series of blog posts on Daily Scrum patterns.  For some background, you might find it useful to read my previous article on a simple Scrum Patterns framework.  Daily Scrum Patterns fall under the category of “Scrum Technique Patterns”, as introduced in that article.

Today we’ll talk about “Obstacle Resolution Patterns”

Notes:

“The Sprint Backlog at the Daily Scrum” Patterns

While it’s a popular and proven practice to <View the Sprint Backlog at the Daily Scrum>, it’s a controversial practice to <Update the Sprint Backlog at the Daily Scrum>, as the updating can detract from the true objectives and focus of the Daily Scrum in some situations.

Also, don’t forget to be creative and <Create Your Own Pattern>, and don’t ever hesitate to use a technique that is not described by a documented pattern.

The Sprint Backlog at the Daily Scrum Patterns:

Daily Scrum Patterns: Who Attends the Daily Scrum?

This blog post is part of a series of blog posts on Daily Scrum patterns.  For some background, you might find it useful to read my previous article on a simple Scrum Patterns framework.  Daily Scrum Patterns fall under the category of “Scrum Technique Patterns”, as introduced in that article.

Today we’ll talk about “Obstacle Resolution Patterns”

Notes:

Who Attends? Patterns

According to the Scrum Guide, the Development Team must attend. With many teams, and especially Shu level teams, the <Scrum Master Attends>. It’s usually a good practice if the <Product Owner Attends> so that they can help the Development Team if needed, often times at <The After Party>. It’s usually not good if an <Authority Figure Attends> on a regular basis.

Also, don’t forget to be creative and <Create Your Own Pattern>, and don’t ever hesitate to use a technique that is not described by a documented pattern.

Who Attends? Patterns:

Follow

Get every new post delivered to your Inbox.

Join 277 other followers

%d bloggers like this: