..............................

IT project management ...

.. is difficult. hell yeah. but.. its a challenge. you just gotta show them that you can do this, implement whatever that you get during those college years and that the new solution will make the system even more reliable. and therefore higher income. although unfortunately increase team member's monthly salary. well .. bonuses atleast ?

its actually not a new idea. the idea was there all along. but no one touched it, since there are quite a lot of faults and mistakes in the old system, that were busy fixing the old. the old is just like a mine-field system. you just keep on walking, armed with a metal censor in your hand, and you realize that your life depends on that tool. at a point the censor indicate a mine, you blow and eliminate them, and
start walking, in nay directions, looking for a new mine. and its a hell large mine-field. enough about this mine-field thing.

the tech department, think at some point we just gotta stop fixing and patching the old, and start planning and implementing the new. because thats just too tiring. the management keep on asking for reports. and the reporting system, is not a good one, in the same period, the number of transactions, could change by it self. and the would ask 'why is it like this?' and we would say 'its the old system'. and they
would say 'fix it'. and we have to track down the functions to query level and check the result against the records. tiring eh?

i'm not saying we dont get support from the management. we do. its just that, they're way too slow in deciding and planning, imbalanced with their demands for speedy results. so we, the techinical staffs, have to shove and push them around to make the decisions. because we definitly cant go forward or anywhere, except backward, if we dont get the final kick-off.

so, yeah, without the permission, i make this almost complete, analysis and design documents, without a proposal or project kick-offs. it contains diagrams of what the staff discuss about the system, in semi-official meetings. so, currently, we have architecture plans, servers communications, system access channels, report-scheduling, state transition diagrams, new database and tables design, development environment plan (and files... man thats too strict!), and a 1.5 months long project schedule.

and now, i'm stuck in resource allocation (read : coder allocation), who will be doing what. i really dont have the authority to push my co-workers around. maybe i just have to use A, B, C.

--

Wida Sari Suryoputro,
IT Staff.

posted by wida @ 10:59 AM