Related Content
 |
Refine Your Product Backlog Continuously to Improve Flow One way to address poorly defined product backlog items is to spend time refining the items as you go. Refining the backlog continuously helps the team deliver consistently and can lead to shorter planning meetings at the start of the sprint. It can even help improve reliability, velocity, and the quality of work. |
|
 |
The 6 P’s of Getting Started on a New Project Ideally, when an employee is transferred to an existing project, there would be at least one team member designated to train the new person. However, this isn’t always the case, and you may be left to fend for yourself. If you suddenly find yourself on a new project, take control and get started with the six P’s. |
|
 |
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. |
|
 |
Why State-of-the-Art Technology Needs Art and Tech There’s a longstanding, often passionate debate about art versus design and what separates the two. Now, many advocate that technology presents yet another creative medium, and silos are being torn down as art, design, and technology are increasingly entwined. |
|
 |
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. |
