BuzzerBeater Forums

In rules we got something like this:
Schedule of Events:
# Tuesday: National Tournament/Scrimmage
# Thursday: Second National Tournament/Scrimmag
I booked a friendly game and date is 12/13/2007. And what about Tuesday scrimmage?

That's not a bug.

You can't schedule the 2nd scrimmage until after the 1st.

People who have arranged an scrimmage for this week, say the game it´s shown to be on Thrusday!!!
It should say is on Tuesday, as we got an extra friendly on that date, isn´t it??

Oh it’s just great how the BB team are working:/. One day in rules we got 2 scrimmage, and another we got only 1. Nice rules erasing. Sorry but this is rubbish.

That is correct, thursday:

12/13/2007 1:30:00 PM Zanarkand Abes Rbc TeaM - Set Orders SC

Oh it’s just great how the BB team are working:/. One day in rules we got 2 scrimmage, and another we got only 1. Nice rules erasing. Sorry but this is rubbish.

Calm down.

Everyone makes mistakes.

Calm down.

Everyone makes mistakes.

I never!
j/k

And then again, I'm getting back to my QA questions I put a while ago.
I understand this application is in an incipient stage, and you are trying to make it dynamic, make changes on the fly and such.
However, it is much better, and definitely recommended to go through a regular development cycle, set up a 1-2 week iteration, followed up by a QA stage (of course you will need a dev platform, then a QA platform, and only after that is the production one). As it stands, seeing how quick some things manage to get fixed, it looks like there process is not organized enough, and it's very dangerous to make changes without a proper QA approach. I am under the impression that the changes are being directly made in production environment, which can backfire...

I say this because in several cases I saw changes done in few hours after being reported. While that seems good, it is rather dangerous. Those bugs were indeed bugs, but they were not critical, nor blockers. Putting them in a regular life cycle would protect the application's health much better than having a display issue fixed right away.

Enough ranting, but hope you understand my point.

Feel free to contact me if you want further professional expertise ;)

Come on! Agile development is the way to go. Forget those M$ inspired cascade development cycles!

Early commits, continuous integration and quick release cycles, that's development in 2007!

Trust your techies, not the pointy haired managers!

/elboss

You know something, but not everything, the way you talk...
Agile development doesn't mean you don't have iterations. It just happens that we work Agile, and I do know how to integrate.

at first there was in the rules that there would be 2 scrimmages during this week.
Once I translated it, I saw a message that the rules changed and there now is only 1 scrimmage. (on thursday)

I liked the first better, but hey, it's the same for everyone.... except translators who now have to re-translate... ;þ

I guess it was to hard to change the way the scrimmage arrangement works at this time.
Now scrimmages can only be fixed between saturday and wednesdaynoon.
This probably conflicted with the fact the scrimmage would be sceduled on thuesday. Further would it be very difficult for teams to arrange an other scrimmage for thursday after the match from thuesday but before wednesday noon... So I guess the BB finaly decided to skip the extra scrimmage on thuesday, and leave things as they where in order to avoid chances for bugs and all kinds of other bad things that would probably happen.

I'm absolutely not sure if it happened this way, but I think it's a fair guess. Any BB feel free to tell us otherwise. ;)