Related Content
 |
3 Key Contributors to Software Development’s Demand for Speed Why does software development demand so much speed? We throw around terms like “agile” or “DevOps” and consider that a good enough answer for the demand for speed, but there are three major factors outlined by Mark Levy, the director of strategy at Micro Focus, that call for greater development speed. |
|
 |
Software Development and Testing Agility Demands Fungibility Fungibility means the ability to change without needing an external catalyst. In our agile culture, fungibility is a critical characteristic. The triad of people, processes, and technology ideally should all be fungible. Just like perfection, this may never be attainable, but it’s an important goal. |
|
|
What's in the Winter 2017 Issue of Better Software Magazine? The first issue of our nineteenth volume of Better Software magazine has a new simplified, modern look. We've been planning this design overhaul for months, and the content keeps getting better. Check out the articles on reducing the risk of failed system updates, scaling agile, and servant leadership. |
||
 |
How Your Software Team Can Successfully Adopt a Shift-Left Approach "Shift left" is the latest philosophy teams are adopting to account for the fact that releases are happening on a daily basis, rather than a weekly or monthly basis. If you're working on mobile applications and don’t adhere to a shift-left mindset, your team will be left behind. |
|
 |
How Retrospective Meetings Can Improve Your Team's Software Quality Efforts Many software professionals think they won't get anything out of retrospective meetings and want to cut them out entirely. However, retrospective meetings are a necessary part of project progression, and they can significantly improve your team's software quality efforts. |
|
 |
Overcoming Resistance to Change in Agile Teams For agile software developers, acknowledging that change is inevitable is a core principle in how we work. Yet we often resist change—for a variety of reasons. By understanding human nature and being systematic about how we evaluate decisions, we can give ourselves a way of identifying changes that add value. |
|
 |
Why You Should Build Your Software How Boeing Builds Planes Instead of building each individual part of a piece of software, putting it all together, and testing it to see the results, maybe we should look to how planes are assembled. By testing each aspect of the product in isolation first, problems are discovered earlier and software can be delivered faster. |
|
 |
Reviving the Master Test Plan in the Age of Agile In the competitive environment of delivering software more quickly, many teams have abandoned detailed test plans. Michael Sowers argues for bringing back the overarching master test plan—not to have more documentation, but for the questions, creative test designs, and critical thinking the planning brings. |
