7 Steps to Surviving a Software Product Assessment

Software product assessments happen for a lot of reasons, but the three most common reasons are:

  • There is a transaction happening – usually a funding event or the sale of the company – and the people on the other side of a transaction want to see that your product works as advertised.
  • Your company is conducting a portfolio review and wants to compare your product with others in the company that could also use investment.
  • Your company is going through a budgeting process to see what level of investment you need.

When you prepare for your next software product assessment, technical details are just the starting point. You have to keep in mind the business problem your product hopes to solve. Thriving – not merely surviving – through a tough technical audit should be the end game. Here are seven key secrets for conquering your next software product assessment.

More »

Refactor vs. Rebuild: The Next Generation Application Development Dilemma

One of the toughest choices an IT organization must make is whether to refactor an existing application or rebuild from scratch. The economic stakes are high; time to market is always critical; and the end-user community usually wants something new by tomorrow – at the latest. IT teams begin looking at the refactor-versus-rebuild decision when the application:

  • Lacks key functionality because it hasn’t evolved with the business (e.g., mobility or cloud integration)
  • Performs poorly
  • Becomes hard to maintain and upgrade.
  • In addition, the technologies once used to create the application may have become obsolete and no longer align with best practices for software development. Even worse, they may no longer be supported by the vendors that created them.

Here are six key factors you need to consider as you decide whether to refactor or rebuild your application.

More »