<\/strong><\/h3>\nScrum\u2019s foundation \u2013 roles and Scrum ceremonies<\/strong><\/h3>\nScrum is in no way a complicated model. First of all, its key element is effective role differentiation between the Scrum Master, Product Owner and development team. Another key factor is the six Scrum ceremonies.<\/p>\n
Scrum\u2019s six ceremonies:<\/strong><\/p>\n\n- Daily Scrum<\/li>\n
- Sprint Planning<\/li>\n
- Sprint Review<\/li>\n
- Sprint Demo<\/li>\n
- Retrospective<\/li>\n
- Backlog Grooming\/Refinement<\/li>\n<\/ul>\n
\nIf role differentiation and the ceremonies have been executed properly, Scrum is very difficult to screw up.<\/p>\n<\/blockquote>\n
<\/strong><\/h3>\nBalance between ceremonies is important!<\/strong><\/h3>\nAlthough a top-notch Scrum requires many other things, if the role differentiation and ceremonies have been executed properly, Scrum is very difficult to screw up. Unfortunately, we Contibyte trainers have frequently noted problems in the balance between Scrum ceremonies. We often face situations where teams in an organization we are training arrange some ceremonies extremely well, but seriously neglect others.<\/p>\n
<\/strong><\/h3>\nT<\/strong>rain with Contribyte \u2013 achieving a good Scrum is like bodybuilding!<\/strong><\/h3>\nA good bodybuilder shapes their body like a sculpture \u2013 if some muscles are too small, they focus on training and growing them in particular. In this way, the body can be shaped into a balanced whole. We should think about Scrum skills in the same way. If a certain Scrum ceremony is in poorer shape than others, focus on improving that particular ceremony!<\/p>\n
<\/strong><\/h3>\n5 minutes retro is enough for us \u2013 because we are already a perfect team<\/strong><\/h3>\nSome reader or other is probably swearing under their breath, thinking that they do not need all six Scrum ceremonies or can combine them without losing anything. In the near future, we plan to write blogs about the most frequently recurring mistakes in each Scrum ceremony. Stay tuned!<\/p>\n
<\/p>\n
![\"scrum-seremonia\"](\"https:\/\/b845811.smushcdn.com\/845811\/wp-content\/uploads\/2019\/12\/AdobeStock_209099836-300x200.jpeg?lossy=1&strip=1&webp=1\")
<\/h3>\n
<\/p>\n
Which is the most important Scrum ceremony? \u2013 Contribyte\u2019s view<\/strong><\/h3>\nBut let\u2019s return to the balance between ceremonies. We conducted a quick survey among Contribyte trainers: What is the ceremonies\u2019 order of importance? We found that even we have different opinions about this. Some trainers thought that all ceremonies are equally important, while others rated some ceremonies more highly. Contribyte places the Scrum ceremonies in the following order of importance:<\/p>\n
Important but often neglected ceremonies:<\/strong><\/p>\n\n- Demo<\/li>\n
- Grooming<\/li>\n
- Retro<\/li>\n<\/ul>\n
Also important but generally much better executed ceremonies:<\/strong><\/p>\n\n- Daily<\/li>\n
- Planning<\/li>\n
- Review<\/li>\n<\/ul>\n
I think the result is affected by the fact that we tend to see major defects in demo, grooming and retro in particular. Teams often execute daily, planning and sprint review much better. That why most of our trainers emphasize demo, grooming and retro.<\/p>\n
\u00a0<\/span><\/p>\n![\"scrum-seremonia\"](\"https:\/\/b845811.smushcdn.com\/845811\/wp-content\/uploads\/2019\/12\/AdobeStock_205853629-1-300x200.jpeg?lossy=1&strip=1&webp=1\")
<\/p>\n
<\/p>\n
External feedback on demo<\/strong><\/h3>\nAnother reason why we rank demo and retro so highly is the fact that these ceremonies, in particular, provide the team with an important feedback mechanism. Additionally, demo is the only ceremony in which it is realistically possible to obtain feedback from the team\u2019s external stakeholders.<\/p>\n
<\/strong><\/h3>\nDo not repeat your mistakes \u2013 seek better practices!<\/strong><\/h3>\n\nIt is important to keep Scrum ceremonies in balance!<\/p>\n<\/blockquote>\n
In retrospect, a team will wonder: \u201cWhat are we doing or have we done \u2013 did it work well?\u201d \u201cWould another approach be better?\u201d \u201cWould we act in the same way next time?\u201d When demo and retro are executed well, they guide the team\u2019s work in the right and optimal direction at all times. If you do not invest enough in these ceremonies, you will leave a great deal of your team\u2019s potential unused!<\/p>\n
And now we come to the heart of the matter! It is important to keep Scrum ceremonies in balance! If three of the ceremonies are well executed, but the other three are neglected, there will be no room to develop Scrum properly! Surely you do not want a Scrum bodybuilder who skips leg days?<\/p>\n
<\/strong><\/h3>\nThe key Scrum ceremony is that in which you are weakest!<\/strong><\/h3>\nBy now, the reader will be aware that the key Scrum ceremony is the one in which your team is weakest. For example, there is no need to develop sprint planning if backlog grooming is still in its infancy. Development ideas must be directed towards the ceremonies in need of most improvement.<\/p>\n
On average, we have noticed that grooming of backlog, demo and retros leave most room for improvement. Grooming of backlog improves backlog\u2019s quality and the team\u2019s analytical skills. Demo works as a direction-giving feedback session in terms of the results. Retrospective fixes pain points and increases the team\u2019s learning speed. There is often much room for improvement in these ceremonies because teams find it easier to concentrate on the other three: daily, planning and review. This may be because the other three are easier to execute. That is still not a very valid reason for neglecting Scrum\u2019s three key ceremonies.\u00a0<\/span><\/p>\n<\/strong><\/h3>\nIf you do not know which ceremony you are weakest at, ask us for help<\/strong><\/h3>\nDo you know which of your ceremonies are in bad shape or \u2018resemble a wet rag\u2019? This is easy to define with an external assessment, which at its lightest can be a Contribyte online survey, or if needed a full\u00a0360-degree feedback<\/a> at team-level. Naturally, you can also ponder amongst yourselves which ceremonies work better than others. An external assessment is still a quick and easy way of identifying the sticking point quickly and easily, and improving everyone\u2019s buy-ins.\u00a0Contact us<\/a>\u00a0and ask more about different options!<\/p>\n <\/p>\n
\n
Scrum is in no way a complicated model. First of all, its key element is effective role differentiation between the Scrum Master, Product Owner and development team. Another key factor is the six Scrum ceremonies.<\/p>\n
Scrum\u2019s six ceremonies:<\/strong><\/p>\n If role differentiation and the ceremonies have been executed properly, Scrum is very difficult to screw up.<\/p>\n<\/blockquote>\n Although a top-notch Scrum requires many other things, if the role differentiation and ceremonies have been executed properly, Scrum is very difficult to screw up. Unfortunately, we Contibyte trainers have frequently noted problems in the balance between Scrum ceremonies. We often face situations where teams in an organization we are training arrange some ceremonies extremely well, but seriously neglect others.<\/p>\n A good bodybuilder shapes their body like a sculpture \u2013 if some muscles are too small, they focus on training and growing them in particular. In this way, the body can be shaped into a balanced whole. We should think about Scrum skills in the same way. If a certain Scrum ceremony is in poorer shape than others, focus on improving that particular ceremony!<\/p>\n Some reader or other is probably swearing under their breath, thinking that they do not need all six Scrum ceremonies or can combine them without losing anything. In the near future, we plan to write blogs about the most frequently recurring mistakes in each Scrum ceremony. Stay tuned!<\/p>\n <\/p>\n <\/p>\n But let\u2019s return to the balance between ceremonies. We conducted a quick survey among Contribyte trainers: What is the ceremonies\u2019 order of importance? We found that even we have different opinions about this. Some trainers thought that all ceremonies are equally important, while others rated some ceremonies more highly. Contribyte places the Scrum ceremonies in the following order of importance:<\/p>\n Important but often neglected ceremonies:<\/strong><\/p>\n Also important but generally much better executed ceremonies:<\/strong><\/p>\n I think the result is affected by the fact that we tend to see major defects in demo, grooming and retro in particular. Teams often execute daily, planning and sprint review much better. That why most of our trainers emphasize demo, grooming and retro.<\/p>\n \u00a0<\/span><\/p>\n <\/p>\n Another reason why we rank demo and retro so highly is the fact that these ceremonies, in particular, provide the team with an important feedback mechanism. Additionally, demo is the only ceremony in which it is realistically possible to obtain feedback from the team\u2019s external stakeholders.<\/p>\n It is important to keep Scrum ceremonies in balance!<\/p>\n<\/blockquote>\n In retrospect, a team will wonder: \u201cWhat are we doing or have we done \u2013 did it work well?\u201d \u201cWould another approach be better?\u201d \u201cWould we act in the same way next time?\u201d When demo and retro are executed well, they guide the team\u2019s work in the right and optimal direction at all times. If you do not invest enough in these ceremonies, you will leave a great deal of your team\u2019s potential unused!<\/p>\n And now we come to the heart of the matter! It is important to keep Scrum ceremonies in balance! If three of the ceremonies are well executed, but the other three are neglected, there will be no room to develop Scrum properly! Surely you do not want a Scrum bodybuilder who skips leg days?<\/p>\n By now, the reader will be aware that the key Scrum ceremony is the one in which your team is weakest. For example, there is no need to develop sprint planning if backlog grooming is still in its infancy. Development ideas must be directed towards the ceremonies in need of most improvement.<\/p>\n On average, we have noticed that grooming of backlog, demo and retros leave most room for improvement. Grooming of backlog improves backlog\u2019s quality and the team\u2019s analytical skills. Demo works as a direction-giving feedback session in terms of the results. Retrospective fixes pain points and increases the team\u2019s learning speed. There is often much room for improvement in these ceremonies because teams find it easier to concentrate on the other three: daily, planning and review. This may be because the other three are easier to execute. That is still not a very valid reason for neglecting Scrum\u2019s three key ceremonies.\u00a0<\/span><\/p>\n Do you know which of your ceremonies are in bad shape or \u2018resemble a wet rag\u2019? This is easy to define with an external assessment, which at its lightest can be a Contribyte online survey, or if needed a full\u00a0360-degree feedback<\/a> at team-level. Naturally, you can also ponder amongst yourselves which ceremonies work better than others. An external assessment is still a quick and easy way of identifying the sticking point quickly and easily, and improving everyone\u2019s buy-ins.\u00a0Contact us<\/a>\u00a0and ask more about different options!<\/p>\n <\/p>\n\n
\n
<\/strong><\/h3>\n
Balance between ceremonies is important!<\/strong><\/h3>\n
<\/strong><\/h3>\n
T<\/strong>rain with Contribyte \u2013 achieving a good Scrum is like bodybuilding!<\/strong><\/h3>\n
<\/strong><\/h3>\n
5 minutes retro is enough for us \u2013 because we are already a perfect team<\/strong><\/h3>\n
<\/h3>\nWhich is the most important Scrum ceremony? \u2013 Contribyte\u2019s view<\/strong><\/h3>\n
\n
\n
<\/p>\nExternal feedback on demo<\/strong><\/h3>\n
<\/strong><\/h3>\n
Do not repeat your mistakes \u2013 seek better practices!<\/strong><\/h3>\n
\n
<\/strong><\/h3>\n
The key Scrum ceremony is that in which you are weakest!<\/strong><\/h3>\n
<\/strong><\/h3>\n
If you do not know which ceremony you are weakest at, ask us for help<\/strong><\/h3>\n