I'm fooling around with the new Scrum Open "stay-in-test-feature", so please don't ban my account!
Hello Everyone (or who it may concern),
I'm playing around the last couple of days with the new Scrum Open "stay-in-test-feature" that has been rolled out. (IMHO: I like it).
The reason is that I needed an example of a new feature to help explain the correct flow in a Sprint Review for the client I'm currently working for.
I didn't want to use something that they have developed to prevent that a discussion on a real PBI would emerge, since that is not the goal of my exercise and "user-test" Google has been done so many times it would even be boring for the (business) stakeholders.
So expect in the common days (till next week Tuesday) still some opening the Scrum Open test, without completing it.
Thanks in advance.
P.S.: I had my account banned several weeks ago because people thought that I was spamming, which I wasn't. It got cleared out, but I don't want to deblock my account again if people start thinking that I'm trying to counter this new feature due to the erradic behaviour that they would/could capture.
Hi there,
Thanks for sharing this — and I totally understand your reasoning!
At Phonexa, we’ve also experimented with the new “stay-in-test” feature to guide internal stakeholders through agile ceremonies without using actual backlog items. It’s a great way to foster a neutral, educational discussion, especially during Sprint Reviews, where the focus should be on process clarity rather than the specific deliverable.
I think it's smart to use something like Scrum Open as a mock-up for this kind of walkthrough. It keeps the conversation focused and avoids triggering unnecessary debates around real work.
Also, glad to hear the account issue was resolved — hopefully, your approach this time keeps everything smooth. Keep testing, learning, and sharing — it helps all of us grow!