Related Content
Plan for the Year the Agile Way The start of a new year always comes with new resolutions, goals, and a set of plans to grow in the future. The excitement and energy that a new start brings can rejuvenate a team. However, if you’re not careful, that same ambition can lead to failure. This year, adjust your strategy and plan in a more agile manner. |
||
The Curse of Rushed Requirements When development is outsourced, a documented baseline of expected functionality sets expectations for both the client and developer. Acknowledging that agile practices are flexible, beware the trap of rushing requirements just because you know they are going to change. It's still essential to be as accurate as you can. |
||
Top 10 TechWell Insights Stories of 2019 Career development was on many software practitioners' minds in 2019, as some of our top stories were about having a technical lead on a Scrum team and making the switch from quality assurance to quality engineering. Stories about new ideas such as DevOps and continuous testing also ranked high. Check out the roundup. |
||
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. |
||
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. |
||
A Software Testing Primer When development teams are pressed for time or budget, testing is often the first activity squeezed out. But testing will actually save you money in the long run. This story gives the basics of why it's crucial to test early and often, the types of testing you should perform, and how to get proactive against bugs. |
||
Testers Must Use Team Connections to Enable Quality The quality team has the greatest reach in its visibility and ability to connect with all other engineering and non-engineering teams. For a tester to realize their fullest potential, they need to acknowledge and leverage this reach by communicating and collaborating with all other teams to create the best product. |
||
Security Testing and Assessing Risk: A Slack Takeover with Shachar Schiff Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Shachar Schiff, founder and principal consultant at BadTesting, hosted this Slack takeover and discussed assessing code coverage like a risk analyst, risk assessments outside security, and more. |