My personal side bet to myself for yesterday's standup meeting came to fruition in today's meeting. It was as awkward and annoying as I guessed it would be. On the side, it seems that there is a new sense of urgency, fright, and agitation from Jefe. She made brief mention that we need to "shave off time" from the project, and might be punting less than necessary work items. Hmm. So Falloutboy's prediction of the rejection for Jefe's estimate to finish the project was correct. Falloutboy also indicated we are hiring a new person Monday. Wow.. really? My guess is by the time the new hire is up to speed the project will be done.

We have no requirement docs.

We have no design docs.

we have NO DOCS what so ever! (a reoccurring problem with most of our systems).

So the new person will have to learn by using it and oral instruction. Yeah, it blows (I've done it). On a side note, the current culture of our department seems to exist like early tribal units... oral traditions are passed on (partially correct but missing information) regarding the system design and reasons "why" something are done. The elders are valued not for the ability but this lexicon of information in their head while their skills diminish. Strange considering one company I worked for had tomes of data on every aspect of their systems. Oh, wait, I forgot... this is how agile development is supposed to go. Silly me!

As it is, Jefe is also trying to punt off our/my old system to our Maintenance Group... sadly I will not be going with it. For some reason she believes this is holding the team back. I am the only one on my team that works on it, and that is sparing since the outsourcing group is the ones doing the grunt work and I only deal with catalogs and dashboard documents - you know things that are time sensitive. Oh well! Jefe knows best!

Now if I can just verify this error isn't occurring as I thought then life is good for the day!