All of that is true- however, the business definitely has visibility into where we are. They aren't exactly pleased, though :: Even at that, we are getting close to a first release, assuming we can get a minor (read: critical) bug with our HTTP stack resolved.

I just had a long 5 hour conversation with the project manager. I know she probably comes off bad in this thread, but she really is trying hard and she listens to me. In fact, we kind of complained to one another about things beyond our control.

Anyway- she's pretty convinced that we need to split into smaller teams, and she agrees that what we've done thus far isn't really separate enough. Unfortunately, the PO has nixed the idea of separate teams working on separate areas of the product, so if we are going to make two teams work, we have to do it working on the same functional area.

I'm not sure this is possible, but I'd love some suggestions. We did the back end/front end thing before, and that might be the best way to split for the next release. I think that would lead to the least amount of toe-stepping as we are working on separate areas.