Related Content
Project Management in Any Industry Software teams in niche industries may think they require a project manager with expertise in their domain. Good project managers can anticipate and address the primary considerations for any project, regardless of industry, but if you encounter a skeptic, here’s a generic template you can use to pitch any project. |
||
4 Common Mistakes New Managers Make Making the transition into a management role is a huge step—but also one fraught with opportunities to make mistakes. Having an inkling of some of the more common mistakes new managers make might help in avoiding them. Here are four mistakes to be on the lookout for so you don't make them as a new manager. |
||
What's in the Summer 2018 Issue of Better Software Magazine For twenty years now, Better Software magazine has published articles offering helpful tips and techniques for those in the software industry. The new issue celebrates those two decades of knowledge-sharing—and, of course, gives you more ideas. Articles this issue focus on leadership and software quality. |
||
3 Mistakes Teams Make When Choosing a ScrumMaster One cause of agile project failure is choosing the wrong person as your ScrumMaster. While a bad ScrumMaster is a problem for any team, it is particularly bad for teams new to agile, as the team won’t know they are being led down the wrong path. Here are three mistakes organizations make when choosing a ScrumMaster. |
||
Be Careful What You Ask For: Contract Considerations for New Projects In a new project, there are always going to be challenges and delays, and when the end date is looming, you may be tempted to rush through the contracting and procurement process. But that can have dire consequences down the line if roles, responsibilities, and expectations aren't clear. Take the time to communicate. |
||
Mob Programming: Working Well Together Mob programming is a whole-team approach to creating software where everyone works together on the same thing at the same computer. It's not a bunch of people watching one person write code, but rather everyone thinking, discussing, designing, and collaborating. Sound crazy? Here's how it improves the quality of code. |
||
Thinking Inside the Box before Venturing Outside It In their rush to solve a problem, teams often overlook conventional methods in favor of out-of-the-box ideas. But sometimes, the old standbys—thinking first, reviewing criteria, and asking questions—work the best. Before jumping to creative tactics, start by examining the possibilities readily available inside the box. |
||
Analyzing the Software Team Generalist There's a recent trend in having generalists on the software team—there are no developers or testers, only "team members." The idea of the two roles learning from each other is a good one, but it's usually a one-way street: Testers learn to write production code or test tooling, but no one focuses on deep testing. |