Down To The Wire Change Requests

So, I'm logging out to catch a flight. Code freeze is tomorrow, and code release is scheduled for next week. Why then, do some users wait until NOW to tell me about corrections and tweaks to reports? -- (...yes, a couple... even I am not perfect!) -- My answer; they just don't care until they're reminded of the code freeze and impending release. Procrastination at its finest!

It's a good thing I am using something as flexible and easy to modify as the BIRT Reporting Application. Changing things like column header names, some data type formatting, even script logic on various report elements is not a big deal (most of the time). This reminds me, that it is always a good thing to take the responsibility as a developer, to create a 'sign-off' check list. Trouble is, I HATE lists! But worse than that, I REALLY HATE being late to the Airport!

I think I'll create a check-list and post it here (later)... why not procrastinate? everyone else does!

Comments

Post a Comment

Popular posts from this blog

Image
Passing Parameters to a Scripted DataSet;or any DataSet for that matter The first time I heard the phrase "parameter binding to a data set" cold chills shot down my spine. I was thrust right back into my first OO Programming Class, where concepts like "pointers", "polymorphism" and others were thrown around like we were all just born to understand these abstract descriptions. Why not call it something simpler... like Parameter "place-holder" or "access point" ? Using the word "parameter binding" just makes it sound more complicated than it has to be. ...Maybe that's the idea? We are talking about nerdy techie types after all. That said, I will try to make sure I don't needlessly try to impress with my cryptic verbage. So, here it goes. If you are both new to BIRT and have to use a scripted source the way IBM’s Maximo implementations do, you might not know where to begin right off the bat. I will break it down into sm
Read more

Automating; the Good, the Bad, & the Ugly

So, when it comes to building a reporting solution why is it that users just want to "Automate" their already overly complex and convoluted Excel or Power Points? Almost every engagement requiring a "Report" seems to start out the same way. There are two primary trains of thought, the first is to "Get Everything" and the second is to "Automate Everything". Business Analyst say they want "everything" when they don't know exactly what a "Reporting Application" is or they don't know exactly what they want in a Report or Report Application. It's kind of like the General Contractor, who'll tell you he does "anything" when you contact him/her to build you a Deck or replace your Roof. Anytime I see ambiguity at this level, I question the understanding level of the individual making the claim or request. There are two tactics I find very helpful when faced with a request that seems to be less than well though
Read more