Anticlue

Change Management

I'm toying with the idea of rewriting a change management app we have at work in my non-existant spare time at home. Toying is a good word here because that conflicts with some of my basic principals. I like to work on projects with managements blessing, the resource availability, fully architected, and using the SDLC. I know there is an application out there we can buy, I just haven't researched that yet. Also an IT goverance package was not approved in the business cases this year or next. The problem is I really don't have alot of coding time at work anymore, and I miss it. Also the application is screaming, i mean literally screaming for a new do.

The app captures the change, the impact, the hardware, the vendor, and the approval process. I'm going to be going into these more later. However, if you were going to use a change management application what information would you like captured within it?

What I'm proposing is doing the full development here on the blog, and posting the deliverables as it goes. This is inclusive of requirements gathering, design, construction, testing, and live. But I wanted to gauge if anyone thinks that is a good idea.