The Latest

Andreas Grabner maintains that most performance and scalability problems don’t need a large or long running performance test or the expertise of a performance engineering guru. Don’t let anybody tell you that performance is too hard to practice because it actually is not. You can take the...

The term minimum viable product, or MVP, has come to be misunderstood and misused in many organizations. It doesn’t mean you should be releasing half-baked, barely feasible software. Instead, you should be thinking of your product’s capabilities as a Specifically Marketable, Useful, Releasable Feature Set—or SMURFS!

Jurgen Appelo’s useful and fun-to-read book Managing for Happiness: Games, Tools, and Practices to Motivate Any Team gives you concrete tools to identify ways to help your team be happier and to create environments where people can thrive and be more productive. Despite the word managing being in the title, the book is a beneficial read for anyone.

Change is a difficult but important part of business. It can be most difficult on the employees, but if you involve them in the planning process and make an effort to understand their points of view, you can mitigate resistance and facilitate the experience for everyone. This article deals specifically with ERP implementation, but its advice is useful for any change management situation.

If you're familiar with pair programming, you know how much it can increase code quality and encourage developers to learn from each other. You should try mob programming—the same concept, but with an entire team of up to eight people and only one keyboard. It's a great way to explore new techniques and solve problems as a team.

Many organizations enforce systems that stifle flexibility by promoting specialization. But encouraging learning new skills and expanding outside core responsibilities promotes flow over resource efficiency, helps cover gaps in time of crisis, and lets you build a team that can deliver continually at a sustainable pace. It's the age of the generalist.

Just because you follow the rules of your software development process doesn't necessarily guarantee project success. According to David Hussman, there are four product-centered principles that everyone should practice.