This Festive Season, enjoy 10% discount on all courses Use Coupon NY10 Click to Copy

Search

Roles and Responsibilities of Successful Scrum Masters

How do the various roles and responsibilities make a Scrum Master an amazing game changer?Three influential powerful roles in Scrum framework of agile software development are- Product Owner, Scrum Master, and the Development Team (Development Team is a cross-functional team such as UI Designers, Dev, QA, DevOps and specialties necessary to complete the work). Here I am sharing my awesome experience by explaining the scrum master role.1. Scrum Master responsibilities towards Addressing Team Dynamics:A good scrum master encourages the team to follow Scrum and also ensures the team has a more productive environment. Provide guidance to the team on how they can become Self-organized to achieve the Sprint goals. Tackles scrum teams, work on impediments, facilitation and also educate organization on agile methodologies to maximize value delivered.  Enabled improvement in team delivery commitments and capacity planning for sprints by identifying & tracking hidden tasks that increased customer’s satisfaction. Ensures to keep build transparency with the entire team.Share insights throughout the company through blogging, internal confluences etc.Managing, improving, empowering and shielding the Scrum teams to achieve Sprint goals. Gives trustable Working environment where all problems can be raised without fear.Arbitrate between team members when necessary.Ensures a good relationship with Dev Team and Product owner  These responsibilities can also be qualities of successful scrum master 2. Scrum Master as a Facilitator, Moderator, and Master of Ceremonies: Facilitator  “key player responsible for Process ”, Moderator “Guide the Scrum team” and Master of Ceremonies “person responsible for the show i.e. Scrum events execution”.Scrum Master conducts ceremonies like Sprint Planning, Daily Stand-Ups, Sprint Reviews, and Retrospective meetings.Sprint Planning and Story Refinement: Ensure the product backlog has been ordered and completed by product owner before sprint planning begins.Attendees: Product Owner, Scrum Master, and Development Team.Time box: 2Hours for 2 Week Sprint.Sprint Review or Sprint Demo: Product Increment Demo, planned vs. completed work assignments. Capture actionable feedback as items in the backlog. Attendees: Stakeholder, Product Owner, Development Team and Scrum Master. Time box: 2 Hours for 2 Week SprintSprint Retrospective meeting: Meeting organized by Scrum Master in which team discusses three points:What went well in the sprint?What could be improved? What will we commit to improve in the next sprint? Any actionable suggestion is captured, assigned and tracked by Scrum Master.  Attendees: Development Team and Scrum Master. Product Owner is optional.Time box: 1 Hour for 2 Week Sprint Burn-Up and Burn-Down charts: Team progress display in terms of graphs is one of the most popular agile methodologies. Scrum master should be able to conduct Sprint /Release progress through Burn-up and Burn-down charts.  Burn-down chart represents how much work still remaining and burn up charts represents how much work has been done or completed. The main idea behind this is to make work progress visible to all levels. Ensures that a Definition of Done (DoD) and Definition of Ready (DoR) is maintained and followed by the Product Owner and team. Suggests Metrics (Metrics tool to track lead times, velocity, and no. of bugs logged so on.) fundamentals for the team as catalysts for change. Keeps track of running Sprint through Scrum tools like Scrum board, Kanban, action board, Jira, charts, backlogs etc.3. Responsibilities towards Product Owner and outside stakeholders: Product Owner someone projects key StakeholderProduct owner and Scrum Master are two different roles but both compliment each other and work closely for Project success.As per my current experience as a Scrum Master role, I observed that teams are not able to perform like they should because the Product Owner and Scrum Master spent more time in discussing roles and responsibilities than helping teams to produce value for their customers.Scrum Master helps Product Owner to maximize ROI (Return Of Investment) to meet his objectives through the scrum.Scrum Master works as a Liaise between the Product Owner and the Development team. Coaches Product Owner to help them understand how to achieve their goals and continually adapt and prioritize their backlog items for example in case there is a change in requirement or change in plan, Scrum Master knows it well how to come through the way that will benefit both Team and PO. Ensures to make collaborative meetings to bridge the gaps. When there is some internal/external conflicts that come up SM understands it and facilitate a collaborative meeting to resolve this. Ensures to work on every possible mitigation strategies to bridge the gap.4. Remove impediments:Impediments can be of any form and can come from any direction. Scrum Master to be brave and creative in removing impediments.Scrum Master owes two types of impediments:      1.Impediments owned by Scrum Master Lack of Automated testing in ProjectConflict between team members.Continuous Integration/Deployment is not good enough for Project     2. Impediments Scrum Master wants the team to resolveConflict between team members.Focus on roles5. Meta Skills:Scrum Master Should be Compassionate, Generous, Humble, Empathy, Selfless, Creative, Innovative, greatness for others, works for People over processes, Quick learner etc.Well trained in Agile techniques/practices like Agile Games, Acceptance Testing Driven Deployment (ATDD), Feature Driven Deployment (FDD), Paired Programming, Test Driven Development (TDD) etc. Familiar with CI/CD (Continuous Integration/Continuous Deployment). Fostering, vision statement, enabling a culture of openness, collaboration, and continuous improvement.“Scrum Master plays a very Crucial Support System role for team/Organization in implementing Agile/Scrum”6. Servant leadership quality: What is Servant leadership in Scrum? It means leaving one’s ego at the door, no authority or power over other team members, operate in a completely flat structure with zero hierarchy. Servant leadership is that the leader is not a superior, but rather a part of the body of the team. S – See the future,E – Engage and Develop OthersR – Reinvent ContinuouslyV – Value Results and RelationshipsE – Embody the Values Ensures ceremonies or planning sessions should be on time. Scrum Master knows that mistakes are unavoidable, it is human nature, after all, and mistakes are additionally a good teacher.Works with Dev team in Estimations so that team does not overcommits the work.Wrap it up: Last but not the least Scrum Master works as a doctor in terms of health check of the project. Coaches new Scrum Master and trained them so that they equally contribute to Organizations success. Of course, there are plenty of blog/articles available on Scrum Master Roles and Responsibilities or Day to Day activity but here I have reiterated my own experience as a Scrum Master.
Rated 4.5/5 based on 21 customer reviews

Roles and Responsibilities of Successful Scrum Masters

6K
Roles and Responsibilities of Successful Scrum Masters

How do the various roles and responsibilities make a Scrum Master an amazing game changer?

Three influential powerful roles in Scrum framework of agile software development are- Product Owner, Scrum Master, and the Development Team (Development Team is a cross-functional team such as UI Designers, Dev, QA, DevOps and specialties necessary to complete the work). Here I am sharing my awesome experience by explaining the scrum master role.
Scrum master roles

1. Scrum Master responsibilities towards Addressing Team Dynamics:

  • A good scrum master encourages the team to follow Scrum and also ensures the team has a more productive environment. 
  • Provide guidance to the team on how they can become Self-organized to achieve the Sprint goals. 
  • Tackles scrum teams, work on impediments, facilitation and also educate organization on agile methodologies to maximize value delivered.  
  • Enabled improvement in team delivery commitments and capacity planning for sprints by identifying & tracking hidden tasks that increased customer’s satisfaction. 
  • Ensures to keep build transparency with the entire team.
  • Share insights throughout the company through blogging, internal confluences etc.
  • Managing, improving, empowering and shielding the Scrum teams to achieve Sprint goals. 
  • Gives trustable Working environment where all problems can be raised without fear.
  • Arbitrate between team members when necessary.
  • Ensures a good relationship with Dev Team and Product owner

  These responsibilities can also be qualities of successful scrum master 

2. Scrum Master as a Facilitator, Moderator, and Master of Ceremonies:

 Facilitator  “key player responsible for Process ”, Moderator “Guide the Scrum team” and Master of Ceremonies “person responsible for the show i.e. Scrum events execution”.

  • Scrum Master conducts ceremonies like Sprint Planning, Daily Stand-Ups, Sprint Reviews, and Retrospective meetings.

  • Sprint Planning and Story Refinement: Ensure the product backlog has been ordered and completed by product owner before sprint planning begins.

Attendees: Product Owner, Scrum Master, and Development Team.

Time box: 2Hours for 2 Week Sprint.
Daily Scrum everyday

  • Sprint Review or Sprint Demo: Product Increment Demo, planned vs. completed work assignments. Capture actionable feedback as items in the backlog. 

Attendees: Stakeholder, Product Owner, Development Team and Scrum Master. 

Time box: 2 Hours for 2 Week Sprint
Sprint review

  • Sprint Retrospective meeting: Meeting organized by Scrum Master in which team discusses three points:
  • What went well in the sprint?
  • What could be improved? 
  • What will we commit to improve in the next sprint? 

Any actionable suggestion is captured, assigned and tracked by Scrum Master.  

Attendees: Development Team and Scrum Master. Product Owner is optional.

Time box: 1 Hour for 2 Week Sprint
Sprint Retrospective

 Burn-Up and Burn-Down charts: Team progress display in terms of graphs is one of the most popular agile methodologies. Scrum master should be able to conduct Sprint /Release progress through Burn-up and Burn-down charts.  
Burn-up and Burn-down charts.

  • Burn-down chart represents how much work still remaining and burn up charts represents how much work has been done or completed. The main idea behind this is to make work progress visible to all levels. 
  • Ensures that a Definition of Done (DoD) and Definition of Ready (DoR) is maintained and followed by the Product Owner and team. 
  • Suggests Metrics (Metrics tool to track lead times, velocity, and no. of bugs logged so on.) fundamentals for the team as catalysts for change. 
  • Keeps track of running Sprint through Scrum tools like Scrum board, Kanban, action board, Jira, charts, backlogs etc.

Sprint 1

3. Responsibilities towards Product Owner and outside stakeholders:

 Product Owner someone projects key Stakeholder

  • Product owner and Scrum Master are two different roles but both compliment each other and work closely for Project success.
  • As per my current experience as a Scrum Master role, I observed that teams are not able to perform like they should because the Product Owner and Scrum Master spent more time in discussing roles and responsibilities than helping teams to produce value for their customers.
  • Scrum Master helps Product Owner to maximize ROI (Return Of Investment) to meet his objectives through the scrum.
  • Scrum Master works as a Liaise between the Product Owner and the Development team. 
  • Coaches Product Owner to help them understand how to achieve their goals and continually adapt and prioritize their backlog items for example in case there is a change in requirement or change in plan, Scrum Master knows it well how to come through the way that will benefit both Team and PO. 
  • Ensures to make collaborative meetings to bridge the gaps. When there is some internal/external conflicts that come up SM understands it and facilitate a collaborative meeting to resolve this. 
  • Ensures to work on every possible mitigation strategies to bridge the gap.

4. Remove impediments:

Impediments can be of any form and can come from any direction. 

  • Scrum Master to be brave and creative in removing impediments.
    Remove impediments
  • Scrum Master owes two types of impediments:

      1.Impediments owned by Scrum Master 

  • Lack of Automated testing in Project
  • Conflict between team members.
  • Continuous Integration/Deployment is not good enough for Project

     2. Impediments Scrum Master wants the team to resolve

  • Conflict between team members.
  • Focus on roles

5. Meta Skills:

  • Scrum Master Should be Compassionate, Generous, Humble, Empathy, Selfless, Creative, Innovative, greatness for others, works for People over processes, Quick learner etc.

Scrum master meta skills

  • Well trained in Agile techniques/practices like Agile Games, Acceptance Testing Driven Deployment (ATDD), Feature Driven Deployment (FDD), Paired Programming, Test Driven Development (TDD) etc. Familiar with CI/CD (Continuous Integration/Continuous Deployment). 
  • Fostering, vision statement, enabling a culture of openness, collaboration, and continuous improvement.

“Scrum Master plays a very Crucial Support System role for team/Organization in implementing Agile/Scrum”

6. Servant leadership quality: 

What is Servant leadership in Scrum? It means leaving one’s ego at the door, no authority or power over other team members, operate in a completely flat structure with zero hierarchy. 

  • Servant leadership is that the leader is not a superior, but rather a part of the body of the team. 

S – See the future,
E – Engage and Develop Others
R – Reinvent Continuously
V – Value Results and Relationships
E – Embody the Values 

  • Ensures ceremonies or planning sessions should be on time. 
  • Scrum Master knows that mistakes are unavoidable, it is human nature, after all, and mistakes are additionally a good teacher.
  • Works with Dev team in Estimations so that team does not overcommits the work.

Wrap it up

  • Last but not the least Scrum Master works as a doctor in terms of health check of the project. Coaches new Scrum Master and trained them so that they equally contribute to Organizations success. 
  • Of course, there are plenty of blog/articles available on Scrum Master Roles and Responsibilities or Day to Day activity but here I have reiterated my own experience as a Scrum Master.
Kamla

Kamla Choudhary

Blog Author

I am a 3-dimensional IT Leader, having 10+years of experience and expertise performing diversified roles as QA Lead, Scrum Master, Agile Coach proficient in Healthcare, e-commerce, and eLearning Product Delivery and Reporting. Agile is a cultural change to be brought into an organization across all levels. As an experienced leader, I have knowledge, roadmap, persuasive attitude, negotiable and implementation skills to make transformation process a SUCCESS. Besides of the team involvement I am also engaged to companywide organization activities, coaching, mentoring, change processes, in-house training and stuff like this :)
 

Join the Discussion

Your email address will not be published. Required fields are marked *

Suggested Blogs

Agile Conflict Resolution Hacks You Should Master

A conflict in an Agile team, usually indicates that the members are actively involved in the team. They either try to drive a change accordingly or raise an issue against the actions of other team members. Conflicts help the teams become more mature and effective. However, resolving a conflict between the team members is becoming more like an umpire between two fighting teams. It is the Agile team, who is responsible for making everybody agree to choose a right solution.   The way of handling conflicts is called conflict style. In the year of 1972, Thomas-Kilmann introduced different styles of conflict resolution. At an initial stage, it is vital to understand the different conflict styles before developing strategies for handling the disputes. The five conflict resolution styles introduced by Thomas-Kilmann are Competing, Accommodating, Avoiding, Compromising, and Collaborating.  Conflict can be a positive factor if it is resolved potentially. If a conflict is not handled properly, it affects the project by damaging targets, breaking down the teamwork, and eventually the team members disengage themselves from their work. Resolving conflicts successfully will not only help teams solve many issues, but also offer many benefits that are not even expected at first. The benefits of conflict resolution are as follows:   Increased Understanding: Discussion on resolving a conflict allow teams to know each other, mount up awareness and search the best talent from the ideas coming out from the team members.    Increased team cohesion: After dispute resolution, team members form stronger mutual coordination and increase the ability to work together.    Improved self-knowledge:   Conflict resolution helps members examine the issue deeply, which enhances their knowledge, sharpens the target, and elevates productivity.   But the question is how to facilitate an effective conflict resolution? Following are the possible conflict management techniques, that can help teams manage the disputes smoothly.   1) Engage in personal coaching: Good relationship among team members is important. So always try to treat the members calmly and politely, take efforts in building a mutual respect and always be constructive while separating people and the associated problems. Always pay heed to the root cause. Listen carefully and act. Welcome ideas from the team members to reach to a proper solution.   2. Mentor a team through a conflict resolution process: This conflict resolution technique consists of four steps. Step 1- Set the scene. Initially, you need to identify the recurrent conflict patterns within the team. Guide a team to make them understand that conflict is a common problem and it can be solved by using an assertive approach rather than being aggressive.   Step 2- Gather Information.  Secondly, listen to others’ point of view and always respect their decisions. Gather information from the team, understand the conflict deeply and try to find a solution.   Step 3- Brainstorm to find out a solution. Arrange spontaneous group discussions to share the ideas on any tasks.   Step 4- Confer a solution. This is the last stage in conflict resolution. Through this step, the hurdles may be removed. Follow the “Be calm, be patient, have respect” principle throughout.    Conclusion: Conflicts in an Agile team are considered as the sign of a group of people working in collaboration. Sometimes conflicts are destructive if not handled properly. Positive and assertive approaches help resolve a conflict peacefully, with non-confrontational discussions. Generally, conflicts are resolved effectively when team members try to explore issues and possible solutions and listen carefully to the other members in the team.      
Rated 4.0/5 based on 20 customer reviews
1378
Agile Conflict Resolution Hacks You Should Master

A conflict in an Agile team, usually indicates tha... Read More

Scrum Master And Its Key Roles For Project Success

Agile can mould the formative years in your IT career. It can transform you into the best cultural fit in any organization. But most of the organizations that embarked on the journey to achieve more operational agility are rather confused about the role of the Scrum Master and who can play it well enough.    What is Scrum? “Scrum is a powerful framework which implements Agile practices in IT and other business projects. This framework consists of a team of 3 to 9 members excluding Scrum Master and Product Owner who break their work and try to complete in timeboxed iterations called Sprints and plan the task in Stand-up meetings, called Daily Scrum.” There are three key roles in Scrum- Product Owner Scrum Master  The Development Team In this article, we shall discuss the primary roles of a Scrum Master. To carry out the key Scrum Master roles successfully, you should be aware of the qualities that make you a competent Certified Scrum Master.  Who is a Scrum Master? Scrum Master is a leader of the Scrum team, he is referred as a champion of the project. Scrum Master guides the team and the Product Owner and ensures that the team members are implementing all the Agile practices properly. The Scrum Master is not only responsible for addressing all the issues encountered in the Agile development process, but also helps the business, product owner, team, and individuals to achieve a target, in the following ways: At the Business level, the Scrum Master creates a creative, productive, and supportive development environment and enables bidirectional collaboration. At the Product Owner level, the Scrum Master facilitates planning and helps product owners to stick to Scrum practices. At the Team level, the Scrum master provides guidance, support and facilitation, and helps to remove all possible operational barriers. At an Individual level, the Scrum Master supports individual efforts, addresses any raised issues, and removes impediments to help individuals be focused and more productive. In an interview conducted by the InfoQ, Lisa Hershman, Interim CEO at Scrum Alliance answered the questions on the major changes in the 2017 State of Scrum Report. She was asked about the changed role of the Scrum Master. Here is her reply-    This clearly indicates the importance of Certified Scrum Master training, that renders ample clarity on the roles of a Scrum Master.   Roles and Responsibilities of a Scrum Master | SCRUMstudy Blog#SCRUM #Agile #Kanban #SCRUMStudyhttps://t.co/FH2RfQRHP8 pic.twitter.com/vydHOtx0Rs — SCRUMstudy (@SCRUMstudy_) 15 January 2018   Roles of the Scrum Master The roles of the ScrumMaster are unique. Some of the key roles are discussed here- 1.The Scrum Master as a Facilitator: A “facilitator” for Agile teams, Scrum Master roles entail the following- Facilitates the meeting and Scrum ceremonies for the team members  Carries out a conversation between the team members and the Stakeholders. Uses different Agile techniques to achieve the targets of the project. Agrees on the “definition of done”. 2.The Scrum Master as a Coach: A Scrum Master is primarily a “Coach” or a “Guide” and is responsible for the following activities- Mentors teams on Scrum practices. Promotes ways for continuous improvements. Promotes standardized processes. Provides feedback. Helps to remove obstacles. 3.The Scrum Master as a Protector: A Scrum Master not only spearheads the team, but also protects it from imminent threats or risks, if any. Here’s how he does it-  Protects teams from external interruptions. Plays a key role in resolving conflicts between the team members. Promotes collaboration. 4.The Scrum Master as a work Enthusiast: Earlier, we have already stated that the Scrum Master is a Facilitator. Having said so, it is an imperative to mention that being an “Enthusiast” and an “Engager” is his way of facilitating project activities. An ideal Scrum Master-  Appreciates when the team does well. Celebrates with the team Promotes the success externally 5.The Scrum Master as a Motivator: A motivated team is a high-performing team. The motivator is typically the Scrum Master. Look at his many ways to motivate the team-  Carries out face to face communication Fosters team collaboration Adaptability to change Resolves problems without waiting for anyone to fix it. 6. The Scrum Master as a Servant Leader: This might sound paradoxical. But a Scrum Master both serves and leads his team. See for yourself-  Serves others Helps team members to develop and perform high Selfless management of team members Promotes team ownership 7. The Scrum Master as a Catalyst for change: A Scrum Master catalyzes changes in the team and boosts performance in no time through a few strategic strides-  Provides coaching in Scrum adoption Planning the Scrum implementation in an in-house organization Resulting as a Change agent, that increases the productivity Work with other Scrum Masters to increase the productivity of the Scrum team 8. The Scrum Master as an Embodiment of Agile values:  If you are to call anyone the “Believer and Preacher” of Scrum values, it has to be none other than the Scrum Master. The following practices earn him the tag-  Reflects Agile and Scrum values to the team Reminds policies to the teams Assists the teams in continuously improving Checks all the models like Sprint backlog, metrics, product backlog of Scrum     What a Scrum Master is “NOT” A lot of grounds has already been covered on what a Scrum Master “is”. However, it is equally essential for us to learn what all he “is not”. This will only help eliminate any opacity and ambiguity about his roles. Scrum Master (SM) is not a Project Manager (PM). Project Manager is a leader, a decision maker. PM manages the project and the teams to accomplish the project target. Scrum Master acts as a coach, facilitator and SM acts as a mediator between the project and the customer.  Scrum Master is not a Product Owner (PO). POs have the huge responsibility of a project. A PO maintains the product backlog. PO has to manage and reprioritize the backlog to fit these changes and drive the project. Concluding Thoughts- The role of the Scrum Master is still a matter of discourse. Organizations consider Scrum Masters as the voice of the Scrum framework. Usually, people see Scrum Master as a facilitator only, but firstly he/she is a coach. The world domination of Agile is clearly happening. But despite all your struggles, there is that glass-ceiling that is limiting your potential to perform as a Scrum Master. Break this limit and take a step  ahead to get laser-focused on the key Scrum Master roles. Certifications like CSM and other related training and courses can be the best way to do it.   
Rated 4.0/5 based on 20 customer reviews
1077
Scrum Master And Its Key Roles For Project Success

Agile can mould the formative years in your IT car... Read More

How to Launch Your 1st SAFe Agile Release Train

So, you are excited to organize and launch your 1st SAFe Agile Release Train. Understanding the importance, structure, and deployment of ART (SAFe Agile Release Train) is the central of SAFe Agile implementation to scale & successfully implement the complex projects, deliver maximum business values and complete the project on time well under the budget. Just like a train carries its passengers to deliver at set destinations within pre-estimated time at defined cost, ART also helps you carry out the projects successfully; however, before starting the journey with an efficient ART, you must know the principles that govern Agile Release Train.    10 Steps to Launching your First SAFe Agile Release Trainhttps://t.co/dNWUfCwMBd pic.twitter.com/rT8FDhqcoj — Yves Mulkers (@YvesMulkers) 27 January 2018 5 Governing Principles for SAFe Agile Release Train:  ART is the self-organised team of Agile Teams. It is composed of Agile teams engaged in development, security, DevOps, Enterprise Architecture etc. ART plans. It commits & executes the processes following a specific timeframe often called - PI (Program Increment). ART must follow a value delivery model for periodic planning and timely release.  ART must follow a common iteration length within the PI.  ART must know the clearly-defined objectives & benchmarks. ART must follow the culture of continuous system integration. The works completed by different teams must be integrated at each sprint to keep the developments in releasable state. ART must respect customer previews, internal reviews, and system level QA.    Roadmap to Launch SAFe Agile Release Train:  1.Train the SAFe Program Consultants (SPCs): Train your SPCs properly, the change agents responsible for transformation and connecting the Scaled Agile Framework (SAFe) to your organization. SPCs teach all the stakeholders & leaders to drive the ART to its destination.  2.Train the Lean Agile Leaders: Lean Agile leaders are expected to understand and implement the principles of SAFe Agile framework. Lean Agile Leaders are also responsible to lead & facilitate SAFe adoption for improved outcomes. And for smooth transition, you need to train the Lean Agile Leaders up to the best standards.   3.Identify Value Streams and ART:  SAFe Agile Release Train is a procedural system; therefore, you should make all the responsibilities of solution defining, building, validation, and deployment etc clear.  4.Organize ART and Agile Teams:  The roadmap to organize the ART and Agile teams contains different millstones including:   Well-defined ‘product’ with features/components Leadership support Collaboration Minimized dependencies Integration Well-managed DevOps activities 5.Define and Fill All The Roles Of ART Members:   The critical roles of ART members must be well defined to help the Release Train Engineer, System Architect, Product Managers, Scrum Masters, Product Owners perform the best at par with customer’s expectations.     6.Prepare the Program Backlog:   The practice of using launch date as the forcing function makes it more urgent to determine the scope and vision of PI. The scope of ‘what is built’ or PI is defined by ‘Program Backlog’ informing about the upcoming features, architectural work, and NFRs. The gained vision about the future behaviour of system helps you create short stories for Agile teams.        7.Train the Teams Train the teams properly to deliver the maximum values at each sprint. It is the key part of ART readiness to ensure the on-the-time best quality ‘product’ delivery. 8.Conduct PI Planning  PI planning is a face-to-face meeting event; it empowers the Agile Release Train to align all the SAFe Agile teams for the shared mission & vision.  9.Set the Program Calendar & Launch Date  Now you have ART definition. The next task is scheduling your 1st PI Planning event focused on the forcing functions and ‘date-specific’ launch with PI calendar. The PI calendar shows the scheduled activities including PI planning, System demos, ART sync, Inspect & Adapt (I&A) workshop etc.  10.Execute Innovation and Planning Iteration:  Now, you are almost at the destination. Innovation and planning iteration is conducted to absorb the variances in estimates, allot time for innovation, refine backlog and to plan ‘Inspect & Adapt’ workshop.  Conclusion: Launching SAFe Agile Release Train (ART) for the first time can be a challenging and complex task; therefore, before going ahead, you should acquire the expertise by joining short-term SAFe 4 Release Train Engineer certification training designed to guide you through for efficient ART launch. .   
Rated 4.5/5 based on 7 customer reviews
1021
How to Launch Your 1st SAFe Agile Release Train

So, you are excited to organize and launch your 1s... Read More