We as a DevTeam

DevTeam consists of generalists specialists (T-shaped skill set) who can perform all work to create product increment as envisioned in the Sprint Goal. The size of DevTeam is 6±3. There is only one role in a DevTeam – Developer. Each member of DevTeam may have a specialization (say QA, front end, back end, database, etc.) but everyone is responsible to achieve the sprint goal. There are no sub-teams within DevTeam. DevTeam members follow good engineering practices. DevTeam members self-organize to achieve the sprint goal. DevTeam is a long running team and members are full time allocated to it. All of DevTeam members follow same norms and rules.

As a DevTeam, we own Sprint Backlog. During Sprint Planning Meeting, devTeam negotiates with Product Owner to keep its commitment for the sprint. Sprint Backlog represents the commitment of devTeam for a sprint. DevTeam members participate in Daily Standup and share their work and impediment if any. DevTeam is responsible to deliver product increment at the end of the sprint. DevTeam presents items to PO as soon as acceptance criteria is met. DevTeam members collaborate to complete the work. DevTeam only accepts the work as envisioned in the sprint backlog.

As a DevTeam, we participate in scrum ceremonies.  DevTeam actively participates in refinement activities to keep Product Backlog healthy. DevTeam estimates PBIs. DevTeam evaluates the technical feasibility of PBIs. DevTeam is responsible for all work to be done to deliver as committed in the Sprint Planning Meeting (in the form of Sprint Backlog). DevTeam participates in Sprint Review ceremony to collect feedback from stakeholders. DevTeam conducts Retrospective in the end of each Sprint with PO and SM to reflect on self. DevTeam helps PO to conduct Demo.

As a DevTeam, we strive for automation to keep effectiveness and productivity (velocity) curve upward. DevTeam adopts Agile engineering practices to keep the quality of product high. DevTeam members strive to learn new tools, techniques, technologies, and skills to develop T-shaped skill set. DevTeam members work closely with PO and SM to deliver consistently and effectively.

As a DevTeam we strive to deliver value with sustainable pace. DevTeam remains in conversation with PO throughout a sprint to get clarification on the Sprint Backlog Items. DevTeam has the clear understanding of Sprint Goal. DevTeam not only focuses on HOW but also knows WHY and WHAT. DevTeam is responsible for continuous delivery of valuable outcome. DevTeam is empowered to make the decision about the HOW part to complete the work as listed in Sprint Backlog. DevTeam manages information radiators. DevTeam continuously communicates with users.

As a DevTeam, we continuously educate ourselves and share learnings with technical, Lean, Agile and Scrum communities. We organize and participate in technical, Lean, Agile, and scrum oriented community events to facilitate understanding of technical, Lean, Agile, and scrum values and principles.

I as a Scrum Master

As a Scrum Master, I assume administrative, coaching, and leadership roles to make Lean, Agile and Scrum successful. I help the team understand and embrace Lean Agile Scrum values and principles to develop into self-organizing teams and to produce valuable outcomes at a sustainable pace.  I assess the team’s knowledge of Lean, Agile, & scrum, and fill in the skills gap through training and coaching.  I serve as keeper of scrum framework, “holding space” for the team. I explore Agile and scrum tools and share my learnings with the team. I encourage teams to share their lessons learned and learn from others using various tools and techniques; e.g. Lean Coffee, Open Space, Tech Talks, etc. I help develop and maintain communities of practice to foster learnings and skill development.  I encourage teams to explore and embrace automation to boost productivity.

As a Scrum Master, I shield teams from interruptions to optimize the outcome. I mediate the general conflict of goals between devTeams (high quality) and Product Owner (more features).  I protect teams from external disturbances during sprints to keep them focused on deploying incremental value to our end customers. I help teams balance proactive activities with immediate goals. I ask open questions to foster communications and exploration of Why and What. I help teams become transparent in communications, practices, and behavior to foster trust. I encourage teams to bring out hidden problems and conflicts and then help to resolve them in benefit of increased trust and transparency.

As a Scrum Master, I facilitate effective Scrum ceremonies. I ensure all team members participate in daily stand-ups to share their respective work and decide how they can help each other with removing impediments. I help the Product Owners and Scrum team with refining the Feature/Product Backlog on a continuous basis to prioritize the Team Backlog Items for Sprint Planning Meetings.  During Sprint Planning Meetings, I ensure teams make commitments based on their capacity. I facilitate Sprint Review Meetings to collect feedback from the wider audience to continuously improve. I encourage teams to remain honest and positive during Retrospectives and to respect to gain trust the proceedings among team members only. I ensure that purpose of Retrospective is learning and improvement, not finger pointing and performance review. I help teams demonstrate the outcome of Sprints to the wider audience to spread the positive word about the team. 

As Scrum Master, I help Product Owners develop a positive rapport with their team and accept him/her as a part of the family. I encourage collaboration between devTeams and Product Owners.  I help the Product Owner interact with stakeholders to develop a collaborative relationship that produces valuable outcomes. I help the Product Owner explore different tools and techniques to discover the Business value of Feature/Product Backlog Items. I encourage Product Owners to interact with stakeholders on a continuous basis to refine and prioritize the Feature/Product Backlog.   I assist the product owner with prioritizing the Feature/Product backlog items.  I help the PO and devTeam develop and evolve Definition of Ready, Definition of Done, and Acceptance Criteria. I help the Product owner develop Sprint Goals and help the Scrum team achieve the same during sprint planning. I provide feedback to the Scrum teams on how to improve. I also ensure that improvement areas identified during retrospectives are captured and tracked in future sprints.

As a Scrum Master, I know when to step back and let the team learn from its own experience – successes and mistakes. I am available to the team for expert advice around scrum, and agile. I work as an advocate for the team in the organization. I certainly do not work as scrum police.  I do Gemba walk and encourage stakeholders to do the same.

As a Scrum Master, I continuously educate myself and share my learnings with Lean, Agile, and Scrum communities. I organize and participate in Agile and scrum oriented community events.

Scrum Metaphor: Scrum Master as a General Family Physician

Scrum Master is like old fashioned General Family physician who keeps a tab on the general health of the family. He takes care of common medical conditions and advises on healthy practices to keep the family healthy. Family members regularly visit him as well for special reasons.  As the family physician is with the family for a long duration, a trust gets developed between family and him. This trust enables him to become an adviser to the family.

As a family physician is a general practitioner, he may refer family members to specialists if a need arises.  He also keeps himself well aware in the field of general medicine by education and training.

Scrum Metaphor: DevTeam as a Soccer Team

Do you watch or play a Soccer game? Have you noticed how different players do their “job” and their tactics change during the game depending upon opposing team irrespective of what they thought of before of start the game?

DevTeam is like a soccer team where some members are specialized for certain type of tasks (e.g. defender or forward or even super specialized like a goalie) but almost everyone can play each other’s position.  The team has a coach who helps the team to lay down the strategy to win the game but during the play, it is the team which makes the decision.

Team Manager’s role is to collect all resources and make available to the team, so the team can do the best – soccer game.

The team as a whole win or lose, not the individuals even the coach and manager. A consistently winning team has members who gel with each other and in the team for a long time. Almost each team member understands each other – professionally as well as psychologically.

Each member pursues its specialization but also learns how to fill the gap if some team mate is not available due to some reason.

Scrum Master Criteria

The Scrum Master should meet the criteria for Scrum knowledge, skill, agile understanding and attitude. These criteria are listed below.

(Be)

• is a team player
• strives to improve continuously
• ready for help for team to achieve Sprint goals
• embraces change
• encourages communication – intra and inter team
• facilitates Scrum ceremonies
• shields team from external pressure
• servant leader

(Know)

• knows nitty-gritties of Scrum
• knows various agile techniques/practices of productivity enhancement

(Must/Should)

• facilitates smooth working environment for team
• guides people and teaches them something
• generates collaboration and interaction
• acts beyond projects

(Share)

• contributes to the Scrum community
• passes on knowledge and experience

SCRUM Master - Job Description

Summary

The Scrum Master will be responsible for developing and maintaining an agile SDLC for a development organization for a project team spread over multiple geographies, time zones and mix of multiple vendors (contractors) and employees. Scrum Master will also be responsible for the coaching/mentoring of existing development managers/leads on Scrum methodology as it is implemented and used during the project development life cycle.

As Scrum Master you must act like "Glue" or "Lubricant" depending on what the situation requires.

Role and Responsibilities

·         Develop and maintain agile SDLC for a software development organization, creating necessary standards, tools and best practices.

·         Guiding the team and organization on how to use Agile/Scrum practices and values to delight customers

·         Guiding the team on how to get the most, out of self-organization

·         Champion values of self-organization across organization

·         Assessing the Scrum maturity of the team and organization and coaching the team to higher levels of maturity, at a pace that is sustainable and comfortable for the team and organization

·         Removing impediments and/or guiding the team to remove impediments by finding the right personnel to remove the impediment.

·         Building a trusting and safe environment where problems can be raised without fear of blame, retribution, or being judged, with an emphasis of healing and problem solving.

·         Facilitating getting the work done without coercion, assigning, or dictating the work.

·         Act as protector of team and moderator to resolve issues within team if arise.

·         Helps team to focus on current Sprint, achieve sprint goals  and value optimization

·         Strive to help team to become high performance team with transparency, self-organization, business value focus, cooperation with competition

·         Helps Team to learn from its experiences

·         Supporting and educating the Product Owner, especially with respect to grooming and maintaining the product backlog.

·         Educating Product Owner on benefits of sustained velocity and setting up cadence of delivery

·         Providing all support to the team using a servant leadership style whenever possible, and leading by example

·         Ensures a proper power balance between PO, Team, and Management

·         Addresses needs efficiently and effectively

·         Detects hidden problems and strives to solve them

·         Facilitating discussion, decision making, and conflict resolution

·         Assisting with internal and external communication, improving transparency, and radiating information

Required Skills

·         CSM certification from Scrum Alliance

·         The ability to distinguish between what "is Scrum" what is "not Scrum"

·         Knowledge of other Agile approaches: XP, Kanban, Crystal, FDD, TDD, etc.

·         Understanding of technologies used by team

·         Must understand evolution of Scrum Master role in team over time period

Optional Skills

·         CSP certification from Scrum Alliance