It seems to me the ranter doesn't get that RIM doesn't care about having a mass of junk apps which are usually the result of have a low bar for entry into the app store. Not to say their app store for their phones is amazing (I own a BB Torch that I do love), but RIM is mostly targeting big business and government where when they need an app that's not already part of the system, they want something that works well (well enough if we are talking government) and are willing to pay a significant amount.

Also complaining about all the forms ignores that RIM has to deal with a bunch of export controls because of the encryption algorithms used in their software. While I'm not 100% sure, I do believe that they are required by law to have you put in all of your information for each download. Which is why they ask for all of your information every time you download a new OS image for their phones as well.

I do hope however that they make their development process a bit more streamlined, but I won't be sad if I don't end up seeing 1000 tetris clones or hundreds of other mindless games.

I am still holding off on a tablet purchase until I see the PlayBook alongside the upcoming Android tablet. I've already decided against the iPad after having used my friends' iPads.

My project has a team of about 40 people including people who develop and write our requirements, developers, integration testers, quality assurance testers, and various managers.
We use DOORS for formal documentation including requirements, high level design documents, and manuals. We use Visio to make UML diagrams for detailed design. We use ProcessMax to track defects in code (found by the integration test team or the QA test team), problems requirements, problems with other formal documentation, and to track the results of code peer reviews.

I've been using these tools for about 8 years now and so far they seem to work well for our team. Other teams in our division also use these tools. The only negative is that if I had my way we would use a better tool to generate UML.Our management doesn't see the need for that since the UML usually never leaves the development team and is not included in the formal documentation package we give to QA.

Good luck in finding a solution for your needs!

I'd seriously like to get my time back after having read the review and then some of the excerpts from the book. I think I lost some IQ points after having read this.