Related Content
 |
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. |
||
 |
5 Questions to Ask in a Project Review Project managers often dread doing reviews, but they're necessary to make sure the project is on the right track. Progress can be affected by unclear definitions, risk, schedules, and cost, so it's important to evaluate whether the project manager, sponsors, and team members are all on the same page. |
|
 |
Know the “Why” behind Your Projects Every project has its own unique reason for existence. We often work on projects to deliver some kind of return for our organizations. When you start a project, do you know what that return is? When we know the reasons behind our work, we can be more successful—knowing why can create success. |
|
 |
Where Do You Start When It Comes to DevOps? DevOps can be a loaded term. Sometimes, you’re just referring to the agile relationship between development and operations. Other people, when discussing it at a conference or in meetings, point toward more frequent releases, to the rate of hundreds of times per day or even per hour. |
|
 |
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. |
|
 |
The Difference between Plans and Planning As former president Dwight Eisenhower said, "In preparing for battle I have always found that plans are useless, but planning is indispensable." The fact that plans may have to change does not mean planning is a waste of time. In projects, it's always valuable to consider budgeting, resources, and timelines. |
|
 |
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. |
