Related Content
 |
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? |
|
 |
Use Continuous Backlog Grooming to Refine Agile Requirements Continuous backlog grooming means systematically refining your user stories: breaking up larger stories, obtaining detailed requirements, writing the requirements in terms of acceptance criteria and acceptance tests, and sharing and refining these details with the team. Acceptance test-driven development can help. |
|
 |
Do Software Teams Need Managers with Technical Expertise? Soft skills matter in how effective a manager is, but what about technical skills? If you're a software engineer, how important is it to you for your manager to have the same background and to fully understand your job? Ideally they would, but in some cases, that role can be better filled by a technical lead. |
|
 |
Build the Right Things and Build Them Fast: Accelerate the Continuous Delivery Pipeline When most people think about continuous delivery, they think of improving the build-test-deploy-operate cycle. They don’t think about how to improve the intake process. Ensuring that quality is built into the application—not tested for after the fact—is the key to achieving accelerated continuous delivery. |
|
 |
What’s in the Fall 2016 Issue of Better Software Magazine? In the cover feature article of the fall 2016 issue of Better Software magazine, “The Evolution of Software Monetization,” Michael Zunke details how software vendors misfire in an attempt to balance protection of their intellectual property with complicated software licensing schemes that frustrate customers. |
|
 |
Building a Business Case for Automation in Your Software Lifecycle To remain competitive, organizations should consider implementing a well-integrated set of automation capabilities—not just for testing, but across the entire lifecycle. Making the investment might take some convincing, so here are some questions to ask in order to assess the potential benefits of automation. |
|
 |
Think Agile to Work Efficiently and Effectively Of course it's important to work efficiently, without wasting time, money, or energy. But working effectively is just as important. Agile cycles between creating, testing, and getting feedback, allowing us to work in small chunks and make sure what we're producing has the most value. That's effective. |
|
 |
Why Is Estimating Software Testing Time So Difficult? Management loves to ask testers to estimate how long their efforts will take. But so many important factors elude measurement that it makes it difficult to predict. If you need to explain why estimation is so tough, here are nine factors that significantly influence our ability to estimate testing time. |
