| Channel | Publish Date | Thumbnail & View Count | Download Video |
|---|---|---|---|
 | Publish Date not found |  0 Views |
In this episode, I share 7 reasons why programmers hate Scrum and how it makes our work almost impossible on software projects where the Scrum Master, Product Owner (or Product Manager), and the rest of the editor software uses it to abuse programmers. This mainly comes down to not understanding the Scrum guide and human nature!
In this first section of the video, I explain how Scrum project management typically focuses on speed and visible features to the point that it puts product quality at risk. They treat points in history like time. They resist investments in areas such as architectural improvement, testing, deployment, and other elements necessary to prevent developers from abandoning if left unchecked. And they fail to accept reality when bad user stories, missing acceptance criteria, and abuse of the burn down chart (and velocity metrics) turn Scrum into a numbers game instead of delivering a product quality software.
In the second section of the video, I share 7 practical tips on changes you can make within your software team to start loving Scrum again! If the programmers on your team hate Scrum, it's essential to draw clear lines between what software developers and project managers, product managers, product owners, or Scrum Masters can and cannot take responsibility for. of decisions. But as programmers, we also need to be more diligent in how we follow Scrum processes. We must closely inspect the work and move forward only with 100% acceptance criteria. We cannot commit to vague user stories. And we need to stop making estimates just for programming and include time for everything we know we need – quality assurance, automated testing, automated deployment, infrastructure as code, software architecture – basically all the benefits that maintain a project on track as it develops. complexity. This is how modern teams do continuous delivery and development.
I hope this video gives you good things to think about. Scrum is a complicated subject, but following everything exactly according to the Scrum Guide is a slippery slope. To love Scrum again, programmers must 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 it’s different for each team!
#scrum #programming #coding
RELATED CONTENT
Daily Scrum meeting: a status meeting in disguise?
https://www.youtube.com/watch?v=gEza0lkDcaM
How Senior Programmers Actually Write Code
https://www.youtube.com/watch?v=oJbfMBROEO0
Spot a fake agile team in less than 7 minutes!
https://www.youtube.com/watch?v=H6GdK-dChtY
Can user stories delay software projects?
https://www.youtube.com/watch?v=NavlPobhj7A
Continuous Delivery: Are you missing the big picture?
https://www.youtube.com/watch?v=TioLSzFw7Yo
Need help with your career? Book a free career consultation:
https://jaymeedwards.com/services/software-development-coaching/#free-consultation
CHAPTER MARKERS
00:00 Presentation
0:36 7 reasons why programmers hate Scrum
0:58 PO n°1 in daily stand-up
1:36 #2 Outpacing the Scrum Master
2:15 #3 Obsession with features
3:38 #4 Story Points Treated as Time
4:42 #5 Refusal to cancel the sprint
5:58 #6 No acceptance criteria
7:19 #7 Combustion chart used for blaming
7:54 7 Ways to Love Scrum Again
8:16 #1 Remove PO from daily stand-up
9:00 #2 Put Scrum Master in their place
9:49 #3 Buffer estimates for code quality
11:03 #4 Don’t engage in multiple sprints
12:04 #5 Keep the burn-down chart with the developers
1:00 p.m. #6 100% acceptance criteria
13:52 #7 Deliver features that delight
15:16 Groove of the episode
Miniature fire flame icon courtesy of https://www.freeiconspng.com/img/696
Download a free software development career guide from my homepage:
https://jaymeedwards.com
Please take the opportunity to connect and share this video with your friends and family if you find it useful.
