The Latest

Giving yourself, and your team, the necessary time to adapt to and move on from change is the healthiest way to make sure that everyone is back on the same page in a timely manner. Learn how to avoid prolonging the necessary time to "heal" by minimizing turbulence.

When you release a website or web application, it’s going to face a lot of very public load testing. If it performs poorly, there’s a good chance that you’re going to lose a lot of customers. Colin Mason offers some tips for load testing in order to ensure a better customer experience.

Most management and change management methodologies assume a traditional environment—one in which the time between changes is much greater than the time required to adapt to each change. In fluid environments, the next change event happens before we can finish adapting to the last one, and sometimes even the one before that.

Mike Kelly explains the following heuristic approach to help ensure your testing is roughly inline based on orders of magnitude across the various types of automation. It’s not a method for measuring effectiveness. Instead it’s simply a “smell” to tell you when you might need to take a little extra time to make sure you’re focusing your automated testing efforts at the right level.

If you've had difficulty applying agile methods to the database side of development, you're not alone. Most developers see the database as an obstacle to-not a part of-agile development.

An enterprise agile initiative requires a higher level strategic, portfolio, product, and team perspective. Lean software development integrates all of these perspectives into a cohesive, actionable whole.

Is your agile team not reaching their potential? They may be suffering from internal dysfunctions that contribute to less than optimal results.