Related Content
The Layers in the Test Automation Journey Test automation is not just a bunch of automated scripts to be written and handed off. The scripting process, though important, is just an inner layer embedded deep within the whole. There are several more layers that are important in showcasing the true value of the automated scripts. You need to understand all layers. |
||
Making a Game out of Building an Amazing Team Games are a cost-effective and efficient way to evaluate, assess, and thus hire people with the right expertise and aptitude. It is an equally practical and powerful way to continue to develop and improve the team and individual team members. Try using games to improve your efforts to build and maintain an outstanding team. |
||
Comparing Ruby and PHP Ruby and PHP are both open source languages, and both are ranked in the top 20 of the TIOBE index for most popular programming languages. If you want to learn a new language and are trying to decide between these two, let’s explore common differences in syntax and constructs to discover which may be more useful for you. |
||
2 Familiar Problems for Software Developers In the quest for writing good code and delivering the right thing to customers, developers have several challenges. But most of them can be boiled down to two main problems: discovering the real scope, and how to do the work. Interestingly, they’re very similar to the problems faced by testers and others in non-dev roles. |
||
Why Setting Priorities Is a Core Agile Practice Every aspect of agile includes prioritization. The most important user stories are implemented first. Testing is prioritized to make sure features valued by customers are tested the most. Even everyday tasks are prioritized during daily standups. Here are three reasons setting priorities is essential to success in agile. |
||
Prioritizing Invisible Work There are work items that will give the team an operational boost and perhaps avoid a crisis, but that never make it to the top of the priority list—like build and deployment improvements, or paying down technical debt. For enabling work that is valuable but too invisible to be a priority, consider breaking it down. |
||
Software Features to Avoid in a Production Environment When developing an application, it’s best practice not to use certain software features in a production environment. These include features related to programming language, the OS, the database, a framework, a web or application server, or a tool. You have to consider the production setup to avoid bugs or server crashes. |
||
Team Agility in a Post-Pandemic World COVID-19 has necessitated entirely remote environments, and people the world over have had to inspect their foundations of working, adapt to a new way of remote execution, and integrate their personal and professional lives more than before. Organizational leaders need to embrace a new outlook in four critical areas. |