article thumbnail

7 Business Drivers for More Software Engineering Excellence

Accenture

We’ve known for a long time, before Agile was even named, that there are good practices the development team should do. They should test their code, they should review their code, they should integrate with other teams building programs, they should work with the business and make sure that we’re building the right thing.

article thumbnail

AoAD2 Practice: Build for Operation

James Shore

Test-Driven Development. Continuous Deployment. Complicated configuration ends up being a form of code—code that’s written in a particularly lousy programming language, without abstractions or tests. It’s okay to use DEBUG logs during development, but don’t check them in. Whole Team. Feature Toggles.

Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

Lean Software Development: The Backstory

LeanEssays

To counter sequential processes and the long integration and defect removal phase, agile software development practices focused on fast feedback cycles in these areas: Test-driven development: Start by writing tests (think of them as executable specifications) and then write the code to pass the tests.

article thumbnail

20 Deadline Management Tips Scrum Masters Should Consider

Codegiant

As a medium-sized company, we don’t follow the Test Driven Development (TDD) approach. We believe that it adds to 20–25% more development time. Also, some of its disadvantages include: With TDD, your team will find itself spending too much time even in straightforward implementations.

SCRUM 52
article thumbnail

20 Deadline Management Tips Scrum Masters Should Consider

Codegiant

As a medium-sized company, we don’t follow the Test Driven Development (TDD) approach. We believe that it adds to 20–25% more development time. Also, some of its disadvantages include: With TDD, your team will find itself spending too much time even in straightforward implementations.

SCRUM 52