I build guitars.

I'm also a software engineer and project manager for a large manufacturing firm and often find myself consumed with implementing large, multi-stage IT projects (macro projects). I also spend a fair amount of time handling requests for enhancements or upgrades. Often these are short duration projects that can be completed quickly and only involve a handful of stakeholders (micro projects). As I reflect on the nature of my work (in and out of the office) I realize that many of my activities and hobbies could be classified as micro projects.

Some clarification: most people can conceptually understand a large project – many stakeholders and participants, a long duration, often highly complex with a substantial budget. A small project, by accepted definition, is typically a one to six month project with a limited scope, budget and only a few stakeholders. A micro project, on the other hand, could be defined as even smaller – less than a month of effort and often executed by a single person. The budget, scope and risk tend to be much more intrinsically manageable than the large, multi-year project.

Business Intelligence has been a main piece of software in the Enterprise toolkit for many years. Fortune 500 companies will typically spend six figures or more – sometimes much more – when implementing BI systems but the payoff can be tremendous. Today, the many benefits of business analytics are not limited to the large companies that can afford expensive and complex commercial software. The advantages of data analysis and reporting can be enjoyed by smaller companies, giving the entrepreneur the competitive edge in expanding market share or micro targeting specific demographics.