Often mentioned in my articles
Dec 7, 2023 5:20:38 GMT
Post by account_disabled on Dec 7, 2023 5:20:38 GMT
Many people think that a Scrum Master does nothing at work and his duties include drinking coffee and playing FIFA nothing could be further from the truth. Before I started my internship I read the Scrum Guide carefully several times watched many videos on YT and read articles found on the Internet e.g. on this blog. I thought I knew everything. However during the first Daily I was shocked! The IT slang exceeded my expectations about this job. Merges implementations backends and other frontends were completely new to me. This is the first thing that completely surprised me and was difficult to understand.
However at the next Daily I sat down with a piece of paper and started writing down what I didn't understand. It helped! I googled some things and asked my friends about others. Some people said that I don't need to know what the technical side is about but it's worth Email Marketing List understanding what the team is talking about and how you can help them. Technical vocabulary is one of the most difficult things that caused me a person starting to work in IT a lot of stress. Another thing goes back to what is described in the Scrum.
Guide Scrum is • lightweight • easy to understand • difficult to master. And I would like to focus on the last point. I had my first Daily with a team that is very well organized and knows the rules of working in Scrum. In such a case you don't even need to know the rules well because the team knows what to do and what its work should look like. However working with such a team I wouldn't learn much. The real challenge came when I started working with a group where Scrum had to be introduced.
However at the next Daily I sat down with a piece of paper and started writing down what I didn't understand. It helped! I googled some things and asked my friends about others. Some people said that I don't need to know what the technical side is about but it's worth Email Marketing List understanding what the team is talking about and how you can help them. Technical vocabulary is one of the most difficult things that caused me a person starting to work in IT a lot of stress. Another thing goes back to what is described in the Scrum.
Guide Scrum is • lightweight • easy to understand • difficult to master. And I would like to focus on the last point. I had my first Daily with a team that is very well organized and knows the rules of working in Scrum. In such a case you don't even need to know the rules well because the team knows what to do and what its work should look like. However working with such a team I wouldn't learn much. The real challenge came when I started working with a group where Scrum had to be introduced.