Search

How To Build A Self-Organizing Team As A Scrum Master

The key element of implementing Scrum successfully in an Agile-oriented business is the self-organized team; however, it leads to a misconception that every team member will be loose cannon, working without the ownership and directions for the assigned task; which is just opposite to the actual experience because the self-organized team members work together under the agreed framework of norms, guidelines, and expectations to achieve iteration goal. Most Agile-Scrum organizations emphasize on building the self-organizing team - why?  The 4 Key Benefits of Scrum Self-Organizing Team:   “Individuals in an empowered organization have the knowledge, skill, desire and opportunity to personally succeed in a way that leads towards collective success" (Stephen R. Covey, Principle-centered Leadership). The 4 key benefits that drive the experienced Scrum Master to build the self-organizing team are:  Motivation improves the performance of the Scrum team Innovative & creative environment is conducive to everyone’s growth Everyone learns from the failures and successes to perform the best with self-optimization Improves ownership because each member feels more responsible for the sprint result   Roadmap to Build a Self-organizing team as a Scrum Master:  Who is responsible for building the self-organizing team? Definitely, Scrum Master is primarily responsible for building a self-organizing team ensuring the cohesive working environment for all the team members. Like the job itself, building Scrum self-organizing team is also a complex challenge for the Scrum Masters. The complete task can be simplified by dividing it into three steps:   Step 1. Training:  The problems can’t be solved with same level thoughts that create them; and, we need the motivated trained minds with a zeal to solve the particular problems. Each Scrum team member is expected to have the best level skill set; therefore, Scrum Master must provide classroom or on-the-site task-specific training to individuals. Often, the efficient Scrum masters tend to lead to problem-solving; but instead of solving the problems yourself, it is better to let the trained team members do it. In parallel, behavioural - communication training must be planned to shorten the training period.  Certified Scrum Masters have mostly proved their potential in building such trained teams.  Step 2. Coaching:  Scrum Master must behave as a coach to guide the team members for solving the problems. Some team members may require more guidance at the start but analytical support trains them to crack the nut on their own. After proper Scrum training and coaching, you will experience the team heading for self-organizing but the task is not completed yet. Scrum Master is expected to observe the team members to make further improvements in identified areas.  Step 3. Mentoring: Keeping your team self-organizing is also a challenge because changing the traditional work habits is not so easy. The challenge can be easily managed by behaving like a mentor who helps the team members to perform at the next level. As per Scrum guidelines, the most efficient and capable Scrum team member to solve a specific problem is the one who needs to solve it. The mantra of building a successful Scrum self-organizing team is – “Self-organizing team need task oriented coaching & personalized mentoring not the “command & control”. Conclusion with 7 Tips for the Scrum Masters to Build Self-Organizing Team:  It takes time to make the people willing to take bigger responsibilities. I always say to Scrum self-organizing team members that they should take initiatives on their own instead of waiting for others to take action for problem-solving. This approach of Scrum self-organizing team speeds up the development besides providing more time for the Scrum Master to focus on other important issues. To conclude, I summarize the 7 points to help you build efficient and successful Scrum self-organizing teams:    To touch the extremes of your career as an efficient Scrum Master be honest in “Know your stuff & learn that you don’t” approach.   Assert the influence but without taking over. Suggest new ideas to address impediments; and, authorize the team members to manage the problem in their own way.  Ask complex questions to motivate the members to come up with innovative concepts Support the team members to take actions  Use safe-to-fail tests to let the team members imply learned skills Be available for the team members to let them work in a flow  Be a practical hardliner because your Scrum team needs it  
How To Build A Self-Organizing Team As A Scrum Master
Shubhranshu Agarwal
Rated 4.0/5 based on 20 customer reviews
How To Build A Self-Organizing Team As A Scrum Master 364
How To Build A Self-Organizing Team As A Scrum Master

The key element of implementing Scrum successfully in an Agile-oriented business is the self-organized team; however, it leads to a misconception that every team member will be loose cannon, working without the ownership and directions for the assigned task; which is just opposite to the actual experience because the self-organized team members work together under the agreed framework of norms, guidelines, and expectations to achieve iteration goal. Most Agile-Scrum organizations emphasize on building the self-organizing team - why? 

The 4 Key Benefits of Scrum Self-Organizing Team: 

 “Individuals in an empowered organization have the knowledge, skill, desire and opportunity to personally succeed in a way that leads towards collective success" (Stephen R. Covey, Principle-centered Leadership). The 4 key benefits that drive the experienced Scrum Master to build the self-organizing team are: 

  1. Motivation improves the performance of the Scrum team
  2. Innovative & creative environment is conducive to everyone’s growth
  3. Everyone learns from the failures and successes to perform the best with self-optimization
  4. Improves ownership because each member feels more responsible for the sprint result
     



Roadmap to Build a Self-organizing team as a Scrum Master: 


Who is responsible for building the self-organizing team? Definitely, Scrum Master is primarily responsible for building a self-organizing team ensuring the cohesive working environment for all the team members. Like the job itself, building Scrum self-organizing team is also a complex challenge for the Scrum Masters. The complete task can be simplified by dividing it into three steps:  

Step 1. Training: 

The problems can’t be solved with same level thoughts that create them; and, we need the motivated trained minds with a zeal to solve the particular problems. Each Scrum team member is expected to have the best level skill set; therefore, Scrum Master must provide classroom or on-the-site task-specific training to individuals. Often, the efficient Scrum masters tend to lead to problem-solving; but instead of solving the problems yourself, it is better to let the trained team members do it. In parallel, behavioural - communication training must be planned to shorten the training period. 

Certified Scrum Masters have mostly proved their potential in building such trained teams. 

Step 2. Coaching: 

Scrum Master must behave as a coach to guide the team members for solving the problems. Some team members may require more guidance at the start but analytical support trains them to crack the nut on their own. After proper Scrum training and coaching, you will experience the team heading for self-organizing but the task is not completed yet. Scrum Master is expected to observe the team members to make further improvements in identified areas. 



Step 3. Mentoring:

Keeping your team self-organizing is also a challenge because changing the traditional work habits is not so easy. The challenge can be easily managed by behaving like a mentor who helps the team members to perform at the next level. As per Scrum guidelines, the most efficient and capable Scrum team member to solve a specific problem is the one who needs to solve it. The mantra of building a successful Scrum self-organizing team is – “Self-organizing team need task oriented coaching & personalized mentoring not the “command & control”.

Conclusion with 7 Tips for the Scrum Masters to Build Self-Organizing Team: 

It takes time to make the people willing to take bigger responsibilities. I always say to Scrum self-organizing team members that they should take initiatives on their own instead of waiting for others to take action for problem-solving. This approach of Scrum self-organizing team speeds up the development besides providing more time for the Scrum Master to focus on other important issues. To conclude, I summarize the 7 points to help you build efficient and successful Scrum self-organizing teams:   

  1. To touch the extremes of your career as an efficient Scrum Master be honest in “Know your stuff & learn that you don’t” approach. 
  2.  Assert the influence but without taking over. Suggest new ideas to address impediments; and, authorize the team members to manage the problem in their own way. 
  3. Ask complex questions to motivate the members to come up with innovative concepts
  4. Support the team members to take actions 
  5. Use safe-to-fail tests to let the team members imply learned skills
  6. Be available for the team members to let them work in a flow 
  7. Be a practical hardliner because your Scrum team needs it

 

Shubhranshu

Shubhranshu Agarwal

Blog Author

Shubhranshu Agarwal is a technical writer with special interest in business management and project management subjects. Over the 15 years of freelance content writing, he has written a lot to help the industries, businesses and project managers to achieve the sustainable growth by implementing strategic critical management methodologies.
 

Leave a Reply

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

Suggested Blogs

Top-paying Agile Certifications To Consider In 2018

The potential positives of Agile and Scrum training are many. Much explains why these training courses have exploded in popularity. The demand for Agile and Scrum training and related courses has not only just increased but intensified in the recent years. One can state with confidence that the era of the non-Agile projects is almost gone!Benefits of Agile certifications:Today, Agile and Scrum occupies a sizeable niche in the corporate sector, and this exactly has spurred an increasing number of IT professionals to pursue these trainings. As a software professional, if you wish to firmly plant yourself into the Agile confines, it is nearly time you explore some of the top training programs.This following sections will present condensed overviews of some of the highest-paying certifications you need to consider to boost your career.1. Agile and Scrum Training:Salary: The average salary of an individual with Agile and Scrum skills is $111,000 per year.Agile methodology offers incredibly enhanced productivity and quality. Agile practices include risk mitigation, new requirements, meeting customer demands and continuous improvement with pre-planned Sprint. Today, the rising demand for such practices in the organizations have made Agile and Scrum very popular.According to the State of Scrum report 2017,“Agile and Scrum methodology is increasing beyond IT and taking hold in diverse industries.”Benefits of Agile and Scrum trainingAn individual will know the difference between the Agile and traditional project development methodologies.Understand how Agile method can be well fitted into the software development projects.Learn the cycle: Concept-Initiate-Deliver-DeployAdopting Agile will help you attain enhanced business value.An individual will earn 8 PDUs and 8 SEUs and course completion certificate.Prerequisites for Agile and Scrum training:There are no specific requirements to obtain Agile and Scrum training. The workshop is for the interested candidates, those want to learn more about the Agile Manifesto, its framework and techniques.Note: Interested individuals should make sure that the chosen institute is a Registered Education Provider (REP) of  “Scrum.org”, the globally renowned certifying body for Agile methodology.2. Certified Scrum Master® (CSM) TrainingSalary: The average salary of CSM is $106,938 per year.The Scrum Master is the facilitator of an Agile project who removes obstacles, manage processes and ensures that the team adheres to the Scrum values and practices that are religiously followed in the top organizations. The CSM® training will help you achieve proficiency in the processes of Scrum methodology.Note: Interested individuals make sure that the chosen institute is a Registered Education Provider (REP) of  “Scrum Alliance”, the globally renowned certifying body for Agile community.Prerequisites for CSM® Certification Training-You don’t need any prerequisites for attending the course. After completing this course, the candidates will receive an email which includes a link to generate your login credentials. You can use that data to take the test online. The CSM test fee is included in course fee, however, retake of the exam will cost $25.3. Professional Scrum Master (PSM)® Training:Salary: The average salary of a PSM is $100,500 a year.The Professional Scrum Master™ (PSM) training entails a deep understanding of the basics of Scrum and makes clear the other practical approaches and mechanisms in Scrum. The key learnings of this course consist of team dynamics, team motivation, conflict resolution and improved planning and estimation.Prerequisites for PSM® Training-Any interested individual can attend the training and certification exam as well. Once you complete the course, you will receive a password to attend the PSM I assessment conducted by Scrum.org. Then an individual can subsequently proceed to undertake level II and III assessments.4. Certified Scrum Developer® (CSD) TrainingSalary: The average salary of CSD is $71,750 per year.The Certified Scrum Developer® (CSD) training is especially designed for the programmers who are building software in the Scrum environment. The CSD training is dedicated to exposing the individuals to the Scrum tools and techniques required to build a software.Benefits of Certified Scrum Developer® (CSD) TrainingThis course will help individuals to-Note: It is better to get certified by the institute which is a Registered Education Provider (REP) of Scrum Alliance.Prerequisites for CSD® TrainingIn order to get CSD® certified, you need to attend at least 5 days of formal training by a Registered Education Provider (REP) of Scrum Alliance and the SA certified instructor. CSM certification holders can skip the first 2 days of training and directly take training from the 3rd day.5.  Professional Scrum Developer® (PSD) TrainingSalary: The average salary of PSD is $93,734 per year.The Professional Scrum Developer® (PSD) training is especially designed for the programmers who are building software in the Scrum environment. The PSD training is dedicated to exposing the individuals to the Scrum tools and techniques required to build a software.Benefits of Professional Scrum Developer® (PSD) TrainingThis course will help individuals to-Prerequisites for CSD® TrainingIn order to get PSD® certified, you need to attend 3 days of formal training by a Registered Education Provider (REP) of Scrum.org and the Certified Scrum Trainer (CST). The candidates should have programming experience and  have undergone Scrum foundation training or atleast have working experience in Scrum team.6. Certified Scrum Product Owner® (CSPO) TrainingSalary: The average salary of a CSPO certified professional is $101,459 per year.The Product Owner is a critical role of the Scrum team and bears the responsibility to lead a project successfully, collaborating with the stakeholders and team in the Daily Scrum, and managing the business targets.Prerequisites for CSPO® TrainingTo obtain this certification, the candidates must have a basic knowledge of Agile to attend this the training. To be eligible for the certification, candidates must take the 2-day CSPO course certificate. On successful completion of 2-day CSPO training by the Certified Scrum Trainer (CST), you will receive a CSPO® certificate from Scrum Alliance designating you as a Certified Scrum Product Owner (CSPO).7. Professional Scrum Product Owner® (PSPO) TrainingSalary: The average salary of a PSPO certified professional is $102,000 per year.The Product Owner is a critical role of the Scrum team and bears the responsibility to lead a project successfully, collaborating with the stakeholders and team in the Scrum meeting, and managing the business targets.Prerequisites for PSPO® TrainingTo obtain this certification, the candidates don’t need any prerequisites for attending the course and subsequent certification.Learn more about the differences between a CSPO and a PSPO from the following video-8. ICP-ACC (ICAgile- Agile Certified Coach) Training:Salary: The average salary of ICP-ACC certified is $119,883 per year.An Agile coach provides focussed guidance, creates awareness of the business goals and serves as a mentor, teacher, guide, conflict resolver, and planner to the Agile team. Also, the Agile Coach facilitates Agile thinking and practices to support the team to attain their project goals. The Agile Coach fosters a new culture of Agile-Lean thinking to welcome the organizational change and changing the work behavior.Prerequisites for ICP-ACC TrainingTo obtain ICP-ACC certification, candidates should have a basic idea of Agile methodology and at least some experience as an Agile practitioner. On successful completion of the training, candidates will get ICAgile Certified Professional-Agile Certified Coach (ICP-ACC) designation from the internationally recognized ICAgile certification body.Note: Before choosing any institute, ensure that the institute is an authorised by ICAgile certification body.9. Leading SAFe® 4.5 Training Course:Salary: The average salary of Leading SAFe 4.5® certified individual is  $68,667 per year.Leading SAFe® 4.5 certification will help you to foster your organization’s success. SAFe Agilist (SA) certification will allow you not only to execute and deliver value through Agile Release Trains (ARTs) but also to lead a Lean-Agile transformation in scaled organizations. This certification will also let you build a continuous delivery pipeline, DevOps culture. Also, the course exhibits the power of coordinating with the larger solutions and empowering a Lean portfolio culture within the enterprise.Benefits of Leading SAFe® 4.5 Training Course-After the course, candidates will be able to-Exhibit how the combination of Lean, Agile, and Product Development shapes the SAFe® foundation.Apply SAFe® 4.5 principles and Lean-Agile mindset to scale the Lean and Agile development in the organization.Managing development of the larger solutions and bolster a Lean-Agile transfiguration in the enterprise.16 PDUs and 16 SEUs and a one-year membership with Scaled Agile Inc.(SAI)Note: Before choosing the institute, ensure that the course is authorised by Scaled Agile Inc.(SAI)Prerequisites for Leading SAFe® 4.5 Training Course-To obtain this certification, you need to complete the course, followed by the exam. However, for attending the exam, the candidates must have 5+ years of experience in software development, testing, business analysis, product or project management. Also, he/she should have work experience in Agile and Scrum.After the course, candidates will get 3 emails from Scaled Academy.A welcome email to create a profile,A survey email which requests your feedback on the training,An exam link email with instructions for the exam10. PMI-ACP® Certification Training:Salary: The average salary of PMI-ACP® is nearly $123,000 a year.The Project Management Institute-Agile Certified Practitioner (PMI-ACP®) is a broadly acknowledged certification in the Agile community and is a proof of the holder's capability to manage projects utilizing Agile practices. Working experience in Agile projects, knowledge of Agile practices, principles, tools, and techniques, and the Agile training are the prerequisites to attend PMI-ACP® training.Benefits of PMI-ACP® Certification Training-This course will help individuals to-Attain deep knowledge of Agile Manifesto, its processes, principles, tools, and techniques.Understand the Scrum Framework, its associated roles and responsibilities, scrum tools to increase transparency, lowering the risks and quality product faster.Learn the concepts that will help you to accomplish project goals within a confined time and budget constraintsDevelop the soft skills like emotional intelligence, conflict resolution, working in collaboration etc.21 PDUs and 21 SEUsCourse completion certificate and courseware approved by PMI® (if the institute is PMI® approved)Prerequisites for PMI-ACP® Certification Training:To acquire this certification, candidates must have2000 hours of working experience in general projects or active PMP® OR PgMP credential.1500 hours of Agile project working experience21 contact hours earned in Agile practicesTo attend the exam, you just need to register and create a login at the PMI’s online system.Note: Choose PMI ® approved certification institute as Project Management Institute® is the renowned certifying body of Project Management. Today, Agile and the organizations aren’t strangers anymore. A plethora of Agile certifications are available for the interested people to boost their Agile career. As you are most likely aware, simply earning a skill is not enough, you need to prove yourself to the potential employer. The relevant training programs open your talent to the outside world. To start your career with a reputed organization, look for the various certification options available to drive you to success. Also, find a good institute to pick the course that best fits your requirements. You can visit https://www.knowledgehut.com/ for more details. Buckle up to keep climbing the Agile ladder!
Top-paying Agile Certifications To Consider In 2018
Author Image
Rated 4.0/5 based on 65 customer reviews
Top-paying Agile Certifications To Consider In 201...

The potential positives of Agile and Scrum training are many. Much exp... Read More

Scrum Master vs. Project Manager: Differences and Similarities

Organizations that are new to Agile and Scrum commit some deadly blunders. The most common and overlooked one is the lack of clarity of the roles of the Scrum Master and the Project Manager. This is more often seen in smaller Scrum teams, where these two discrete roles overlap.  There are of course similarities between Scrum Master and Project Manager roles. But that does not give way to ignoring the distinct differences between an Agile Project Manager and Scrum Master.  We have spaced out this article into various sections-  Scrum Master vs. Project Manager roles and responsibilities Scrum Master roles and responsibilities: Scrum Master is referred as a facilitator, who manages the teams that are implementing the Agile methodology. Scrum framework is the best framework for smaller teams of developers, who can break their work into a Sprint in order to get your project done at the end of every sprint.  The roles and responsibilities of the Scrum Master includes- Sprint planning  Scheduling the daily Scrum meeting Managing Scrum process responsibly Helping the Scrum teams to follow Scrum practices Removing barriers so the team can focus on their work Assisting with the Product Backlog Co-operating with Product Owner in designing Product Backlog items for the next Sprint Protecting the team from external distractions Recording and assisting to improve team dynamics   *Project Manager roles and responsibilities: Project manager’s role is to manage the projects and ensure that the project meets the requirements. The roles and responsibilities of the Project Manager are as follows- Defining project scope to the team Planning project target Preparing the work schedule for the team members Gathering requirements Defining the resource requirements for the project Preparing the budget for a project Assuring quality Mitigating the risks Monitoring the plans Getting user feedback Managing relationships with the client and the stakeholders Ending the project Similarities between the Scrum Master and the Project Manager Project Manager and Scrum Master both are humans and they both make mistakes. But they both debug and learn from the mistakes. They both can communicate, receive feedback, mitigate the risks, and enable a great bonding within a team. Actually, neither the Project Manager nor the Scrum Master is the supreme authority. The Project Manager has to report to the client and the stakeholders, whereas the Scrum Master has to report to the Product Owner alongside the stakeholders and clients. Both Project Manager and the Scrum Master fail when they ignore the basic principles that are supposed to be adhered to. They fail when they not only neglect being professionals, but also when they are any less than skilled professionals. Sometimes, they may also fail when they disrespect the team members’ opinions. Differences between the Agile Project manager and Scrum Master While noting down the differences between the Project Manager and the Scrum Master, you will find out that the Project Manager plays the leadership role by leading a planning for the execution of the project. Scrum Master plays a support role for the team members, by working closely with the team and assuring that they are following Agile principles properly. Let’s look at the major differences between the PM and SM: Project Manager(PM) vs.Scrum Master(SM) Goals Has defined goals like- Completing the project on time, planned budget, and scope Makes sure that the team members are well trained to follow Agile practices appropriately. Also, SM coaches the Scrum teams and mentions the timeline to finish the project. Quality Assurance PM also knows the importance of quality, but doesn’t know how to achieve this. Usually, a consultant is hired to fix the errors. SM assures the quality and very well knows the importance of it. Team Size Project Managers like to make the things large. PM works with more people and a huge budget. In this way, they improve to Program Manager Scrum Master always tries to keep things smaller. They like to work in small teams irrespective of budget. Average Salary Rs.1,351,403 per year Rs 1,036,017 per year Job Description The job description of the Project Manager includes- Planning, creating budget and the related documents PM has to work with upper management to ensure a scope and direction of a project PM has to work with another department also, in case of emergency sometimes have to work themselves or instruct the team to finish a goal. The job description for Scrum Master includes- Resolves barriers and controls the Scrum processes. Making a team aware of Agile and Scrum to deliver successfully Facilitates the Scrum ceremonies Ensures that a project is running smoothly with the help of the tools Executes the Product Backlog as per the Product Owner prioritization Solves team conflicts with good communication skills Motivates the team Monitors the Scrum processes to increase efficiency   Scrum Master vs. Project Manager certification The Scrum Master and the Project Manager certifications are the two most popular certifications of the Agile and Waterfall methodologies.  Scrum.org report as of 30th April 2017 states that around 110,000+ people are  Scrum certified. Only 56% of the Project Management Specialists are holding a Project Manager Certificate, even in Big IT companies. This was revealed in a survey conducted by IBM.  Last words: Deciding between the Scrum Master and Project Manager certification is indeed a tough choice and entails a careful consideration of the prospects of each. Eventually, the role of a Scrum Master is proved as a ‘deciding factor’ of the successful projects. The Scrum Master and the Project Manager both have distinct roles. Both need particular skill-sets and a right person to make the work happen.       
Scrum Master vs. Project Manager: Differences and Similarities
Author Image
Rated 4.0/5 based on 9 customer reviews
Scrum Master vs. Project Manager: Differences and ...

Organizations that are new to Agile and Scrum commit some deadly blund... Read More

The Biggest Challenge of Agile

I have had the experience of implementing Agile from scratch in organizations that were using no development methodology at all. And I have also had the opportunity of guiding and supporting several companies in the improvement of their Agile adoption. In both cases, you need to know how deep the company wants to go, what level of adoption they expect and  whether they understand the benefits of being Agile (yes, several companies just do it because it’s trendy, but trendy is not enough when it comes to organizational changes).   As a coach, when guiding organizations in their Agile journey you will have in your mind several ideas on what you have to do to be successful. You will revisit those ideas and find out which ones are the most appropriate for your client. There are different approaches you can use, but at a higher level, you will have to choose between the two: let the organization detect what is the best way to meet their objectives, or use your previous experience to tell them what steps they should follow to succeed.  No matter which approach you select, you may probably think that your ideas are considered brilliant. After all, who can say Agile is not good nowadays? You may also think that everybody believes that the change is going to be beneficial for them (if most organizations are using it, why would it be different in this case?). Your work will be really successful! But guess what? Things may start to get complicated. The steps you chose may make no sense anymore. Agile adoption may no longer be an easy way to go. So, what’s happening? Why are you facing all these challenges and setbacks? Well, the answer is simple: people. People are the major roadblocks when implementing Agile. They offer resistance, even when they do not make it consciously. The big question is… why? Fear Even when this may seem a bit exaggerated, many people are afraid. They think they may lose their jobs, may be exposed and at risk for not having had good ideas in the past or not having detected the improvements before.   Lack of understanding It may happen that people will not understand the approach you are suggesting. They may not be clear on what to do and how to do it. Thus, they feel unsafe, they think they may ruin everything. And don’t forget that all this is really important for the organization (they may feel the pressure, don’t you think?)   Comfort zone “If everything works this way, why should I change?”. This is one of the most commonly heard excuses. But what that generally means is “All this is so new, I don’t know if I’ll be able to do it. Just thinking about it stresses me out!”.   Then, what can you do to help people commit to and collaborate with the change?   1) Show yourself as a peer - you’re not the enemy and they have to know that Reserve some time to meet people so that they know you. Spend time building relationships, understanding the main concerns of the people involved in the transformation. Tell them why you’re there and what you want to achieve. Let them know that your job is to serve, not to command. 2) Define a clear vision and, most important, the reasoning behind it If the team has no vision, then they have no north. The vision is the place where they will go every time they lose focus. No matter how busy you are, you must ensure that the whole team knows what the final goal is and why it is important. Most importantly, they need to know why they will benefit from this.   3) Let the team decide their own path Have the team not only detect their areas of improvement, but also define the specific actions to improve. Doing so, people will feel reinforced, they will believe in their autonomy and they will feel owners of the change. 4) Assign owners, avoid being the “boss” You will be tempted to do everything on your own. After all, you’re the most experienced person in this journey! This is a tremendous mistake. If you do so, people will see you as the “boss” and all the effort you made to win their trust and to build relationships will be sent to the trash. Instead, remember that people need to feel important, they need to feel that they are adding value and that their work matters. Assign them important tasks, make them feel appreciated and valuable. 5) Guide them in the process of change, since change hurts! We’re not designed to adapt to change. Our brains are not prepared for that. But the world in which we’re living requires adaptability from us, everything evolves so fast! So, given that it is pretty normal that people feel uncomfortable with change you should be their guide and help them overcome difficulties and deal with their own limitations. 6) Give them wings to fly (and to learn to improve on their own) You will not always be there for them. The best legacy of a good coach is a person or group of people that can continue your work. Use your time with the team to identify those that have the required skills to support the company and its improvement cycle once you’re gone. Be a personal coach for them as well. This way, you’re job will be complete, you will have guided the company in its initial Agile transformation and you will have left people prepared for future improvements.
The Biggest Challenge of Agile
Author Image
Rated 4.0/5 based on 20 customer reviews
The Biggest Challenge of Agile

I have had the experience of implementing Agile from scratch in or... Read More