Related Content
How Retrospective Meetings Can Improve Your Team's Software Quality Efforts Many software professionals think they won't get anything out of retrospective meetings and want to cut them out entirely. However, retrospective meetings are a necessary part of project progression, and they can significantly improve your team's software quality efforts. |
||
How to Adapt to IoT Devices and AI as a Software Professional When something about your job changes, it’s easy to panic. However, you shouldn’t discount all your current skills or fear you’ll have to be retrained just to continue testing and developing software. The best part about IoT and AI is that what you’re doing now will transfer over. |
||
Why You Should Build Your Software How Boeing Builds Planes Instead of building each individual part of a piece of software, putting it all together, and testing it to see the results, maybe we should look to how planes are assembled. By testing each aspect of the product in isolation first, problems are discovered earlier and software can be delivered faster. |
||
Reviving the Master Test Plan in the Age of Agile In the competitive environment of delivering software more quickly, many teams have abandoned detailed test plans. Michael Sowers argues for bringing back the overarching master test plan—not to have more documentation, but for the questions, creative test designs, and critical thinking the planning brings. |
||
The Changing Role of Testing in DevOps Testing is just as important as ever, but with DevOps, who does the testing and how it is done are changing. Testing has become the responsibility of everyone along the software development lifecycle, and automation is key to success. Learn how testers should elevate their skills and shift their QA mindsets. |
||
3 Ways to Foster Enthusiasm in a Software Team Enthusiasm can’t be forced on you. If you’re not passionate about software, it’s difficult for someone to get you to the point where you wake up in the morning excited to develop a mobile application. However, the conditions of your software team can change your level of enthusiasm drastically. |
||
Shorten Your Feedback Loops to Build Better Software, Faster When we have short feedback loops, we are still in the moment for that feature. We still have the context. The longer the feedback loop, the less likely we are to still have all the context for the feature because we are on to the next piece of work. How long are your feedback loops? Can you shorten them? |
||
Why Chemistry and Character Are Often Afterthoughts When Building Software Teams One aspect of the interviewing process you can’t forget is chemistry. We so often look at someone’s skills and competence in certain areas of the job and completely forget that if that person can’t work well with your current team, development won’t go smoothly. |