Related Content
Balancing Testing and Delivery Times in Software Development So how can developers and their teams optimize testing procedures with the modern tools and tech available to them? Here, we will explore optimizing testing through experimentation to meet delivery deadlines and adapt to challenges in software development.
|
||
A Tale of Toxic Sponsorship It is difficult to succeed without effective sponsorship—and almost impossible if your sponsor is toxic, as this true tale explains. |
||
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. |
||
A Physical Metaphor for Quick Fixes and Root Cause Analysis If you deal with legacy code you’ve likely found yourself struggling to debug and fix a mysterious, intermittent problem. Along the way you may have discovered some code that didn’t quite make sense. |
||
Schedule Risk Analysis Building schedules for complex projects is challenging. While the results are never perfect, credible schedules are a useful communication and coordination device. Incredible schedules are a dangerous waste of time and energy that damage a project manager’s credibility and cost an enterprise a fortune. |
||
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. |
||
Lessons the Software Community Must Take from the Pandemic Due to COVID-19, organizations of all types have had to implement continuity plans within an unreasonably short amount of time. These live experiments in agility have shaken up our industry, but it's also taught us a lot of invaluable lessons about digital transformation, cybersecurity, performance engineering, and more. |
||
Code Integration: When Moving Slowly Actually Has More Risk Many decisions about code branching models are made in the name of managing risk, and teams sometimes pick models that make integration harder in the name of safety. Moving slowly and placing barriers to change can seem safer, but agile teams work best when they acknowledge that there is also risk in deferring change. |