Related Content
New Features in JavaScript Here we’ll explore the new features in the most recent version, ECMAScript 2020, which is the 11th edition of the ECMAScript Language Specification.
|
||
Test Teams Evaluation to Improve Effectiveness Evaluating a test team member’s abilities is crucial in recognizing deficiencies within the team, and it provides an opportunity to outline a strategy to remedy the weaknesses. Selecting the proper method for evaluating the test team’s abilities is vital. |
||
How AI and Machine Learning Are Revolutionizing the Manufacturing Industry Manufacturing tasks used to be manual up until the Industrial Revolution. We’re now experiencing another revolution, with technology making processes easier, faster, and more efficient. Today, artificial intelligence and machine learning are automating machine maintenance, optimizing inventory, and even helping out humans. |
||
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. |
||
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. |
||
What’s the Problem with User Stories? Agile projects focus on very lightweight, simple requirements embodied in user stories. However, there are some problems with relying solely on user stories. They often don't contain enough accuracy for development, testing, or industry regulations. There's a better way to write detailed requirements that are still agile. |
||
Testing in the Dark Requirements only go so far in identifying areas to test. Sometimes testers are given no information at all, leaving it up to them to determine what to test. Don’t accept the need to indiscriminately test with no clear understanding. Your testing should be targeted, and these techniques will help focus your test effort. |