How I become Scrum master in company ?

2 Comments

1. 

   Jossy Chinedu Ibe PRINCE2, ITIL 4, CSA 4 years ago
   You need to look for a company who is willing to hire you and agree to trained you. If you look at the Scrum Master as being the coach of both the Product Owner and the Dev-Team. The Product Owner must blindly trust the team to build the thing the right way, but the Scrum Master needs to coach them on this. You cannot coach Agile software development if you have never experienced it yourself while being knee-deep in with the team. Most Certified Scrum Masters still lack experience with technical skills and practices. Even if they do understand their importance, they likely lack the credibility to convince their team. Coaching only the process. In other words, when you are slow in making changes to your product, then it doesn’t matter how you structure your teams, your organisation or what framework you adopt, you will be slow to respond to changes. Most Scrum Masters with a project management background will have to trust the development team that they keep the cost of change on the product low. Time told me that most developers have no experience how to really achieve this. Most developers just think it is their job to make it work, not making sure the code is adaptable over time. Finding the balance of what you need now versus what you might need in the future is hard, certainly if you want to make sure your product is able to respond to change today. Your team will need someone to coach the balance between making it work and good technical excellence practices, minimizing the technical debt they create. While making sure the Product Owner understands the importance of these practices to minimize wrong discussions around this topic. A perfect Scrum Master is someone who understands the balance between structural, process and functional quality while keeping the Agile values and principles in mind. Combined with work-experience within an Agile team. Therefore, I would advise you TO start perfecting your skills in these areas: • Structural quality: why working close with the development team. Understanding the importance of code quality. While having a test-first mindset can help you get started with practices like TDD. Hopefully having enough credibility to introduce and motivate Clean Code to team. Preventing rigid application. • Process quality: working in a full software process life-cycle. Going from feature requests till delivery. Being able to communicate with stakeholders, developers, product owners and managers on their own level. Understanding the need of a “A repeatable development process that reliably delivers quality software” • Functional quality: You need to shift your mindset from building features to a user-centric business view. This will help you understand the core functionality. Hopefully it will help you to find the 20% of features that deliver 80% of the value.
   +6 Reply Upvote post

2. 

   Andrej Studencan 4 years ago
   Hi Ivan...sometimes you don't have to have the role of a Scrum Master to be one... I suggest, initiate some simple agile project in your company. Put down some ideas for improvement of your environment, automation of work, scripting, developing of simple new features... make backlog out of that... tell your company you want to work on this with your team of 3-4 people... have company prioritize ideas.... be one of the developers but try to lead the process to be agile scrum (according to your knowledge)...learn from mistakes...do retrospective...do it better.... it might not be a risky project with much attention....but it counts as when to build your skills and experience...and what is more, you show your company you're pro-active...;)
   +6 Reply Upvote post