Remove Games Remove Systems Review Remove TDD Remove Weak Development Team
article thumbnail

Agile, Stand-ups, TDD and Code Reviews

The Programmer's Paradox

These two things tend to make agile an excellent fit for startups and an impossibly bad fit for large projects in large organizations. A big problem in development, particularly when a lot of people are introverts, is communication. Mostly that is a bad idea. It just doesn’t scale up or formalize properly. Is everything ok?

article thumbnail

Value vs valueable - another aha-moment

Marcusoft

According to Dave Farley it’s a common mistake he sees for teams to adopt user stories effectively. The reasons we want to make the stories small are plentiful; it’s easier to manage, implement, fix, deploy, and test… just about anything we do as a software development team. We, the developers, got some value from it.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Don't Measure Unit Test Code Coverage

James Shore

If you're using test-driven development, don't measure unit test code coverage. If you're trying to improve your team's coding and testing practices, perform root-cause analysis 1 of escaped defects, then improve your design and process to prevent that sort of defect from happening again. Here's the thing about TDD.

article thumbnail

AoAD2 Practice: Fast, Reliable Tests

James Shore

This is an excerpt from The Art of Agile Development, Second Edition. The full text of this section is available below, courtesy of the Art of Agile Development book club ! Test-Driven Development. Teams who embrace test-driven development accumulate thousands of tests. Fast, reliable tests are a game changer.

article thumbnail

Don't Measure Unit Test Code Coverage

James Shore

If you're using test-driven development, don't measure unit test code coverage. If you're trying to improve your team's coding and testing practices, perform root-cause analysis 1 of escaped defects, then improve your design and process to prevent that sort of defect from happening again. Here's the thing about TDD.

article thumbnail

No Fighting In This (Agile) Dojo with M. David Green

Marcus Blankenship - Podcasts

How can we train teams to consistently produce quality code without negatively impacting productivity? David Green, discuss Agile Dojos and how they can make teams more effective. Dojos provide a six-week training ground where teams focus on recognizing and replicating value by pairing, mobbing, and swarming. Episode 46.

Agile 59
article thumbnail

Uncle Bob Martin challenges software industry to Grow-up

Storm Consulting

Although it didn’t always work-out that way in the case of C++, these improved languages resulted only in fractional increases in developer productivity. Martin is challenging developers to accept the diminishing magnitude of improvement of tools and to concentrate on making a good job of writing software instead.