Week 1. Post 2.

 Today in the meeting, we worked on understanding Scrum and Scrum Development principles. Understanding the Scrum framework can get tricky because it forces me to get used to an entirely new structure of teamwork that I am not used to. There was no such thing as pair-programming, answering questions together in Google Docs like I used to do during teamwork assignments, and many other things. No longer could I split the work between my teammate and myself as "You work on the adding function, and I will work on the main function." The scrum team is self-organizing in that there is no overall team leader who decides which person will do which task or how a problem will be solved. It took me a lot of time to understand how this worked. It feels that you are now more independent about how you approach your tasks in the team, and nobody is controlling you. If I could do the teamwork assignments at school, I could get used to the Scrum framework. However, the question is - how do I make it happen?  

To make that happen, I realized I should spend more time trying to research the Scrum framework. I have learned that when I get introduced to something new to me, I get overwhelmed and start complaining about it instead of spending this time trying to tackle my comfort zone. So, I decided to read more about Scrum and even asked my mentor for some books. I skimmed through the book and realized it still feels overwhelming. I started thinking of how can I get more real-life insights and decided to read other people's feedback online about how they handle the Scrum framework setting at the workplace. After doing it, I started feeling much less overwhelmed, and I was surprised how my mindset changed as I started learning more and more about Scrum. I have realized that the more I know about the new topic - the more I feel comfortable, and the less I freak out. But most importantly, I have realized that what matters to me more is getting feedback from real people, and only in this way do I get a better understanding of things, and they start to make more sense to me. That is the strategy that I used to understand the Scrum framework better.