(no subject)

Ah, it's nice to be back at work and busy— as opposed to Friday, where i was at work, but having my time actively wasted by other people.

Busy is good. It keeps me from getting bored. And, since the developer i'm actively working with now kicks ass, he's given me sufficient stuff to do to keep me busy for another few hours.

(no subject)

Project and Project Web Access. What insane pencilpusher dreamed this bastard child application up?

Well, in all reality, it might not be too bad if people actually checked off on tasks reliably. Instead, once every few weeks, i get e-mail wanting to know how much time different tasks which i've never seen before- because the PMs who love this tool don't love it enough to actually update it regularly.

So, i figure, if they're not going to do it regularly, i'm not going to make an effort to remember what i did each day.

So- i've done 360 hours worth of work today- some of it on stuff which in the real world i did back in November.

I think this sort of efficiency deserves a raise.

(no subject)

Hey, lokheed! Remember the concerns you voiced about our release? At this point, the only thing that's going to hold it up is if Daniel's not ready with his release- as of 5:30 today, it had eight open issues and he'd just found a new one. All of our 5.5.1 fixes have been verified in test and are good to go, leaving only the last few items left, all of which except for the one checkin oddity, i think can be safely deferred until the next maintenance release- so i'm not concerned in the least about it.

You, sir, rock.

In other notes:
I'm convinced that the precepts of Agile Development can work in a vacuum.
I'm equally opinionated that the way we're implementing it is critically flawed. It is being driven by people who don't know the personalities of the people in the department, much less whether there are working processes in place; and they don't seem to care when a self-organizing team begs to be let work on things that are well within their scope and practice- the same group which has been doing so for an extended period and has met or beat every deadline, as well as having demonstrated a capability to release on a bi-weekly basis.
If people had been brought in entirely for the purpose of doing this, they could become an effective team. If the late arrivees bothered to listen to some of their senior staff, they'd have a capable team. As it is, the personalities ang work ethics on the team they've assembled will make it tough, and that difficulty will be compounded by the fact that the database admin, the user experience designer, and the quality assurance engineer all are also tasked out on other projects.