Skip to content
Hallway
0:00 / 0:00

#scrum#agile#kenschwaber

Scrum et al.

Google TechTalks

349K subscribers • 66 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • A classic. People kept recommending it from 2014 to 2024.
  • Presented by Ken Schwaber, co-developer of Scrum
  • An opinion. It argues one side of a question engineers disagree on.

Beginner. No background in the topic needed.

173K views19 years ago2 recommendations

Tools and practiceCode review and teamworkDeveloper productivity

Ken Schwaber presents the original framework of Scrum, its core principles, and the implementation challenges associated with agile adoption.

Google Tech Talks September 5, 2006 Ken Schwaber co-developed the Agile process, Scrum. He is a founder of the Agile Alliance and Scrum Alliance, and signatory to the Agile Manifesto. Ken has been a software developer for over thirty years. He is an active advocate and evangelist for Agile processes. ABSTRACT Scrum is an amazingly simple process that causes many, many changes when it is implemented. This seminar presents the basic framework of Scrum and some of the implementation issues associated with it. Credits: Speaker:Ken Schwaber

Why it's here

2 people recommend this

What people say. Recommended for understanding the original, self-managing intent of Scrum before it became commercialized.

u/One_Curious_Catsin r/ExperiencedDevs • Recommends

On “I have a theory that the dedicated Scrum Master only exists because of how new the software industry was in the 90s when it comes to communication.”

You’re describing a real scrum master and their role. Help the team self-manage, and then move on. For the original Scrum that now sadly has been lost watch this video: Scrum el al. - by Ken Schwaber link to this video
20View on Reddit

u/gmarceauin r/compsci • Recommends

On “As a business professional, what are the dos and don’ts of working with software developers?”

Like you I work at a tech startup. When we were just starting, our business/strategy people asked the question you just asked. They opened a dialog with development team, and found good answers. I attribute our success in large part to that dialog being eager and open-minded, just as you are being right now. So, it's good tidings that you are asking. For us, the answer came from conversation, but it also came from reading the following books together: * The Soul of a new Machine. Pulitzer Prize Winner, 1981. It will teach you the texture of our work and of our love for it, as well as good role models for how to interact with devs. * Coders at Work, reflection on the craft of programming W…
2View on Reddit