Related Content
 |
3 Myths about Software Project Managers People often have the wrong impression regarding the activities and responsibilities of project managers. You'll hear them say that managing a software project is all about delegating work and keeping the crew in line, but it's more than that. Let's debunk three common, pervasive myths about project managers. |
|
 |
Who Should Be Doing Automation Work? Testers often look at automation work as the next career step after manual testing. Automation work has more visibility at the project level, and people who do this work usually also tend to have a little more social status. But Justin Rohrman makes a case for why testers shouldn't be the ones doing automation work. |
|
 |
6 Signs Your Agile Project Isn’t Really Agile There's a trend of organizations declaring they are agile without actually changing how they develop software. Declaring that an apple is an orange doesn’t make it so. These six key indicators can help you determine whether your agile project isn’t really agile after all—and give you some solutions to help. |
|
 |
2018 Hour of Code: Let’s Dance What kid doesn’t love a dance party? With aliens and sharks that drop, double down, and dab? Introduce kids to the basics of computer science in a way that doesn’t elicit “I’m boooored” with Dance Party, the draw for the 2018 Hour of Code. Do a little dance, make a little code! |
|
 |
Feature Branching Is Not Evil Some people believe branching and pull requests are inherently bad. True, branching done poorly can slow down a team, but advocating for avoiding branching altogether can lead you to ignore the more important goal of an agile process: rapid integration of changes. First, make sure you're considering the right metrics. |
|
 |
The Premortem: Planning for Failure While a postmortem, or retrospective, is done after a project is completed, a premortem is done before the project starts as a way to imagine that the project failed and to explore what went wrong. You list every possible thing that can go wrong, then devise solutions to the most probable risks—before you need them. |
|
 |
4 Ways to Increase Software Quality and Decrease Test Time Software testers are continually under pressure to test faster without sacrificing quality. By taking the perspective that quality is the responsibility of the entire team, not just the testers, shorter test cycles with higher quality software are possible. Here are four ways the whole team can improve releases. |
|
 |
Crowdsourcing Emerging Manufacturing and Water Security Technology Borrowing from the successful NASA Challenges playbook, the US Department of Energy recently launched several crowdsourcing efforts to incentivize new applications and technologies in additive manufacturing, also known as 3D printing, and transforming nontraditional water sources into resources. |
