Showing posts with label Master. Show all posts
Showing posts with label Master. Show all posts

Tuesday, 23 October 2012

How to Become a Scrum Master

Step 1. Get knowledge of another methodology
It may seem unusual when I say that it is just as important to understand the world without scrum, as it is to understand how scrum has changed the world. The reason I say this, is that to really appreciate the benefits of any methodology or framework it is very important to understand the pitfalls (and benefits) of other methods.
Step 2. Get scrum project experience and reassess your values
After gaining solid project knowledge in at least one other methodology you should have a good basis on which to compare to other methodologies. I recommend getting a copy of "the scrum guide" by Ken Schwaber and Jeff Sutherland, reading it thoroughly and then enquiring after project experience within your department, organisation or other organisation.
Step 3. Become a certified CSM
After you have an understanding of a methodology other than scrum, and you have also lived and breathed scrum for a while (I recommend six months to a year, but it all depends on your aptitude), the next step is to become a Certified Scrum Master (CSM). On this course you will be given an overview of the rules, get to ask the trainer questions and finally you will be tested on what you have learned. There are numerous organisations that offer this certification but I recommend the Scrum Alliance CSM Course.
Step 4. Put your certification into practice
As you may already know, the best way to get yourself a new role or job is to demonstrate that you already have experience in it. Having done a course leaves you in an excellent position to apply your knowledge. You can suggest practices in debates and speak to your line manager about the benefits of implementing them. If your team is already doing the practices, you will often find that the rules are not followed when the going gets tough. However, this is precisely when the methodology should be most powerful in controlling chaos. Therefore, you can help to explain the benefits of maintaining the rules.
Step 5. Get a voluntary leadership role
Although the role of is not about authority or management of people, there certainly is a strong element of leadership of people and management of the framework. I suggest showing your manager that you are interested in a technical or non technical leadership role.
Step 6. Get a scrum master role
Once you have proven to yourself that you fully understand the rules, you are ready to facilitate a team and can play the part of "servant leader", you are then ready to go and get that role! At the time of writing this text, scrum is the de facto standard methodology for software development projects and is fast moving into non software development projects. I listed my CV on jobs sites so that the interested parties came to me, but also rang agencies directly.
Step 7. Stick to the rules
The seventh step is for some people the most difficult to carry out, and no example can make it easier. After having learned the rules, you will now need to make sure that regardless of the characters you meet, the deadlines imposed by an ambitious business client or the reluctance of the individuals you meet, you continue to maintain the simple rules. Believe me when I tell you that many have tried and failed to do this. However, if I have done it, you can too!



Tuesday, 28 August 2012

What Is a Scrum Master?

The scrum master's purpose is to understand the scrum rules and practices, remove any impediments or blockers to the team delivering and to help the team to understand how to self organise and work in a scrum manner. The scrum master facilitates for the scrum team wherever it makes sense to do so. The scrum master is your go-to guy in terms of how the scrum framework should operate, and this applies to anyone in the organization.
The scrum master usually understands how to aid the product owner in maximising return on investment from the business and he helps the team to work together to be as productive as humanly possible and deliver a shippable increment of the product.
A scrum master should understand the rules of scrum to an expert level. This means that anyone in the organisation and any stakeholder should be able to rely on the scrum master for advice on the framework. It requires the ability to coach, mentor and build relationships with people at all levels of business. The role often requires a great deal of confidence and strength. This is because others may not share the experiences or beliefs of the scrum master and therefore they must often be convinced that scrum's practices will solve their issues. This is why influence, persuasion and leading by example are such important traits for scrum masters. A scrum master is a coach to the scrum team, and therefore strong interpersonal skills are necessary. The team should feel comfortable explaining any issues and the scrum master should be happy to help even on the busiest of days.
The relationship with the product owner is just as important as the relationship with the team. The ability to understand how to assist, motivate and coach the product owner can turn projects around. For this reason, one will need to understand the personal characteristics of the product owner as well as what scrum requires of him.
A traditional project manager often performs the role of scrum master. This can have both pros and cons. In this role we manage the framework without managing the people. However, traditional project managers may be from the "command and control" background, which is averse to the belief in "self-organizing teams". Therefore, I suggest that any candidate should be ready to embrace and see the value in this new way of thinking. To be fair, many of the best non-scrum project managers I have worked with made their name by empowering teams of experts to make decisions and knowing how to manage the process. Good traditional project managers usually have the key interpersonal and process management skills that all projects can benefit from.
Prior technical or product domain experience is a strong plus since there are often situations that require you to empathise with the team and help them to solve problems. For example, experience in solving common problems such as setting up databases, breaking down large problems into small ones or just plain keeping solutions simple in the first place. This experience also helps the team, since the person in this role can often explain technical issues to the product owner and stakeholders without involving the team, hence leaving them to get on with the work.



Monday, 27 August 2012

What Is a Scrum Master?

The scrum master's purpose is to understand the scrum rules and practices, remove any impediments or blockers to the team delivering and to help the team to understand how to self organise and work in a scrum manner. The scrum master facilitates for the scrum team wherever it makes sense to do so. The scrum master is your go-to guy in terms of how the scrum framework should operate, and this applies to anyone in the organization.
The scrum master usually understands how to aid the product owner in maximising return on investment from the business and he helps the team to work together to be as productive as humanly possible and deliver a shippable increment of the product.
A scrum master should understand the rules of scrum to an expert level. This means that anyone in the organisation and any stakeholder should be able to rely on the scrum master for advice on the framework. It requires the ability to coach, mentor and build relationships with people at all levels of business. The role often requires a great deal of confidence and strength. This is because others may not share the experiences or beliefs of the scrum master and therefore they must often be convinced that scrum's practices will solve their issues. This is why influence, persuasion and leading by example are such important traits for scrum masters. A scrum master is a coach to the scrum team, and therefore strong interpersonal skills are necessary. The team should feel comfortable explaining any issues and the scrum master should be happy to help even on the busiest of days.
The relationship with the product owner is just as important as the relationship with the team. The ability to understand how to assist, motivate and coach the product owner can turn projects around. For this reason, one will need to understand the personal characteristics of the product owner as well as what scrum requires of him.
A traditional project manager often performs the role of scrum master. This can have both pros and cons. In this role we manage the framework without managing the people. However, traditional project managers may be from the "command and control" background, which is averse to the belief in "self-organizing teams". Therefore, I suggest that any candidate should be ready to embrace and see the value in this new way of thinking. To be fair, many of the best non-scrum project managers I have worked with made their name by empowering teams of experts to make decisions and knowing how to manage the process. Good traditional project managers usually have the key interpersonal and process management skills that all projects can benefit from.
Prior technical or product domain experience is a strong plus since there are often situations that require you to empathise with the team and help them to solve problems. For example, experience in solving common problems such as setting up databases, breaking down large problems into small ones or just plain keeping solutions simple in the first place. This experience also helps the team, since the person in this role can often explain technical issues to the product owner and stakeholders without involving the team, hence leaving them to get on with the work.