Category Archives: Project Management

The Four C’s to Sell MOSS

You’ve been tasked with bringing some order to the chaos of your various organizations’ file shares, e-mail servers, and externally facing websites. After all the research and analysis you’ve done you’ve decided that MOSS 2007 is the optimal solution to solve the problem. The problem? Selling it to management. You can demo MOSS with all its fantastic features and Office integration, but your management needs some “bullet point” reasons why they should invest in MOSS. In Essential SharePoint 2007* the authors lay out the “four C’s” of company portals that MOSS can satisfy. These can be (read more...)

Harvest Reports WordPress Plugin

When freelancing I use the Harvest application to manage all of my time tracking. It has made invoicing painless, and while I got it thinking I was over-charging my clients, it turns out then I was not charging them enough! Anyway, after being listed as a WordPress consultant by Automattic I naturally had more WordPress contracts. I then wanted to solve a business need by allowing my clients to view their impending charges inside the familiar WordPress administration interface. This was impossible until recently when Harvest published their full API. I now have the ability, through REST, (read more...)

The Value-Up Paradigm

The paradigms I’m going to contrast are how we view the entire development process. I will refer to two different paradigms: the first is the “work-down” approach which I will contrast with the “value-up” approach. I read about this in Software Engineering with Microsoft Visual Studio Team System concerning the new Microsoft approach to software development including an introduction to the Agile SDLC. However, I’m not here to promote Microsoft Team System or Agile methodology; instead, I’m here presenting a paradigm that is pertinent regardless of your chosen SDLC or technological platform.I will start by defining both (read more...)

Engaging the Entire Development Team

Before I left college the only experience I had in software development was as a one-man team. I did all the design and back-end development. There wasn’t a conflict of interest between designer and programmer, because they were both one person! As I left college and got into the “real world” I found that it was impossible to do large-scale software development by oneself. All of the sudden there were information architects, program managers, user interface experts, database administrators, technical writers, and on and on. I came to realize the value of specializing in one field. (read more...)