Use Herogami for a successful Scrum experience (part 1)

Under the right conditions Scrum can be a tremendous success story, but it often requires hard work to get there. For new Scrum teams it means learning to fundamentally work very differently than they are used to, such as relying on a lot more collaboration, making and delivering on shared commitments and building a high degree of trust. For existing Scrum teams it means constantly renewing the team commitment to each other, the cause, and to the Scrum framework.

This includes the rather painful practice of revisiting the fundamentals and ensuring any deviations from accepted processes or practices were for the right reasons and had the right results. To have a chance at achieving high performance a new-to-Scrum team will not only need to just change their processes, but fundamentally change the culture and behavior of the team and all of the supporting roles (that includes their leadership).

Meanwhile, a mature or well-established team should never assume they are high performance; they should always be checking (and rechecking) that they are still living the Agile values. Needless to say this can become an extremely complex challenge! To be absolutely clear, I’m not proposing there is a single formula or recipe that works, but I do believe certain criteria can dramatically improve your Scrum team’s chances of success. To that end here are 10 tips (plus a bonus) that may help you focus your efforts towards building a successful Scrum team and experience.

One of aspects of a successful Scrum-driven project is having the right number or team members and well defined roles.

Currently the Scrum Guide recommends that Scrum teams will work best with three to nine people, not including the Scrum Master and Product Owner.  Enter your project dashboard, scroll down to Team Member and clic on the Add button to start adding people to your project. If you run out of users, Herogami provides you with a shortcut to create a new user and have it allocated immediately to the project team.

Herogami provides you with four team roles on your project, all with different privileges, roles and visibility on the project content.

Owner: that’s the product owner (and often the Scrum Master too) which controls the project

Developer: a developer consumes stories or issues and creates them as well

Tester: you can identify a given member as a tester too

Guest: this user will only see public content of the project, aka every single item on Herogami, from stories to issues, from documents to wiki articles and even calendar events can be marked as private. As such, only the team members see them, therefore they are invisible to guests.

Having issues marked as private and being therefore invisibile to guest members provides lots of advantages. First and foremost you give your team the ability to track every critical aspect of the project, every complex story and especially complex or blocking issues on Herogami without guests knowing about it.

In a scenario where the development team invites a few people from the customer’s staff and register them as guests, the benefits are obvious: the team handles the most internal issues by keeping them private and let their customer focus on highly visibile ones.

Grumpy Herogami, Architect

26 Sep 2016