Related Content
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. |
||
Joking Around and Taking Work Seriously You may be totally serious about your job yet give the impression that you’re not. Laughter and fun help some people tackle the high-priority, stress-inducing problems they face every day, but it can also be misinterpreted by others that they aren't taking their work seriously. How are people perceiving your behavior? |
||
How to Make Sure Your Website Is Fully Accessible Ensuring accessibility to websites, applications, tools, platforms, and other forms of technology is not only a legal requirement; it should also be a social responsibility of web developers, testers, and other software professionals. Here are some basic recommendations to keep in mind to make any website accessible. |
||
Don’t Ask for Permission or Forgiveness—Use an Agile Alternative Some teams get around bottlenecks by taking a “better to ask forgiveness than permission” approach. This may be expedient, but it doesn’t provide a path to changing the organizational dynamic, and it can lead to wrong decisions when wider input is advisable. A more agile way is to take an “I intend to” approach. |
||
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. |
||
If Santa Can Be Agile, So Can You To improve his toy development lifecycle, Santa Claus had the North Pole move to an agile and DevOps approach. Santa knows it's important to accept requirements late in the process, work incrementally, deploy on time, and—above all—focus on the customer. Here’s what he found to be more effective with agile and DevOps. |
||
Security Testing: A Constructive Mindset with a Destructive Approach A typical tester mimics end-users, who are constructive when exploring an application’s functionality. But the role of a security tester is different. Their focus is mainly on mimicking hackers, who are intentionally destructive. A solid security strategy should balance both constructive and destructive efforts. |
||
2 Ways to Know Your Work Is Actually Done Some people think a good indication that a piece of work is done is if it's been tested. But by whom, and how? Testing alone doesn’t specifically determine whether you are done—especially when we probably don’t mean the same thing when we all talk about testing. Here are two ways to know when your work is truly done. |