Related Content
 |
Agile Collaboration on Remote Teams The first value in the Agile Manifesto is “Individuals and interactions over processes and tools,” and for many teams, being located in the same place facilitates these interactions. However, being part of an effective, collaborative team is less about location than it is about motivation and good practices. |
|
 |
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. |
|
 |
What to Keep in Mind If You Want to Be Persuasive To successfully persuade someone of something, it’s important to keep in mind how you come across to others—when you’re trying to persuade and when you’re not. It's a good idea to build up trust and credibility before you need something, listen to others when they're in need, and think about tailoring your message. |
|
 |
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! |
|
 |
5 Reasons You Should Have More Unit Tests The test pyramid is a valuable visual in agile. In particular, it argues that unit tests should make up the majority of tests, and while agile teams recite this principle, it is often not clear why it is so important. Here are five reasons unit tests should make up the majority of tests written for an application. |
|
 |
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. |
|
 |
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. |
|
 |
Creating a Cohesive Culture in a Distributed Organization When organizations are distributed across multiple locations, it brings questions about how much each location should have a unique identity relative to the larger company. While a theme of “we are one” is common, it’s better to embrace the differences and work toward being a cohesive group that celebrates diversity. |
