Scott Norberg has spent the last decade successfully delivering custom (and customized) software using Microsoft technologies in a wide variety of industries, including manufacturing, healthcare, non-profits, marketing firms, and insurance. While he has built software for both start-ups and Fortune 500 companies, he specializes in turning around failing projects and departments for small businesses. He is currently serving as both business and technical lead to overhaul an insurance software company’s internal software and procedures.
Scott has an MBA from Indiana University, as well as several technical certifications from Microsoft.
In his free time, Scott plays tennis, as well as repairs flutes, clarinets, and oboes.
The opinions expressed in this blog are those of Scott Norberg and do not necessarily represent those of IDG Communications, Inc., its parent, subsidiary or affiliated companies.
Most job postings for software developers list a degree in Computer Science as a preferred item, if not a requirement. But are these degrees indicators of better developers?
When companies embark on new software projects, they too often ignore organizational idiosyncrasies that make software tougher to deliver. Having a culture that is particularly tied to broken processes is one such issue that should be addressed.
There's a relatively new movement among software developers called "software craftsmanship" which is meant to help developers learn the right approaches to avoid project failures. My experience has been that the software craftsman appr
There's a sweet spot with unit testing -- and most dev teams are missing it
Automated unit testing is a great tool to help deliver higher quality software at a lower cost. But most software teams either don't write any unit tests or write too many
Many software teams find themselves taking an increasing amount of time to deliver new features as time goes on. It doesn't have to be this way. Consistent investment up front editing your code for readability can pay big dividends in the long r
The success of software projects is traditionally measured by the ability of the team to meet a pre-determined budget and timeline. But these measurements only indirectly measure the software's true value to the business.
Poor requirements can derail your software project before development starts. Here's how to get started in the right direction