Related Content
What You Can Learn from Failure—and from Success Success and failure teach different lessons. Lessons from failure tend to revolve around what not to do next time around, whereas lessons from success focus on what you can do again, perhaps even better. But whether you experience success or failure, the key is to take the time to learn from what happened. |
||
What's in the Spring 2018 Issue of Better Software Magazine The Spring 2018 issue of Better Software magazine is now available, and it's got a great mix of foundational basics and cutting-edge techniques. This roundup describes the featured articles about DevOps, service virtualization, Scrum, test automation strategies, and testing for the internet of things. |
||
Is There a Bias against Manual Testers? Manual testing might not be as all-important as it once was, but it’s still needed if you have any hope of delivering software at a quality you can be proud of. How we create software is going to continue to change, but the burden of that change needs to be handled by more than one group within the industry. |
||
How to Offer Help in a Way That’s Actually Helpful When you see a coworker who’s stuck or upset, it’s natural to ask, “What can I do to help?" But this can be the wrong thing to do because the question, though well-intended, is too vague. It puts the burden on someone who is already stressed to identify the possible ways you might help. Here's what you can do instead. |
||
3 Must-Read Books for a Good Agile Foundation If you are searching for agile knowledge, there are many books outside the current literature that may enlighten you. Some discuss the underpinnings of concepts we consider agile, while others are contemporary business books that present compelling ways to use agile effectively. Here are three Jeff Payne recommends. |
||
Do Most Agile Teams Lack Creativity and Innovation? You can’t solve the problem unless you know what that problem is, and you can’t rekindle your creativity if you just don’t know why you’re doing what you’re doing. Pinpoint your team’s purpose, let everyone on your team contribute, and rekindle the innovative nature at the core of agile. |
||
Make a Point of Appreciating Others—and Yourself Offering appreciation is an easy yet powerful way to acknowledge a coworker’s efforts. It’s one of the best ways to say thank you. There are many ways to show appreciation, including verbally in person, over the phone or by email, or writing a note. And while you're at it, reflect on what you appreciate about yourself. |
||
Elevate Code Quality by Integrating Testing and Development Pair programming generally involves two programmers working on a single change from start to finish. You can augment this pattern by adding a test specialist, so you can test-drive feature changes first and the tester can ask questions and guide test and code design. What you get is quality built in from the start. |