Related Content
Legacy Code Can Hinder Your Agile Transition Although there's a lot of practice evolution that happens with agile transitions, legacy code can still be a major obstacle to agile success. A few risks and considerations emerge when scaling agile while still managing legacy code barriers. |
||
The Challenges of Incorporating Robust Test Data Management We can no longer be myopic when it comes to testing, as there’s a wide group of needs to be addressed on any given project. For a project to succeed, testers must build out robust test data management capabilities in response to growing application demand. |
||
The Cost of Holding a Grudge against a Coworker Grudges zap your energy and divert your attention to things that are irrelevant, counterproductive, and, worst of all, negative. But the cost of holding onto a grudge isn’t just mental or emotional. Hang onto a grudge for too long and it can trigger a stress response that can also be damaging professionally. |
||
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. |
||
Hiring for Your Best Software Team Possible Software teams spend a lot of time thinking about processes and requirements for development so that we can build great software systems. However, we seem to think much less about how to hire the people for the teams that will build those systems. Consider these points to assemble your best possible team. |
||
Striking a Balance with After-Hours Email The best way for employees to recharge themselves after a workday is to detach both mentally and physically from work. Unfortunately, after-hours email has made that detachment impossible for many. Still, you don't have to give up work-life balance. Try imposing some limitations on after-hours communication. |
||
Why Process Standardization Is a Terrible Idea Having a standard process everyone uses makes sense in theory. You could compare metrics and progress across teams and projects. But it practice, it becomes like comparing apples and oranges. Teams aren't all the same, and neither are projects. Each team need its own optimized way to deliver value. |
||
Developing Mobile Apps: Focus on Features, Not Ratings Does your team desperately want to have a five-star app? If so, you are chasing the wrong goal. Relative measures of quality are better because they can be adapted to your own situation. Instead of asking “How can we get five stars?” you should be asking “How can we get more stars than the competition?" |