The Reason Extreme Programming Works Better Than Anything Else
HTML-код
- Опубликовано: 10 окт 2024
- Extreme programming has become one of, if not the best way we build software in modern times. In this clip Dave talks to Dragan Stepanovic about the competitive advantages of XP and how it brings software development teams together.
You can listen to the full podcast episode HERE ➡️ open.spotify.c...
-
🗣️ THE ENGINEERING ROOM PODCAST:
Apple - apple.co/43s2e0h
Spotify - spoti.fi/3VqZVIV
Amazon - amzn.to/43nkkRl
Audible - bit.ly/TERaudible
-
🙏The Engineering Room series is SPONSORED BY EQUAL EXPERTS
Equal Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ bit.ly/3ASy8n0
-
#softwareengineer #extremeprogramming #xp
No one explains what Extreme Porgramming actually is in this video!
I liked the discussion, but I don't get what you mean with "The Reason Extreme Programming Works Better Than Anything Else". Joy at work? I sure like that. Strong relationships? That, too. Like it a lot. The video is a bit unclear about it. From the title I expected something else.
"Old school" XPer here, first working with it in 2000, and I couldn't agree more! I'm actually seeing a resurgence of interest in the technical practices now that the bloom is finally off the rose that was Scrum.
I once consulted with a team, whose "founder/cto" was doing all the code reviews. And he was only allocating his Sunday mornings for the code reviews. So his team was each time waiting for a full week before they got the feedback telling them what should be fixed, and then waiting for another week to get a confirmation that it is okay to deploy. Once I verbalized this to the whole team, they instantly understood the problem themselves. So many people simply don't understand how to "look at things" correctly.
I had a similar problem, but not with CTO. It was my architect. I had to practically beg him to review my PRs. Without prodding, he'd do it at the end of the sprint.
The nicest combo is XP, Kanban, CI/CD and ORSC 😮
Regardless, there are just some that don't want to believe and prefer the tried-and-true Chaos programming method because they have experience with that one the most.
The reasons why they wanted to ignore XP or Scrum, or any Agile process, they'd tell me that: "That's the always the way the projects go regardless of planning", "Agile isn't designed for projects with deadlines", "It's always been done this way and for 20 years it has worked successfully, so why change it?" Oh, I'm sure we've all heard these and more!
Come on Comment section, don't disappoint me, let's hear some good old fashioned war stories from work! LOL
We have been using XP for five years now as I (as an architect) have actively fought Agile within my area of our org. Oddly enough, I didn't even term it as Extreme Programming when I first promoted it, but discovered the term for it by watching your channel. The slow speed of delivery of our development groups were due to large amounts of disparate legacy code/languages/projects and not their processes. However, the *velocity of value* difference for our Agile vs. XP teams is very obvious.
XP does follow the agile philosophy though...
@@Software.Engineer agile, Not Agile(tm).
Great guest, Dave!
Scrum just had a better marketing team.
@Rcls01 ah the Betamax v VHS war all over again!
Dragan is awesome
It would be awesome to have James Bach on the Engineering Room. He has worked in Apple in the late 80s and, if not the one, is one of the most influential testers in the industry throughout the decades.
Ha! Thx! The pull request is the worst moment to make a code review. And the dark role git has here, oh dear. Bad coders with the intelligence to dominate projects to get those stucked are having a big long party.
Getting to the point isn't part of the method apparently.
But the main product of software engineering is not a learning. Just like the main product of civil engineering is not learning how to build bridges but a bridge.