Related Content
 |
Data Means Nothing if You Don’t Know How to Use, Analyze, and Interpret It Simply having data stowed away and ready to use when needed is great and all, but if you don’t have a smart strategy for how to not only analyze and interpret it, but also put it to proper use, then you may end up creating a connected ecosystem without a real purpose. |
|
 |
Testing in a Pair Programming Environment If a development team does pair programming, where does testing fit in? You don't have to wait until the programming is done—testers can be part of the whole process, from code design to reviewing changes to production. Pair programming plus a good automation strategy mean quality is built in throughout development. |
|
 |
Why Agile Is a Double-Edged Sword When It Comes to Quality When it comes to quality, agile very often leads to better applications and just stronger testing overall. However, the rapidity of agile can make it even more difficult to keep up with bugs since you’re iterating at speeds teams often just aren’t used to. |
|
 |
Software Teams Aren’t Taking Bug Reporting Seriously Enough Of the things that are being sacrificed for speed, proper bug reporting is high on the list. Because it’s so easy to quickly update applications on the fly and push out fixes within days or even hours rather than weeks or months, plenty of teams assume it’s OK to ship something with a high volume of bugs. |
|
 |
The Manager’s Role on a Self-Organizing Agile Team Scrum and other agile methods focus on team roles and dynamics, and because of the emphasis on self-organizing teams, there’s sometimes a misconception that there’s no need for a manager. In reality, good people management can help an agile team thrive—the manager just has to know how to empower the team. |
|
 |
What's in the Winter 2018 Issue of Better Software Magazine As Better Software magazine continues to publish articles that propel our industry forward with great tips and techniques, TechWell sees the future focused on continuous processes. Three of this issue's feature articles will help you improve how enterprise software is planned, developed, validated, and released. |
|
 |
Interface Grief: Is It Agile, or Just Bad Software Engineering? There are people who will use "being agile" to justify software engineering practices that could be perceived as lazy or even bad. The specifications are going to change, they say, so it would be a waste to engineer more to begin with than the minimum viable product. What's expediency and what's just poor practice? |
|
 |
Agile and Testing Change Can Come from Leaders at the Bottom, Not the Top Change doesn’t need to be a decree from the top that forces everything else to follow suit. Change can and should start from the bottom, and that happens after you empower your developers and testers and clearly show why things like agile are critical to overall success. |
