Related Content
 |
Solving Problems and Seeking Solutions on an Agile Team While teams are composed of individuals, all of whom solve problems and make decisions, people on consistently successful teams understand that they can be more effective when the focus is on the team, not the individual. Making the best decisions collectively delivers the most value to customers in the long run. |
|
 |
3 Ideas to Prevent ‘All Talk and No Action’ Meetings When many people are speaking in a meeting but it never translates into meaningful actions later on, it can leave us frustrated. But with some planning and collaboration, we can facilitate ways to make it easier for people to communicate better. Here are three ideas for a little less conversation, a little more action. |
|
 |
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. |
|
 |
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. |
|
 |
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. |
|
 |
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. |
