why-doesnt-scrum-care-about-good-software-development

Trainer Talk Podcast: Why Doesn’t Scrum Care About Good Software Development?

why-doesnt-scrum-care-about-good-software-development
Share on facebook
Share on twitter
Share on linkedin
Share on email

Episode Description:

In this episode of Trainer Talk – the supplemental series to the Agile Coaches’ Corner podcast – Eric Landes, a Professional Scrum Trainer, answers the question, “Why doesn’t Scrum care about good software development?”

Listen on Google Play Music

 

Introduction

In my Professional Scrum Foundation classes, sometimes I’m asked, “Why doesn’t Scrum care about good software development?” Kind of a funny question, right? Scrum was founded for software development teams, yet we don’t really see that in the Scrum Guide. So, for instance, if I look at the Scrum Guide and search for terms like “tester” or “development” or “continuous integration,” we don’t really see that.

 

Scrum Does Care About Good Software

My answer to that question is typically this: Scrum actually does care about software development. In fact, the Professional Scrum Developer course – which was created by Ken Schwaber – was one of the first classes created by Scrum.org. Plus Schwaber is a software developer at heart; he’s very passionate about having good practices in the course. The course actually teaches Scrum along with good software engineering practices; things like test-driven development and continuous integration are the foundation of the course and, as with all courses, participants create multiple increments of software over the course of multiple Sprints.

As a Professional Scrum Developer Trainer and I love the course. One of the things I like about it is that it regularly incorporates fresh trends: For instance, trends like DevOps, infrastructure as code, telemetry and monitoring are all things that are incorporated now into that course. So Scrum.org is always modifying, inspecting and adapting – as any good Scrum team should do – in their courses.

 

Build the Right Team

The idea that Scrum doesn’t care about good engineering practices is not actually correct; the Scrum Framework encourages development teams to have all the skills necessary to create a complete increment. For instance, if your team doesn’t have the ability to do infrastructure as code, and you don’t have the right person to get all the way to production, then you need to get somebody on the team to do so. Also, self-organization means that, together, your team has to decide which practices to utilize. Scrum may not be prescriptive and specifically say you need to use certain technical practices, but it provides a good basis from the Professional Scrum Developer course on what practices are good and pair well with Scrum.

 

Self-Organize

Scrum assumes that you, as part of a self-organizing team, are going to come up with good engineering practices to create the finished increment that delivers what the customer wants. It also assumes that you’re going to continue to keep up on good trends and the software needs of your customer. In the end, Scrum does care about good software engineering practices, it’s just not prescriptive about it. And if you’re interested at all in the Professional Scrum Developer course, keep in mind it’s made for all different kinds of languages: Java, C#, JavaScript, React, all of which can be modified and used with the course.

 

Provide Feedback

Let us know what you thought about this supplemental episode of the Agile Coaches’ Corner. If you’re interested in training, visit agilethought.com/training or call us at 877.514.9180 to learn more. And if you have a question you want us to answer on the next Trainer Talk episode, email us at podcast@agilethought.com.

 

Want to Learn More?

Stay Up-To-Date