Category Archives: Methodology

Why your projects don’t seem to get “done” (part 3)

Okay, so let’s say that you are a shrewd manager, and you are certain that your requirements are crystal-clear, your scope is contained, and yet, stuff isn’t getting “done”. In that case, part 1 & part 2 (of this article) … Continue reading

Posted in IT Psychology, Lessons Learned, Methodology, Professionalism, Team | Tagged , , , , | Leave a comment

Why your projects don’t seem to get “done” (part 1)

In my career, I’ve seen a few projects that had a problem getting “done”. Okay, I was being too nice. Let’s just say: it happens more-often than I think it should. I’ve even had a CIO mock me because I … Continue reading

Posted in Lessons Learned, Requirements | Tagged , | 1 Comment

Knowing what you don’t know

A few weeks ago, I had the joy of experiencing a new twist on an old problem: gathering requirements.  I have a small project which has missed a deadline or two.  Naturally, I’ve heard question a few times: “when will it … Continue reading

Posted in Lessons Learned, Requirements | Tagged , , , , | Leave a comment

Switching from dev-process to maint-process

I was going to name this article “Maturity model for maintenance programming”, but every time I read that title, I cringed. Maintenance programming is not much fun. It sounds a bit like “prison guard” or “mortician”, or some other unpleasant … Continue reading

Posted in Lessons Learned, Methodology | Tagged , , | Leave a comment

My most epic project

The biggest project of my career was a Y2k project for a state agency. The project was a huge challenge by itself. To make things more interesting, it had a fixed timeline (Y2k) and a customer who didn’t typically do … Continue reading

Posted in Career, Lessons Learned, Methodology | Tagged , , , , , , | Leave a comment

Why management wants more technical debt

*** Disclaimer: this is not about my current project. It is about every project. *** I think it is safe to say that every program contains some technical debt.  This is because perfection is (somewhat) impractical.  If you actually try to achieve it, … Continue reading

Posted in Lessons Learned, Methodology | Tagged , , | Leave a comment

Technical debt and interest

In case you are not familiar with the term “technical debt”, it mostly means “messy programming”.  Unfortunately, it is more serious than just ordinary messiness.  It usually happens because a programmer was in a hurry and couldn’t think of a … Continue reading

Posted in IT Psychology, Methodology | Tagged , , | Leave a comment