Related Content
 |
Collaborating with a Highly Distributed Team Being distributed can cause challenges for team collaboration, such as insufficient communication and a lack of visibility. However, advancements in tools, technology, and best practices have helped to lessen some of those challenges. Here are four ways to make collaborating with distributed teams more seamless. |
|
 |
Don’t Ask for Permission or Forgiveness—Use an Agile Alternative Some teams get around bottlenecks by taking a “better to ask forgiveness than permission” approach. This may be expedient, but it doesn’t provide a path to changing the organizational dynamic, and it can lead to wrong decisions when wider input is advisable. A more agile way is to take an “I intend to” approach. |
|
 |
Stop Fanning the Flames of Constant Firefighting Continually having to address unexpected problems interrupts your original sprint activities, causing stress on the team members and fanning the flames for future firefights. But with due diligence, you can lessen the need to constantly put out fires. Here are some steps that can break the cycle of work and rework. |
|
 |
5 Questions to Ask When Choosing a Software Provider When working with an outside company to develop a new product, there are many things to consider. You need to find a service provider that can make your vision a reality on time and on budget. Here are five questions you should ask prospective service providers to make sure they will be a good fit for what you need. |
|
 |
2 Ways to Know Your Work Is Actually Done Some people think a good indication that a piece of work is done is if it's been tested. But by whom, and how? Testing alone doesn’t specifically determine whether you are done—especially when we probably don’t mean the same thing when we all talk about testing. Here are two ways to know when your work is truly done. |
|
 |
4 Tips to Refocus Stale Standups The daily standup is supposed to get everyone on the same page and make teams more productive and efficient. But it’s easy for this short meeting to become stale and stop providing any real benefit. Here are four ways to get out of the slump of merely delivering status updates and re-energize your daily standups. |
|
 |
Is Your Culture about Responsibility or Blame? When things go wrong, it can be helpful to understand what happened and who was involved. However, all too often organizations (and the managers within) confuse responsibility with assigning blame. The former is essential for improvement. The latter works against an effective, collaborative, productive culture. |
|
 |
Beware of Success Stories The tendency to look back and think you know what contributed to a success is called survivorship bias. It occurs when you make a decision or take some action based on past successes while ignoring past failures. That's why it's important to approach reports of successful projects with a healthy dose of skepticism. |
