Monday, November 05, 2012

Webinar: Scrum Yesterday, Today, and Tomorrow


Next year will mark the 20th anniversary of Jeff Sutherland’s invention of Scrum. What does it mean to reach such a landmark?

There is a gulf between those who were there at the beginning and those who have joined the journey more recently. It behooves us all to attempt to cross the gulf. Old-timers need to transmit the heritage; to ensure that those who will carry us into the future have heard the stories, understand our ideals, and have the knowledge they need. The new guard needs to listen, to honor the past, and to know that they are entrusted with making changes. Scum, after all, has “embracing change” encoded in its DNA.

Jeff Sutherland and Scrum Inc. Chief Product Owner Alex Brown will talk about the ideas that sparked the creation of Scrum,  and speak of the fundamental ideals embedded in Scrum. They will also assess the current state of Scrum in the world. We see this coming 20th anniversary year as a game changing moment. And they will look ahead to where Scrum is headed and share some of Jeff's dreams about the future.

Update: this webinar has been postponed until January due to some illnesses in the office.  We apologize for any inconvenience.

3 comments:

Pavel Surmenok said...

Hi Jeff!

Unfortunately, I have not managed to find how to contact with you, so I try to use this comment as a communication instrument.


Jeff, could you please answer these questions:

1. Does SCRUM suppose that development team should be cross-functional?

2. What does "cross-functional" mean? Does it mean that every single member of the team can perform all kinds of tasks (coding, requirements analysis, testing, documenting and so on)?


Thanks in advance!


Best regards,
Pavel Surmenok

Jeff Sutherland said...

The Scrum Guide is reasonably clear about this. The cross functional team needs all the skills that are essential to creating a product increment at the end of a Sprint. It doesn't say everyone has to do everything. However, a really good pattern to implement is to have nothing in the sprint backlog that cannot be completed by at least two people. Failure to implement this will reduce velocity, sometimes drastically.

Pavel Surmenok said...

Thank you!