Some say test-driven development may work well initially, but as soon as we start to refactor our code, it breaks old tests and requires us to write new ones. This is not the fault of TDD; it’s the way we’re using it. TDD remains a valuable way to verify code as we write it, so we need to repair our test-driven damage.

When planning a software project, you need a thorough project communication plan. Both managers and developers need to take part in formulating the plan so that the correct terms of reference are present, achievable goals are set, and deadlines are attainable. Clear communication is essential. Here's what to include.

If you have an important implementation date, early identification of the minimum viable product is a vital risk-management step that helps focus your team’s attention on what's important. Rather than apologizing for intelligent phasing of functionality to manage risk, explain it to stakeholders and take credit.