article thumbnail

Top 15 project management certifications

CIO

The exam covers topics including Scrum, Kanban, Lean, extreme programming (XP), and test-driven development (TDD). 11, 2001, terrorist attacks to address issues of cyberterrorism and the information security of nations at large. Certified Project Management (CPM). The EC-Council was formed after the Sept.

article thumbnail

Taking an Extreme Approach to Software

Coveros

While there were definitely some new concepts introduced in the article—like pair programming and test-driven development—the overall philosophy hit home in a big way. When the Agile Manifesto was first published in 2001, I smiled. Happy 20 th Anniversary Agile!

article thumbnail

Software Testing and Agile

Coveros

Take a moment to think about where you were in February of 2001—at the inception of the Agile Manifesto. I was with a privately held software engineering firm focused on helping organizations transform their software testing capabilities. February 2021 marks the 20th anniversary of the signing of the Agile Manifesto.

article thumbnail

A Practical Approach for Shifting Left

Tenable

Coined by Larry Smith in 2001, shifting left is an "approach used to speed software testing and facilitate development by moving the testing process to an earlier point in the development lifecycle. Shifting left is a reference to moving testing to the left on a timeline," according to TechTarget. .

article thumbnail

AoAD2 Practice: Incremental Design

James Shore

Test-Driven Development. Test-driven development encourages you to think about and improve your design at nearly every step. Test-Driven Development. If you’ve practiced test-driven development, you’ve practiced incremental design, at least at the level of a single module or class.

article thumbnail

AoAD2 Practice: Pair Programming

James Shore

Cockburn and Williams 2001] Every team is different, so take these results with a grain of salt. Test-Driven Development. Take small steps—test-driven development works well—and talk about your assumptions, short-term goals, general direction, and any relevant history of the feature or project.

article thumbnail

AoAD2 Practice: Incident Analysis

James Shore

Kerth 2001] (ch. In this case, a closer look at the event reveals that, although the team used test-driven development and pairing for production code, they didn’t apply that standard to their scripts. In addition, consider establishing the Vegas Rule: What’s said in the analysis session, stays in the analysis session.