Related Content
 |
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. |
|
 |
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. |
|
 |
Coaching Senior Management to Be Agile Embracing an agile mindset isn’t always easy, and it can be especially difficult for senior managers who spent most of their careers working in more traditional development methodologies. By trying to speak the same language and demonstrating successful self-organization, teams can help senior management become agile. |
|
 |
Understanding the ScrumMaster's Role in Team Communication Some agile teams believe the ScrumMaster is the sole point of communication between them and the product owner, so the team can abdicate any responsibility to communicate with stakeholders. That couldn't be more wrong. It's actually the ScrumMaster's job to enable communication and coach or guide the team to solutions. |
|
 |
Are You Forgetting a Stakeholder? Technology allows amazing innovations to optimize business and deliver new and better services, but if you don’t carefully consider your entire user community, innovations may cost you business. When designing for stakeholders, don't stop at the obvious cases—or else you may find that you forgot an important customer. |
