Scrum Team - Deal with Crossfunctionality

-
Do you have a crosssfunctional Scrum Team? How many different Specialist do you have? Are they all "cross" enough to act and deal with all the work that accrues?

Yes!
Great. You should be happy and stop reading this post and use your time to produce some value.



No?
Then I recommend to read further. Maybe I have some Ideas to deal with this challenging situation.



According to the Scrum Guide we have only one role in the team. The Dev role. But this role faces a lot of different skills.
- writing User Stories (if the PO delegates it)
- communication with customers
- full stack developer skills
- Testautomation skills
- Testmanagement skills
- Operation skills
- Support skills
- ...
Maybe there are other things. But let us be honest. Do you know someone who could cover all this skills in a professional level. Then please give me the contact coordinates I have a employment for her/him. ;-)
Because of the situation above we have different professionals in our teams. So what do we do to not fall back in to a classical waterfall, where the requirements engineeer writes the stories, some developers are programming and afterwards your tester is in charge to save the quality.
If each professional discipline knows something about the disciplines at left and right hand, we getting much more flexible in working out of the backlog. It is not possible to define or plan the exact amount of work for each discipline. If we do not learn from others, we working on items with lower prio or even on items not in the backlog, just because we wanna not bore out.
With T-Shaped people, flow can arise. The team begins to perform and learn a lot. If the team is stable for a while, they can perform even better, because they learn from other disciplines.
Key values for such a culture are:
- eager to learn
- fail fast, learn fast
- commitment
- focus on customer value
- ...


To increase this, the employees can learn the business domaine well. In this case they can judge the value for customer even better and come up with new ideas for the product. The customer is even more satisfied, when the Scrum Team talk in customer language.
Such employess are + - shaped. Specialist in one discipline and business domaine, able to work with neighbour discipline very well.

What is your opinion to that?
Let us discuss.

Kommentare

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

ScrumMaster - ThatMatters - Team

-
Bild
ScrumMaster - ThatMatters The ScrumMasters Job is to develop the Team so they can deliver maximal value. This is coupled to good quality and people oriented leadership. We do not squize out the juice out of one orange, we wanna grow up an orange tree, where we can get much of juice from it and which is sustainable. To do so, we have to consider a lot of habits and methods. Some of them are described in the following table. If you have any other ideas, please help me to get this more complete. Picture Description As ScrumMaster you live in many different leadership roles  ( 8 Stances of a ScrumMaster ).  The most important thing is to claim to help others become better. This can be done as a coach, mentor, teacher, etc. It is important to recognize in which status ( ShuHaRi ) the team and the individual members are . Active and well-managed retrospectives are a very effective means of improving the team (and also the organization). The impediments mus...
Mehr anzeigen

ScrumMaster - ThatMatters

-
Bild
Hi ScrumMaster's Have you ever ask yourself what really matters for your Job? Where you should have Focus on? What is expected from this role? I have made some experience I would like to share with you. This experience are based on my own work with different teams, but also from books like Scrum Mastery from Geoff Watts, Whitepapers from Barry Overeem and other inspiring articels on the web. My way to Certified Scrum Professional did also have Impact to this. Maybe there are some ideas you can benefit from. Idea Proportions in the following picture are not choosen at random. You-Team-Organization-Community. In this order I see the responsibility in the role of a ScrumMaster. You have to be ready for this Job, then you can bring your Team to success and out of your success you can help the organization to become better in agility. After all, the community is thankful, if you share your experience with others, so the agile movement can grow. You  - ScrumMaster is in...
Mehr anzeigen

Scrum Master - Vacuum Cleaner of the Team?

-
Der Scrum Master wird als servant leader beschrieben. Was man darunter versteht schreibt Shreedhar Koganti sehr schön in seinem Blog  auf der Scrum Alliance Member Ship Seite. Häufig wird der SM auch als Beschützer des Teams tituliert. Beide Bezeichnungen können dazu verleiten zu sagen, der SM sollte das Team auch vor unschönen Aufgaben schützen. Wenn es darum geht den Betrieb aufrecht zu erhalten eingehende Tickets zu analysieren, unbequeme Meetings zu besuchen, das Team zu vertreten oder Bugs analysieren wird häufig der SM vorgeschoben, weil er ja das Team beschützen muss. Wenn man diese Arbeiten kommentarlos erledigt hilft man dem Team nicht wirklich weiter. Die Verantwortung für alle aufgezählten Arbeiten liegt nämlich beim Team. Sehr gerne schiebt man den SM vor, weil er vielleicht schon die Beziehungen hat, sich auskennt oder sonst eine Affinität für solche Dinge hat. Manchmal kommt man sich vor wie ein Staubsauger, der hinter dem Team noch den aufgewirbelten Staub berein...
Mehr anzeigen