Why is it going to be late? There is, in fact, a technical explanation for this.
"Stuff happens."
As for "give me a specific date," that's about the worst thing you could possibly ask for. 99.973% of all bugs that you've ever experienced in any software that you've used have been the result of some yahoo announcing an arbitrary date, then insisting that the developers meet it no matter what. Predictably, what happens next is massive overtime, sleep deprived programmers (because you really want the code we write at 3 AM when we haven't slept in months), and ultimately a piece of software that was released way before it was ready. All because someone pulled a date out of his posterior and demanded that the software be shipped at that time.
The correct way to do this is to write the software and then, when you know it's done, announce the release date. Of course, hardly anyone can sell that to upper management because they want to create buzz in the marketplace. The fuzzy date that Kemper offered still causes more problems than it solves (no offense, guys), but at least they didn't pick an arbitrary date that's set in stone. "End of summer" is easily translated to "End of summer-ish" by most people, which gives them a little wiggle room.
In the software biz, if you want dates that are any more precise than that your best bet is to buy a Ouija board and burn some incense. This isn't an exact science, and the number of unknowns for even a modest software system are vastly greater than anyone but developers understand.
Not picking on you, of course. I just do this stuff for a living and periodically the insanity of how the business is run makes me want to find the nearest marketing guy and beat him senseless with a Nerf bat. Then I have another cup of coffee and go back to coding.