Related Content
 |
Defining Velocity for Your Agile Team When an agile team talks about velocity, it's usually how much functionality they'll deliver in a sprint, often based on historical data about the number of story points the team tends to finish. But you shouldn't use velocity as a measure of success for your agile process. Make sure everyone knows what's important. |
|
 |
Engaging Developers in Unit Testing Unit testing is key for driving early defect identification, but organizations and teams continue to be challenged when it comes to designing and implementing unit tests. Realizing a culture of sound unit testing is often more a leadership challenge than a developer one. Here's how to instill a culture of unit testing. |
|
 |
The Test Automation Mindset Building a test automation strategy involves all members of the technical team, layering tests throughout the technology stack, and using this approach to design better software and catch simple problems earlier in the development cycle. But working like that requires a shift in mindset across the organization. |
|
 |
What's in the Summer 2018 Issue of Better Software Magazine For twenty years now, Better Software magazine has published articles offering helpful tips and techniques for those in the software industry. The new issue celebrates those two decades of knowledge-sharing—and, of course, gives you more ideas. Articles this issue focus on leadership and software quality. |
|
 |
3 Mistakes Teams Make When Choosing a ScrumMaster One cause of agile project failure is choosing the wrong person as your ScrumMaster. While a bad ScrumMaster is a problem for any team, it is particularly bad for teams new to agile, as the team won’t know they are being led down the wrong path. Here are three mistakes organizations make when choosing a ScrumMaster. |
|
 |
Lessons Learned at the Agile Dev, Better Software & DevOps West Conference The Agile Dev, Better Software & DevOps West conference was held in Las Vegas in early June. Coveros technical manager Gene Gotimer was a speaker at the event, but he also attended as a delegate, getting to experience the keynotes, sessions, Expo, and other parts of the software conference. Here are his takeaways. |
|
 |
The Risk of Overemphasizing Risks We are trained to identify and evaluate risks. This prevents teams from making decisions that are unlikely to work, saving time and money and helping the team move forward. However, a risk-avoidance mindset can also stop progress. Successful agile teams see risks as ways of starting a conversation, not stopping it. |
|
 |
Mob Programming: Working Well Together Mob programming is a whole-team approach to creating software where everyone works together on the same thing at the same computer. It's not a bunch of people watching one person write code, but rather everyone thinking, discussing, designing, and collaborating. Sound crazy? Here's how it improves the quality of code. |
