Technical debt is an inevitable side effect of legacy code. Some code can (and should) be pruned, but institutional memory fades—what if there's a reason certain lines were included that may not be immediately obvious? Done right, unit tests can serve as documentation. Later on, these tests can illuminate what the developer was thinking when they created the code.
Software companies with tight-knit agile and robust release management practices have a significant competitive advantage. To realize this advantage, an organization must first optimize its release management process and identify the most appropriate platform and release management tools. In this article, Surinderpal Kumar explains three major software release management trends every software development organization can benefit from.
Karen Favazza Spencer writes of the time her team members had to modernize and expand the capabilities of their legacy system. In this situation, Karen took on the role of ScrumMaster, implemented several helpful agile techniques, and empowered the team to share leadership of the project with management.
Beware of the hidden sirens in your rewrite project. They will sing the words you want to hear--that the project is easy to complete. Don't be fooled: Sirens are mythological, but the lure of rewrite projects can be quite real. Rewrite may seem a simple task, but it isn't until you're deep into it that you'll start to realize the true nature of the project. In this article, James Shore offers some words of wisdom (and warning) to help guide your rewrite project in the right direction.