Development Agile Test & Quality Assurance Project Management Requirements
CM & ALM Devops Cloud Mobile People & Teams

By Topic

Agile Development Methods

Agile Development Stories
Equal scales 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.

Michael Sowers's picture
Michael Sowers
The cover of Better Software magazine 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.

Ken Whitaker's picture
Ken Whitaker
sprinters at starting block 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.

Josiah Renaudin's picture
Josiah Renaudin
team improving together 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.

Sanjay Zalavadia's picture
Sanjay Zalavadia
Change 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.

Steve Berczuk's picture
Steve Berczuk
Master test plan 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.

Michael Sowers's picture
Michael Sowers
Feedback loop Shorten Your Feedback Loops to Build Better Software, Faster

When we have short feedback loops, we are still in the moment for that feature. We still have the context. The longer the feedback loop, the less likely we are to still have all the context for the feature because we are on to the next piece of work. How long are your feedback loops? Can you shorten them?

Johanna Rothman's picture
Johanna Rothman
Breaking down the walls of IT silos Can’t We Tear Down More Than One Wall at a Time?

Specializations tend to put people in silos, which inhibits communication and collaboration. The agile movement seeks to break down the dividing walls between customers and developers, and now DevOps is dismantling the wall between development and operations. But can't we break down multiple walls at once?

Lee Copeland's picture
Lee Copeland