Skip to main content

Ask yourself, Are you a Scrum Master ???

A scrum master can make or break an agile transformation. Often asked what is the role of a conductor in an orchestra. Answer is simple (as once explained by Jobs). Members are good at playing their instruments. But the conductor plays the orchestra. So be careful when you are the scrum master.

What you are supposed to do;

  1. A Servant Leader : empathetic listener and healer. This self-aware steward is committed to the growth of people. 
  2. A Coach can coach the other team members on how to use Scrum in the most effective manner.  Also to coach the PO and organization.
  3. The Framework Champion is an expert on how Scrum works and how to apply it. 
  4. The Problem Solver protects the team from organizational disruptions or internal distractions or helps remove them. 
  5. The Facilitator is a neutral participant who helps a group of people understand their common objectives and assists them to achieve these objectives.
And if you are indulged in below activities, realize you must realign yourself for scrum to succeed;
  1. Boss has the ability to hire and fire others. 
  2. Taskmaster myopically focuses on assigning and tracking progress against tasks. 
  3. Product Manager is responsible for managing schedule, budget, and scope of the product.
  4. You lack interest in or concern about emotional, social, or spiritual well being of others. 
  5. The Performance Reviewer is responsible for documenting and evaluating job performance.

Comments

Post a Comment

Popular posts from this blog

What does the Kanban board do?

Is it just about placing post its all over the wall? Core of lean is visual management which is seen as having a board and placing all the open tasks on that. But there is more to visual management.  Visual management also means; information exchange improve transparency surface problems faster Typically Kanban board helps; Visualization of tasks of a team; task state and impediments Regular update and share of information during daily stand-up Reflection of process Team should try to teach a state where rate of "inflow of tasks" matches rate of outflow. Else tasks will keep on piling in different states (i.e. ready, in-work etc) and create an inventory which team will not be able to resolve quickly. Always high priority tasks are closed faster. So you will speed up results and identify and resolve impediments faster. But often people ask one question, why working with paper when modern electronic equipment and tools are available? The answ...
Post a Comment
Read more

Where do Scrum and Kanban fit?

I hear a question more often if agile is under the Lean umbrella, "so what is Kanban, and how does it compare to Scrum?” Scrum and Kanban are similar in certain aspects. In some others ways they are different. I am not talking about the similarity/differences here. Let's keep them aside for the time being. But lets understand under what circumstances how we can make best use of one over the other. Also can we combine them? If so, when? The image below is more of self explanatory. The axes represent how much risk involved in the project versus the focus. Here risk emphasizes the exploratory of innovative nature of the work. More exploratory, more the risk of failure and thus risk appetite of organisation is on the higher side.
Post a Comment
Read more