Related Content
 |
Why You Should View Every New Workplace Challenge as a Confidence Booster New challenges can certainly be rich learning opportunities, whether or not the effort is a success as anticipated. It's time to view every new challenge as an opportunity to boost confidence. You certainly won't lose—you only stand to gain with this approach. |
|
 |
The Art of Giving Feedback Your Team Will Act On Giving good feedback is hard. A common pattern we follow—especially when we have to give negative feedback—is starting with something positive, addressing the problem, and ending with something else positive. But it turns out this "feedback sandwich" method isn't the most effective. Here are some better ways. |
|
 |
Shake Up Your Software Processes: The Intermediate Disturbance Hypothesis Organizations that refuse to change will get left behind. But at the other end of the spectrum, too much change is also harmful. Revamping everything you do at once creates stress and can lead to your efforts failing. The right balance is shaking things up just often enough to experiment with new ideas. |
|
 |
How to Build Credibility as a Tester Respect is a major player when it comes to creating and maintaining a cohesive team, and plenty of testers today feel they’re lacking the respect of their peers. With test automation sometimes being seen as some magical solution to fixing bugs, the usefulness of manual testers has come into question. |
|
 |
Scaling Product Agility: More Product, Not More Process Focusing on scaling product discovery that feeds product delivery is valuable to scaling frameworks. A cross-team product discovery cadence highlights work that's valuable to everyone and facilitates workflow for all the teams, helping them produce more of what they really need (and less of what they don’t). |
|
 |
Go-Live Lessons: The Path from Software Development to Production On systems integration projects where a vendor is building or configuring a system for a client, you sometimes cross the canyon from development to production and maintenance in several smaller bounds rather than one big leap. A warranty period after go-live can help stakeholders confidently monitor quality. |
|
 |
Make Better Software by Learning from Your Mistakes If you accept that it’s OK to make the same mistakes over and over, you’ll never give yourself the opportunity to grow. If you don’t grow, you won’t improve your software. A writer should always ask why an editor did what he did, and a developer should understand how he can fix the code he broke. |
|
 |
Dealing with Chronic Complainers in the Workplace At work, you don’t always have the option to steer clear of chronic complainers. If you're kind (and patient), you can listen and empathize. But if that doesn't sound appealing, there are other options. Read on to learn some suggestions for deferring and discouraging complaining coworkers. |
