tisdag 27 januari 2009

Work? What work?

So, just a brief update. I've recently (a few months back *cough*) taken over our Linux "education" group at work, and it's interesting. The sad part is, we mostly only see people who already knows what Linux is as we're working internally in a world where most people are rather Computer savvy as it is. It's given me a few new viewing angles though, and I'll get back to that at a later point.

Currently working on some Trac guidelines for our Change Management process as well. Working from home today to actually get something done with it, as most of the days I wind up getting too many disturbing calls, talks and discussions to be very efficient. Our first two tries at making a decent workflow winded up a bit messy, and I think we really must get this down properly this time.

There are some other things I react on, and want to fix, for example, as it looks now, every single project sets up their own bugtracking/ticketsystem, and every project uses a different system (trac, mantis, clearcase, dimensions, etc). Preferably, this should be centralized in some fashion, and if possible I'd love to get a bit more homogenized environment. As it is, I try to tell people "look, here's a system for handling your day to day tasks, use it!". First time, the workflow got overly complex, second shot was also overly complex, and people where put off by all the choices and steps to take. This problem mainly stems from project/change management criterion.

My latest and greatest (yeah yeah) workflow should alleviate some of these problems by making some of the choices less visible to normal users. Ie, we have one task management system and a problem and change management system baked into one, but normal users (programmers) only use the task management system, while the project manager, tech project manager and CM also have the ability to handle problems and changes in separate workflows.

We're also adding the ability to have supertickets, where a single problem report can contain several tasks. This is a pseudo development so far, as we're not actually adding the whole deal right now, we're just adding the idea of it, not bounds checking or views/reports of it. Basically, every ticket can have a superticket (we add a numeric field to the ticket), which can point to another ticket, which is the "parent" ticket. This makes it possible to handle a large and complex bug in several smaller tickets. Anyways, the idea is there, but it's not fully implemented. If our management likes it, and the others like it, we could implement it for future usage. I'm worried it's too complex however. At the same time, one complex system might be better than 6 alltogether different systems as it allows for longer time to learn? Kind of like... well, unix for example. Once you find ls, its a darn good bit faster than having to click your way through a whole heap of paths to find the specified file list.

At the same time, both me and PM are a bit tired of Trac's shortcomings, maybe change to Mantis for example? My general thought to this however is, we need to stick it out i'm afraid... one more system will just make the normal user less interested in the new tool and hence taking even longer to learn. As it is, people use it at a bare minimum cause they dont know it, give them time to learn it properly, and they might come to like it. Comments on this line of thinking?

For now, tata. Back to writing.