Search

A Practical Perspective On Addressing The Pitfalls During Scrum Adoption

Scrum is a roadmap that guides you to perform in project management with remarkable excellence as expected by all the stakeholders. Scrum master holds the responsibility to ensure that Scrum theory, rules and practices are enacted with perfect understanding. The high expectations of the Product Owner, Scrum team members, and organization make the Scrum adoption more challenging even for the experienced project managers but great results never come on their own; you need to do something different. Here, I share 5 major pitfalls identified for putting barriers to smooth performance of projects and Scrum Masters are:    1.Pitfall: Resistance to Recommended Changes: The resistance to change organizational culture and philosophy is the very first pitfall you come across on your Scrum journey. Sometimes, the extra efforts to fit Agile elements into the non-Agile framework make the task more complex. Accepting change is difficult and uncomfortable for the most; you see many stakeholders keeping distance from it. In other words, the majority of Scrum team members or the people concerned with the project in one way or the other poses rigidness when their comfortable routines are disrupted. Also, some experienced team members have a mindset “this is the way we have always done it and succeeded”.  Solution: The Practical Perspective:  So, change is the fundamental requirement for Scrum adoption; because you wouldn’t be planning for Scrum adoption if the changes were not required to improve. And, all the concerned members must be willing to accept the changes to improve the collective performance. As an efficient Scrum master, you must be able to perform as the change agent being proactive in resolving the resistances to change. The following 6 steps will help you overcome the resistance to Scrum rollout:  Explain the importance & need for the suggested changes  Actively listen to the members and incorporate their feedback into the process changes Highlight the benefits for winners and losers both while defining roles Use the key influencers to make the messages clear and accepted Measure the outcome & share the success to inspire the team members Identify and isolate the stubborn detractors    2.Pitfall: Lack Of Scrum Training Having trained and efficient project team is essential for successful Scrum adoption because Scrum is not a pre-scripted methodology; instead, it is a suggestive approach that delineates the processes and practices to keep the team members on the right track. The lack of training results in lack of commitment to Scrum adoption. The team members not comfortable in Scrum rules implementation tend to shift to old practices; they love to work in their own areas without much concern with others; such knowledge silos put diverse hurdles to your Scrum transition journey.    Solution: The Practical Perspective:  Scrum training should be a part of Scrum adoption strategy; especially, if it is being introduced in the organization first time. Giving the team members deep insights into Scrum methodology is a must for smooth scrum transition. Schwaber, in his book Enterprise and Scrum (2007), states that limited size maximizes the speed, content accuracy and communications; and the ideal team size is nine people. As a Scrum Master, you are responsible to help the team members hit the goals fixed in sprint meetings. To plan for the role specific Scrum training, you need to fix the following three parameters:  Numbers of people for Scrum training  The specific roles Requirement of certification On-site video training or classroom training      3.Pitfall: Distributed Team Scrum allows the team members to work from different locales but the distributed Scrum teams face certain major issues that retard the project’s progress:  Conflicting working hours and different time zones impair effectiveness and collaboration. Delay caused by lack of zero gap communication  Cultural differences & language barriers create confusions and misunderstanding  Team members have divergent preferences for technologies.  Solution: The Practical Perspective: As a Scrum Master, you need to assemble the distributed team for building trust and respect for each other. Try the following three experienced based hacks to solve the problem:  Make the communication fast, transparent and understandable to all despite the difference in working hours Give the team members ownership of their work to improve their commitment & motivation levels  Organize the camps to crush the boundaries of cultural and language differences    Present the clear picture of tooling, standards, and architecture design to keep everyone on the same track    4.Pitfall: Changes In Team To Manage Resourcing Problems Some organizations on the first time journey to Scrum adoption make massive changes in the team to manage the resourcing problems because of not knowing the hidden pitfalls. Although Scrum team members are trained to face the changes, still, frequent changes break the rhythm by disrupting the team’s velocity. Every member needs stability to perform; when the frequent role changes are applied, even the performing members quit. The replacement of old member with new member poses new problems for the other team members during the settling period. Assuming changes as the best feasible solution for improvement is a big pitfall in the journey of Scrum adoption.   Solution: The Practical Perspective: As a Scrum team leader, it is your responsibility to help and train every team member to speak the same language. How?  To retain the members, make sure every team member has Scrum training The required changes in Scrum team should be discussed with senior members but you need to have valid reasons  Keeping right person at right position is the responsibility of Scrum Master; it makes the individual’s performance evaluation more important   The task of making changes doesn’t end just by adding new member; you also need to track the cooperation between the new member and old members     5.Pitfall: On The Demand Tasks and Outcomes of Old Practices  Handling the unexpected urgent requests thrown by the client or the technical support team is one of the biggest challenges for the Scrum Masters. The other unexpected problem often faced by the Scrum Masters is the outcome of old practices even before they came into the picture. Some of such issues can be put into the backlog but many of these are needed to be handled at top priority. It harms the efforts to protect the team members from any interruption to let them drive in the secluded environment.  Solution: The practical perspective: Iterative product development is the part of Scrum approach. Respect the new demands and urgencies as the opportunities to test your capability. Whatsoever kind of problems you may face in managing on the demand tasks and bugs of old practices, you are expected to do it and you must do it the deliver the quality product ensuring 100% satisfaction to the client. Try the following 3 tricks to ease down the pressure:  Take the Bugs and urgent requests as the stuff for the superhero; and, you are indeed.  As Robin was important for Batman; you too need Robin to be called in for action.  Allocate sufficient time and resources separately to manage Bug Backlog and Product Backlog.   Conclusion:  On the way of Scrum adoption, you need to make several changes at diverse stages. Deep insights into Scrum principles, learning from problems, zero gap communication, effective team building and optimized use of tools/technology etc are the core strengths of successful Scrum Master to lead the team. The Certified Scrum Master (CSM) Certification and Professional Scrum Master (PSM) courses, separately designed for class room and team/corporate training modules give you knowledge, practical experience and confidence to get the best from Scrum adoption by incorporating the changes as the acceptable working culture transformation.   
A Practical Perspective On Addressing The Pitfalls During Scrum Adoption
Shubhranshu Agarwal
Rated 4.0/5 based on 20 customer reviews
A Practical Perspective On Addressing The Pitfalls During Scrum Adoption 268
A Practical Perspective On Addressing The Pitfalls During Scrum Adoption

Scrum is a roadmap that guides you to perform in project management with remarkable excellence as expected by all the stakeholders. Scrum master holds the responsibility to ensure that Scrum theory, rules and practices are enacted with perfect understanding. The high expectations of the Product Owner, Scrum team members, and organization make the Scrum adoption more challenging even for the experienced project managers but great results never come on their own; you need to do something different. Here, I share 5 major pitfalls identified for putting barriers to smooth performance of projects and Scrum Masters are: 






 

1.Pitfall: Resistance to Recommended Changes:

The resistance to change organizational culture and philosophy is the very first pitfall you come across on your Scrum journey. Sometimes, the extra efforts to fit Agile elements into the non-Agile framework make the task more complex. Accepting change is difficult and uncomfortable for the most; you see many stakeholders keeping distance from it. In other words, the majority of Scrum team members or the people concerned with the project in one way or the other poses rigidness when their comfortable routines are disrupted. Also, some experienced team members have a mindset “this is the way we have always done it and succeeded”. 


Solution: The Practical Perspective: 

So, change is the fundamental requirement for Scrum adoption; because you wouldn’t be planning for Scrum adoption if the changes were not required to improve. And, all the concerned members must be willing to accept the changes to improve the collective performance. As an efficient Scrum master, you must be able to perform as the change agent being proactive in resolving the resistances to change. The following 6 steps will help you overcome the resistance to Scrum rollout: 

  • Explain the importance & need for the suggested changes 
  • Actively listen to the members and incorporate their feedback into the process changes
  • Highlight the benefits for winners and losers both while defining roles
  • Use the key influencers to make the messages clear and accepted
  • Measure the outcome & share the success to inspire the team members
  • Identify and isolate the stubborn detractors 
     

2.Pitfall: Lack Of Scrum Training

Having trained and efficient project team is essential for successful Scrum adoption because Scrum is not a pre-scripted methodology; instead, it is a suggestive approach that delineates the processes and practices to keep the team members on the right track. The lack of training results in lack of commitment to Scrum adoption. The team members not comfortable in Scrum rules implementation tend to shift to old practices; they love to work in their own areas without much concern with others; such knowledge silos put diverse hurdles to your Scrum transition journey. 

 

Solution: The Practical Perspective: 


Scrum training should be a part of Scrum adoption strategy; especially, if it is being introduced in the organization first time. Giving the team members deep insights into Scrum methodology is a must for smooth scrum transition. Schwaber, in his book Enterprise and Scrum (2007), states that limited size maximizes the speed, content accuracy and communications; and the ideal team size is nine people. As a Scrum Master, you are responsible to help the team members hit the goals fixed in sprint meetings. To plan for the role specific Scrum training, you need to fix the following three parameters: 

  • Numbers of people for Scrum training 
  • The specific roles
  • Requirement of certification
  • On-site video training or classroom training   
     

3.Pitfall: Distributed Team

Scrum allows the team members to work from different locales but the distributed Scrum teams face certain major issues that retard the project’s progress: 

  • Conflicting working hours and different time zones impair effectiveness and collaboration.
  • Delay caused by lack of zero gap communication 
  • Cultural differences & language barriers create confusions and misunderstanding 
  • Team members have divergent preferences for technologies. 

Solution: The Practical Perspective:

As a Scrum Master, you need to assemble the distributed team for building trust and respect for each other. Try the following three experienced based hacks to solve the problem: 

  • Make the communication fast, transparent and understandable to all despite the difference in working hours
  • Give the team members ownership of their work to improve their commitment & motivation levels 
  • Organize the camps to crush the boundaries of cultural and language differences   
  • Present the clear picture of tooling, standards, and architecture design to keep everyone on the same track 
     



4.Pitfall: Changes In Team To Manage Resourcing Problems

Some organizations on the first time journey to Scrum adoption make massive changes in the team to manage the resourcing problems because of not knowing the hidden pitfalls. Although Scrum team members are trained to face the changes, still, frequent changes break the rhythm by disrupting the team’s velocity. Every member needs stability to perform; when the frequent role changes are applied, even the performing members quit. The replacement of old member with new member poses new problems for the other team members during the settling period. Assuming changes as the best feasible solution for improvement is a big pitfall in the journey of Scrum adoption.  

Solution: The Practical Perspective:

As a Scrum team leader, it is your responsibility to help and train every team member to speak the same language. How? 

  • To retain the members, make sure every team member has Scrum training
  • The required changes in Scrum team should be discussed with senior members but you need to have valid reasons 
  • Keeping right person at right position is the responsibility of Scrum Master; it makes the individual’s performance evaluation more important  
  • The task of making changes doesn’t end just by adding new member; you also need to track the cooperation between the new member and old members  
     


5.Pitfall: On The Demand Tasks and Outcomes of Old Practices 

Handling the unexpected urgent requests thrown by the client or the technical support team is one of the biggest challenges for the Scrum Masters. The other unexpected problem often faced by the Scrum Masters is the outcome of old practices even before they came into the picture. Some of such issues can be put into the backlog but many of these are needed to be handled at top priority. It harms the efforts to protect the team members from any interruption to let them drive in the secluded environment. 

Solution: The practical perspective:

Iterative product development is the part of Scrum approach. Respect the new demands and urgencies as the opportunities to test your capability. Whatsoever kind of problems you may face in managing on the demand tasks and bugs of old practices, you are expected to do it and you must do it the deliver the quality product ensuring 100% satisfaction to the client. Try the following 3 tricks to ease down the pressure: 

  • Take the Bugs and urgent requests as the stuff for the superhero; and, you are indeed. 
  • As Robin was important for Batman; you too need Robin to be called in for action. 
  • Allocate sufficient time and resources separately to manage Bug Backlog and Product Backlog.
     

Conclusion: 

On the way of Scrum adoption, you need to make several changes at diverse stages. Deep insights into Scrum principles, learning from problems, zero gap communication, effective team building and optimized use of tools/technology etc are the core strengths of successful Scrum Master to lead the team. The Certified Scrum Master (CSM) Certification and Professional Scrum Master (PSM) courses, separately designed for class room and team/corporate training modules give you knowledge, practical experience and confidence to get the best from Scrum adoption by incorporating the changes as the acceptable working culture transformation. 

 

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

Is The Scrum Master(CSM) Certification Worth It?

Being new to Scrum, you have browsed enough about Certified Scrum Master (CSM) from the Scrum Alliance website. But do you know if the CSM certification is the right choice for you? Let us help you understand the value of this certification. Firstly, why do you even need a certification? We need it to enhance our resume by having an additional skill set. Secondly, why CSM? Because this certification will provide a baseline knowledge of the Scrum process and fundamental aspects of the Scrum framework. Scrum is a leading Agile technology used by many companies around the world to tackle complex projects. Ken Schwaber and Jeff Sutherland developed the Scrum and the Scrum guide. The Scrum is not a technique or a process but a lightweight and simple framework to address complex problems of a project and creatively delivering a high value product. There are various components within a Scrum framework like the Scrum Team and its associated roles and responsibilities. The Scrum team consists of:- 1. The Product Owner The major responsibility of the Product Owner is to maximise the value of the product and work of the development team. Additional duties include managing the Product Catalogue. 2. The Development Team The development team consists of self-organising professionals which turn Product Catalogue into a Product increment at the end of each Sprint. 3. The Scrum Master The Scrum Masters make sure that the Scrum team is abiding by the Scrum Theory and its rules. And this is where our CSM certification comes into picture. A Certified Scrum Master helps the project teams understand the Scrum and properly use its functionalities. CSM help the Scrum Team to work together and learn about Scrum’s values, practices and applications. Today, the Agile Software Development methodology is taking the world by storm and this certification sets you apart and makes you more noticeable. From a knowledge acquiring perspective, the basic Scrum training is sufficient but if you intend to play a role of Scrum Master then CSM certification will definitely validate you. You need to pursue a CSM course from a Certified Scrum trainer (CST), learn all about Scrum, attend a CSM course conducted by Scrum Alliance Authorised Trainer, complete the course and take up an online CMS test. After you successfully pass the CSM exam, you will get your License Agreement. Benefits of Scrum Master Certification 1. Obtaining core knowledge of Scrum Even if you don’t know much about Scrum, the CSM certification will definitely help you build a solid base of Scrum knowledge and understand the concepts of Scrum framework. 2. Adopting Agile mindset Scrum being an Agile methodology, training and certifications will help people in your team embrace the Agile practices. And having a consistent Agile mindset in a team will lead to lesser disagreements, better team collaboration and ultimately delivering successful projects. 3. Staying marketable All industries adopting Agile practices will have excellent career opportunities for candidates with Scrum certification. This certification will prove that you have an Agile mindset and core knowledge of Agile practices. 4. A Plus for your organisation If there are skilled and proven Agile professionals in an organisation, the management might benefit from it by adopting Agile methodology as it will effectively influence all the aspects of business like people and processes. 5. Exposure to Scrum Experts Being a certified Scrum Master, you can join a community of recognised Scrum experts, practitioners and trainers. This global network will give you exposure to deepen your Scrum knowledge, acquire guidance whenever necessary and also enable you to provide solutions to others problems.
Is The Scrum Master(CSM) Certification Worth It?
Author Image
Rated 4.0/5 based on 20 customer reviews
Is The Scrum Master(CSM) Certification Worth It?

Being new to Scrum, you have browsed enough about Certified Scrum Mast... Read More

From Creation To Execution: How Sprint Backlog Helps Scrum Teams

Scrum is an agile way to accomplish the project, usually in software development. In Scrum, artifacts are the key information providers that are designed specifically to enhance transparency of key information required to ensure that the Scrum teams are successful in delivering a ‘Done’ increment. The Scrum Process Framework defines 3 essential artifacts:Product BacklogSprint BacklogProduct IncrementIn this article, we are going to see everything in detail about Sprint Backlog in Scrum. While being a simple concept, it is misunderstood by many people. This article will clear up the confusion and explain clearly what the Sprint Backlog is and how to use it.What is a Sprint Backlog?The Sprint Backlog is a set of all the product backlog items chosen for the current sprint, plus a plan for delivering the product increment and achieving the sprint goal. This plan takes the form of all the work required to get the backlog items to “Done” in that sprint.The following video will explain how to create your first sprint backlog.The Sprint Backlog is produced by the team in the Sprint Planning meeting. It is an outcome of that meeting and the Sprint Planning meeting should not conclude until the team has produced the Sprint Backlog in some form (though it can actually change after that, as I’ll explain below).How to create a Sprint BacklogSprint Backlog is the output of the sprint planning meeting with the participation of every team member in the Scrum team. The process is as follows:There is another final step that many teams don’t do (and don’t know about!). As of the latest version of the Scrum Guide, the team must also add a continuous improvement item to the Sprint Backlog. This is an interesting and important change and will really encourage teams to take continuous improvement seriously (rather than as an afterthought). Make sure you don’t forget to do this with your teams!Once produced, the team should make sure that the Sprint Backlog is visible to everyone. This ties in with the Scrum pillars of transparency, inspection, and adaptation. It provides a clear, real-time view of the progress of the team in completion of the sprint goal and Product Increment.How does the team plan the work?Many people might now be wondering what a “plan” is. The answer is, it can be anything that the team comes up with to complete the product increment and complete the items in the Sprint Backlog. Some people do this by breaking them into tasks, which are estimated in hours. That’s fine, though it’s not mandated by Scrum.Each team should find its own best way to plan and arrange the work. Scrum guide is very clear on this matter:The figure below shows an example of how the development team plan the work to be done in the sprint for each user story.So the Sprint Backlog will start off with some Product Backlog Items. The team can then add tasks, subtasks, designs, diagrams, whatever they like to the Sprint Backlog, as part of coming up with a plan to complete the work.Can you change the Sprint Backlog?Some people believe that the Sprint Backlog cannot be changed during the Sprint, that it is locked down when the sprint starts. This is totally untrue!The Scrum Guide is very clear on this point. It saysThe key point is that only the Development Team can change the Sprint Backlog since it is their artifact. Conversely, the Product Owner owns the Product Backlog and is the only person who can change that.So the team should add, remove, and change things in the Sprint Backlog as the sprint progresses, work is completed, new facts are discovered, and so on.Keep in mind though that the changes should be discussed with the Product Owner (though they don’t need approval from them), and that they should still reflect the team’s understanding of the sprint goal. Changing the Sprint Backlog so that it no longer matches with the sprint goal is a serious decision that would need the agreement of the product owner, and could be grounds for canceling a sprint.Do we have to use tasks?Another myth is that the team must break the stories down into tasks as part of moving them into the Sprint Backlog in Sprint Planning. This is also not true! The Scrum Guide does not include the word “task” anywhere. The team finds its own best way of completing the work.What is the output of a sprint backlog?The output at the end of a sprint is a product increment (PI). A product increment is the sum of all the Sprint Backlog items which are “Done” at the end of the sprint, plus the outputs of all the previous increments in previous sprints.
From Creation To Execution: How Sprint Backlog Helps Scrum Teams
Author Image
Rated 4.0/5 based on 1 customer reviews
From Creation To Execution: How Sprint Backlog Hel...

Scrum is an agile way to accomplish the project, usually in software d... Read More

How Justified Is It To Map The Project Manager Role To The Scrum Master Role?

For an entrant in the IT industry, the Project Manager and the Scrum master are two similar roles. Absolutely, this is not a fact. Both roles are very separate and distinct from each other. Both can be moulded into different approaches in the project. Most probably we can say Product owner role is closely aligned to the Project manager role. Apart from that, it is important to know the differences between the Scrum master and the Project manager, to find how they complement each other in large-scale projects. Let’s figure out a big difference between two. The Scrum master is a coach and facilitator. The Project Manager is a leader, decision-maker and is responsible for managing the project, resources and scope of business requirements. Sometimes, the project manager has to make sure whether the project is lined up with the necessary business requirements or not, whereas the scrum master has to look after one project team. Also, scrum master has to be a mediator between the project and the customer. Scrum Master as a Coach, Mentor, and Guardian:  The Scrum Master supports the product owner in managing the teamwork, coaches the team and ensures that the team is properly aligned to the Scrum process. The Scrum Master manages the Scrum process, ensures its correct implementation and increasing scope of its benefits throughout the project. The highly responsible entity in the project can be identified as a Product Owner (PO). They have to maintain the product backlog and ensure that the product fits with the business requirements. In case of any changes in the product, the PO has to adjust and reprioritize the current product backlog to fit these changes and maneuver the project. This is a tedious task for the Product Owner. So, the Scrum Master is there to play a consultant role and take care of the project from all perspectives. The Scrum Master guides the PO on how to manage the teamwork with the use of product backlog and the sprint planning and meetings.Next, you might be thinking, what is the role of the Project Manager in Scrum? If you know the transition from Waterfall to Agile, you might think that the title ‘project manager’ is just shifted to the title ‘scrum master’. However, the project manager’s responsibilities cannot be directly converted to a scrum master role. When you transit from traditional approach (Waterfall model) to Agile, the responsibilities of a project manager are distributed among the variety of team members. Some responsibilities go to the program manager, some to the product owner, to the scrum master and some to the remaining team. On the other hand, switching from waterfall to agile is not an easy process. Let’s see how the project manager and the scrum master roles differ from each other: Project manager: Managing the finance related issues budget Reporting to business leaders on the project progress Task allocation Risk management Focusing on processes Prioritizing the project related features Coordinating with other teams if required Scrum Master: Helps the team when needed Removes impediments Guides the product owner on the project Facilitates the daily scrum and sprint planning Helps teams to speed up the processes Monitors the sprint progress Promotes team discussions Motivates the team SM acts as a cement to bind the team together Project Manager(PM) vs Scrum Master(SM):  There is a time or place for a project manager in the large projects. The Project manager can cover multiple teams and can work with other dependent teams as well. PM can coordinate with multiple teams, help them to meet project timelines and collaborate when resources are required. Great teams rely on the Scrum masters to get their work done within a time limit. You might as well say that being a Scrum Master is a kind of art. All depends on the sprint planning and release planning processes which give scientific clarity to SM in ensuring that the team is able to execute the amount of assigned work in a right way. Ultimately, the Scrum Master role is proved to be a deciding factor in a successful project. It plays a very different role if compared to the Project Manager. Product Owner defines an Agile project and it is developed by the team. The Scrum Master facilitates and ensures that the team is following Agile processes in a proper manner. It sounds very simple but it needs particular skillsets and the right person to make it work.
How Justified Is It To Map The Project Manager Role To The Scrum Master Role?
Author Image
Rated 4.0/5 based on 20 customer reviews
How Justified Is It To Map The Project Manager Rol...

For an entrant in the IT industry, the Project Manager and the Scrum m... Read More