20 years ago Agile has transformed the world of software development, but today's Agile practices and tools fail to catch up and they work against software developers. In this video I talk about how and why it happens.
Scrum and Jira are just 2 examples of tools that focus on the process instead of outcome, they're optimized for project managers and scrum masters, not for software developers. In comparison with the progress that we made on the technology side with web applications, continuous deployment or SRE practices, management in software development can't catch up and focuses on the wrong things.
📝 My other related content:
* why estimatig using time sucks - [ Ссылка ]
* how t-shirt shizes make estimation suck less - [ Ссылка ]
* moving to async stand-up - [ Ссылка ]
🎥 timeline:
0:00 Intro
0:24 From waterfall to Agile
1:47 Why Scrum is anti-productive
4:44 Why Jira is not Agile
5:50 Why Agile has failed developers
8:04 How software developers can work around Agile
10:26 Summary
📝 Credits
Videos used in this episode come from pexels.com and were provided by fauxels, Kindel Media, Artem Podrez, Mikhail Nilov and Ketut Subiyanto
Images come from atlassian.com (Jira logo), scrum.org (scrum.org logo), scaledagile.com (beautiful and totally Agile SAFe chart), scrumalliance.com (certificates)
If you enjoy this kind of content, check out my website, 🌏 [ Ссылка ], where I publish more in-depth articles about software development.
As always, if you have any questions, suggestions or feedback, you can contact me:
✉️ email: gregory@notonlycode.org
🐦 Twitter: @GregoryWitek
