Every programmer seems to want to vomit the second they hear the word scrum. What is it about scrum that's made programmers hate coding so much, and how can you prevent this on your software development team
In this episode, I share 7 reasons why programmers hate scrum, and how it makes our jobs nearly impossible on software projects where the scrum master, product owner (or product manager), and the rest of the software company use it to abuse programmers. These mostly get down to not understanding the scrum guide, and human nature!
In this first section of the video, I explain how management on scrum projects usually focus on speed and visible features to the point that it puts the quality of the product at risk. They treat story points like time. They resist investment in things like improved architecture, testing, deployment, and the other things needed to keep developers from quitting unless kept in check. And they fail to accept reality when bad user stories, missing acceptance criteria, and abuse of the burn down chart (and velocity metrics) turns scrum into a numbers game instead of about delivering a quality software product.
In the second section of the video, I share 7 practical tips for changes you can make on your software team to start loving scrum again! If programmers on your team hate scrum, drawing clear lines between what software developers and project managers, product managers, product owners, or scrum masters can and can't make decisions about is essential. But as programmers, we also need to be more diligent with how we follow scrum processes. We need to closely inspect the work and only move forward with 100% acceptance criteria. We can't make commitments to vague user stories. And we have to stop estimating just for programming and include time for all the things we know we need - QA, automated testing, automated deployment, infrastructure as code, software architecture - basically all the goodies that keep a project on track as it grows in complexity. This is how modern teams do continuous delivery and devops.
I hope this episode gives you some good things to think about. Scrum is a complicated topic, but following everything exactly by the scrum guide is a slippery slope. To love scrum again, programmers need to work with management and the rest of the company to adapt processes to meet the way everyone needs to work together to deliver software. And that's different for every team!
You can also watch this video on YouTube.
Chapter markers / timelinks
Visit me at JaymeEdwards.com
Find me on Facebook at JaymeEdwardsMedia
Find me on Twitter as @jaymeedwards
My Recovery From Programmer Anger
Scott Nimrod on Personal Reputation vs Teamwork
Woody Zuill on Mob Programming and Influencing Change
How Agile Teams Grow Toxic! Ep. 4 Commitments
Response to Comments on "Sprint Planning is Bullshit!"
3 Embarrassing Software Developer Stories From My Career
How Agile Teams Grow Toxic! Ep. 3 Forecasting
How Agile Teams Grow Toxic! Ep. 2 Hiring Talent
How Agile Teams Grow Toxic! Ep. 1 Founder Values
I Quit My Software Project To Get Healthy!
Scrum Got 3 People Fired From A Software Project!
How To Get Support To Fix A "Disruptive" Problem
They Watched Us With Webcams And Rewrote Our Code!
Lead Software Developers Better By Letting Go!
It’s Hard To Keep A New Team Doing Continuous Delivery
How To Stop Comparing Your Career To Other Developers
John Cutler on Agile Skepticism and Making an Impact
Can User Stories Make Your Software Project Late?
We Were Hired For A Hidden Agenda
Is Your Team Really Measuring Software Projects Correctly?
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
The Unbelivable Truth - Series 1 - 26 including specials and pilot
Lex Fridman Podcast