Comments (7)

Hi Åsa,

Thanks for your feedback. We have tested the user interface in a public beta with approximately 4500 users for several months before release. All users were invited to join the beta/customer preview through a link on the start page of the system.

Are you experiencing problems?

Best regards,
Karolina

Hi!

Attached please find some issues I have noticed. Hope you get what I mean and that this can help you.

Best regards,

/Åsa
0703-32 03 09

Från: Projectplace Ideas [mailto:karolinaj@projectplace.com]
Skickat: den 20 juni 2012 08:58
Till: Normelli Åsa
Ämne: [Projectplace] New comment

Hello,

A new comment has been posted by Karolina Wicksén Jackson-Ward on the idea "Test properly before deploy":

You can reply to this email to comment the idea too.

You can view the details at http://ideas.projectplace.com/feedbacks/98284-test-proper...;

Thank you!

Hello Karolina

In my humble opinion, the fact that you had a public beta w/ 4500 users several months before release doesn't excuse the bugs that exists upon release.

In my opinion, one big part of a public beta is for YOU to find problems before the release. For example you could use a beta program in order to find any bugs or design flaws that you haven't found internally when you finished your internal testing. But this require a good way to (automatically) log and follow up errors that occured. It also requires the right people in the beta program. If, for example, the beta program is only populated by people that doesn't report bugs, then the reason for the beta program is lot less.

Me, for example, didn't sign up for the beta program for two reasons. First, there were no information about the possibilities to switch back from the beta. And since there were no guarantees that I could switch back I didn't dare since I use Projectplace as a production tool and any problems I found could potentially make me less productive.

Just to sum up what I believe.

  • The beta program shoudn't start before you have finished your internal testing (for bugs, design problems is sometimes only possible to find in a public beta).
  • Automate a way to actually get all possible errors from the users (the server side bugs should be very easy to log, and I'm sure you could figure out ways to get some of the client side bugs as well).
  • Provide a way to sign out of the beta program.
  • Give an incentive for the people in the beta to actually help you. For instance, give a months credit for a user who reports a confirmed bug.

This is just my two cents, but I have to agree with Åsa, in that this does not feel like a well tested release.

Hi Tobias,

I agree that a beta can not be a replacement for internal testing and it has not been used as such.

We have server side logging and there was a super easy feedback tab to use for giving opinion and reporting problems.

All users could go back to the old look with a single click in the interface.

We received around 470 feedback messages during the customer preview and we have thanked all the people who participated.

Hi,

I enclose it again as I have a meeting shortly.

Mvh
/Åsa
0703-32 03 09

Från: Projectplace Ideas [mailto:karolinaj@projectplace.com]
Skickat: den 20 juni 2012 11:29
Till: Normelli Åsa
Ämne: [Projectplace] New comment

Hello,

A new comment has been posted by Karolina Wicksén Jackson-Ward on the idea "Test properly before deploy":

You can reply to this email to comment the idea too.

You can view the details at http://ideas.projectplace.com/feedbacks/98284-test-proper...;

Thank you!

DIMELO - social media platform editor