Related Content
What's in the Spring 2015 Issue of Better Software Magazine? There’s been a meteoric adoption of DevOps, requiring attention to higher quality processes throughout the SDLC and deployment. Our authors in this issue of Better Software magazine see development teams attempting to deliver on this new program of continuous integration and rapid deployment. |
||
How to Succeed at Project Failure If you're bound and determined for your software project to fail, you're in luck: Naomi Karten has some advice for you. She'll tell you to set unclear objectives and unrealistic expectations, leave gaps in communication, and ensure a lack of resources and support. You'll be failing in no time! |
||
Who Is Responsible for Happiness? No one can take full responsibility for another person's happiness. However, a manager can create an environment in which a team can thrive, and that leads to happy environments. Being a servant leader means you don’t micromanage; you manage for outcomes. Is team happiness part of your culture? |
||
Three Ways to Increase Test Coverage Most defects are due to poorly defined requirements and incomplete test coverage, and fixing an error is cheaper at the coding phase than during testing. In order to ensure more thorough testing, try functional workflow documentation, four-dimensional test coverage, and risk-based prioritization. |
||
Let’s Stop the Password Madness People and organizations definitely should take security seriously. That said, some of the “experts” advising about password security are going too far. Frequent password changes give the appearance of more robust security without actually affecting anything. Payson Hall unpacks this requirement. |
||
Focus on the Most Challenging Parts of Your Project We estimate to make decisions and to give an answer to the question, "When will this be done?" But estimation has limits, and trying to estimate too precisely in an agile project is wasteful. By driving the backlog based on priority, you can better deliver what is valuable to the business. |
||
Meetings: The Good, the Bad, and the Ugly Meetings are a crucial part of the communication process, but they endure a lot of ridicule. You can’t do away with them entirely—meetings are essential to an agile process like Scrum. Rather than avoiding all meetings, it’s better to work at making the times you meet with people more effective. |
||
Managers Are Still Good for Self-Organizing Agile Teams When teams self-organize to deliver software and solve problems, they can be more robust, effective, and directed. But this begs the question: If agile teams self-organize, do they really need managers? Yes, they do. Managers help create conditions that help teams thrive. Read on to find out how. |