Related Content
 |
3 Critical Considerations for Technical Due Diligence Technical due diligence is the process of verifying a company’s technical capabilities, quality, and processes. It is typically performed by investors or buyers before a contract. There are many aspects you can investigate, but three are crucial: a code review, security evaluation, and open source components compliance. |
|
 |
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. |
|
 |
Comparing Java and Ruby Java and Ruby 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. |
|
 |
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. |
|
 |
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. |
