Requirements
Better Software Magazine Articles
Painful Lessons I Learned from Bootstrapping a Startup If you are considering leaving the nest to self-fund your own endeavor, you may want to read about Mike Botsko's experience creating a cloud-based, bug-tracking app called Snowy Evening. What started out as a lot of fun quickly turned into a tough journey. Don't worry—it has a happy ending! |
||
How Can You Get More Effective with DevOps? By emphasizing better communication and collaboration between software development and IT, this article explores ways to establish trust by focusing on customer value. For example, Manoj Khanna suggests continuous integration and validation as techniques that helps build that trust. |
||
Moving Beyond the Backlog: The Four Quadrants of Product Ownership What do you consider the role of product owner in an agile development project to be? Bob presents a compelling perspective that a product owner has four distinct critical roles that can prove impactful to a team's success. |
||
Requirements Reuse: Fantasy or Feasible? Software development teams think nothing about reusing code, but what about requirements? The benefits include faster delivery, lower development costs, consistency across and within applications, fewer defects, and reduced rework. |
||
Strengthen Your Discovery Muscle An organization shouldn’t spend all its time building its delivery muscle without simultaneously building its discovery muscle. In fact, successful software teams deliver great products because they invest in discovery. Learn how to expand your innovation and strengthen your discovery muscle. |
||
Lessons Learned from Ancient Wisdom: A Software Review Story Lessons learned long ago from reviews and inspection can be effective today, particularly in collaboration within agile teams. Learn how an organization used review techniques as part of its agile collaboration, including the advantages and potential problems of this ancient wisdom. |
||
Simplicity and Precision: Test Planning in Agile Projects Test planning is often thought unnecessary in an agile project. However, if our mindset is on "planning" rather than "plans," we see that test-planning activities happen throughout the project, taking advantage of levels of precision, i.e., what is absolutely necessary at each level. |
||
Why Do Requirements Matter? A series of dining mishaps leads Lee to reflect on why mistakes happen in spite of well-defined requirements. |
||
Seven Ways to Make Testing Irrelevant on Your Team Testers and developers can be friends. In fact, on teams working at a breakneck pace to deliver software, they must be friendly enough to rely on each other. However, there are a few sure-fire ways to ruin that relationship before it begins—and potentially make testing both irrelevant and unwelcome. Marlena Compton lists seven such ways here, along with suggestions for avoiding disaster. |
||
Goodhart’s Law Charles Goodhart stated: "Any observed statistical regularity will tend to collapse once pressure is placed upon it for control purposes." In other words, "When a measure becomes a target, it ceases to be a good measure." |