Related Content
 |
Agile+DevOps Culture in a Virtual World Transforming and maintaining culture is hard enough when team members are somewhat co-located and in physical spaces—even harder when the majority are working from home. |
|
 |
How Agile Principles Help in a Remote Working Atmosphere When working remotely, teams often face high risks due to lack of communication and differences. However, when implementing agile principles, even remote teams can minimize the risks of failure. |
|
 |
Test, Test, Test Test, test, test. This is a phrase that has caught everyone’s attention this year as we grapple to mitigate COVID-19. The WHO states that testing is the only way out, as we cannot fight the pandemic blindfolded. |
|
 |
Evaluating Team Health in Agile and DevOps The importance of the human element in delivering great software is sometimes overlooked, as is the relationship between team health and team performance. Just like physical health checks, team checkups are important. Let's look at some factors that can affect team health and how you can evaluate the important metrics. |
|
 |
Making the Most of Your DevOps: A Slack Takeover with Gene Gotimer Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Gene Gotimer, a senior architect at Coveros, hosted this Slack takeover and discussed all things DevOps, including whether you can have DevOps without agile and how you can reap all its benefits. |
|
 |
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. |
