feedback
Focus on User Input for Software Product Development Determining the kind of product that's developed boils down to what the user wants. These days, end users are very vocal in sharing their feedback about a product—the good, the bad, and the ugly. Companies would do well to gather input efficiently, pay heed to the results, and then respond quickly. |
||
Why Accepting Failure Is Necessary The phrase “failure is not an option” is a common cliche often used to motivate people to succeed. But forbidding failure does not prevent it. A mindset that denies failure might actually detract from long-term success. |
||
Embrace Your Mistakes—Make Friends with Pairing and Feedback We'd rather be recognized for our accomplishments than our mistakes, but chances are you're more worried about the mistakes you've made than are your coworkers who saw your gaffe. Pair programming and feedback are great ways to recognize the good and the not-so-good of everyone on the team. |
||
Acknowledging Work Effort Can Increase Productivity and Motivation Steve Berczuk writes on the importance of acknowledgement in making people feel good about work. Simply acknowledging someone’s effort can lead to increased engagement and motivation—and result in more productivity. |
||
Why You Must Depersonalize Feedback to Become a More Valuable Tester Welcoming feedback isn’t as easy as it sounds, especially when you’re in a testing role and potentially getting constant feedback from numerous sources. If you don’t depersonalize feedback and you react defensively, the people around you will likely start to disengage, check out, and move away. |
||
Why People on Agile Teams Need Feedback Agile teams work by continually improving, and feedback is essential for agile methods to work well. Giving feedback to your team members and peers is hard, and receiving it is sometimes harder, especially when it’s not delivered with the right amount of thought. |