Course Discount

Search

Daily Stand-up Dos and Don’ts

Anyone who has been part of a Scrum team knows the importance of the Daily Stand-up, the 15 minute meeting that is held at the end of each day. This is a vital part of the Scrum process- as everyone gets updated on information that is needed for coordination. During this meeting, each team member briefly shares what they have completed, and describes any obstacles they have faced the previous day. A Daily Stand-up promotes transparency and teamwork, smoothens work processes and helps to minimize problems. While this meeting is of critical importance to successful sprint outcomes, here are some things that you MUST keep in mind: Timebox your meeting duration! Without a specific timebox in place, a Daily Scrum meeting can drag on and actually waste the time of the team. A typical daily meeting should get over in 15 minutes- but larger teams could agree upon a longer duration. The idea is to stop when that time runs out, and keep all discussions short and to the point. Don’t hide issues. If there are any issues with the work that you are doing, please make sure that you mention them. Nothing is more annoying than an ongoing problem which comes to light only toward the end of the sprint. If shared at the outset, problems can be tackled and solved by the team.  Don’t postpone a meeting. Daily interaction lays the foundation for a successful Scrum team. If meetings are postponed, project completion may just get postponed too. Ideally, the meeting should happen at the same time each day. Meetings that are held in the morning, for instance, could set the mood for the work that has to be done during the day. Start the meeting on time: Ensure that the Stand-up starts on time, even if some development team members are missing. A delay of even five minutes, when multiplied by the number of team members, counts for a lot of potential work wasted. Peer to peer interaction. All interactions should be on a peer-to-peer basis, and not in the form of a status report made to the Scrum Master. Teamwork is always emphasized in Scrum, and the team should communicate well with each other. Questions asked and answered: There are three questions that are sought to be asked and answered by each team member.  What did you complete yesterday? What will you do today? Did you find any impediments in your way? Answers should be concise and precise. Stay focussed: The Scrum Master must keep the team focussed on answering the three questions, and not straying into a random discussion on, say, a particular issue that has been raised by a member. This can remove the focus for the entire team, and will result in the time limit getting out of hand. A Scrum team that works well together, and understands the principles of Agile in a deeper context, can achieve unprecedented and outstanding results. Make sure your Scrum team follows these simple principles and stays on track!
Rated 4.0/5 based on 20 customer reviews

Daily Stand-up Dos and Don’ts

791
Daily Stand-up Dos and Don’ts

Anyone who has been part of a Scrum team knows the importance of the Daily Stand-up, the 15 minute meeting that is held at the end of each day. This is a vital part of the Scrum process- as everyone gets updated on information that is needed for coordination. During this meeting, each team member briefly shares what they have completed, and describes any obstacles they have faced the previous day. A Daily Stand-up promotes transparency and teamwork, smoothens work processes and helps to minimize problems.

While this meeting is of critical importance to successful sprint outcomes, here are some things that you MUST keep in mind:

Timebox your meeting duration! Without a specific timebox in place, a Daily Scrum meeting can drag on and actually waste the time of the team. A typical daily meeting should get over in 15 minutes- but larger teams could agree upon a longer duration. The idea is to stop when that time runs out, and keep all discussions short and to the point.

Don’t hide issues. If there are any issues with the work that you are doing, please make sure that you mention them. Nothing is more annoying than an ongoing problem which comes to light only toward the end of the sprint. If shared at the outset, problems can be tackled and solved by the team.

 Don’t postpone a meeting. Daily interaction lays the foundation for a successful Scrum team. If meetings are postponed, project completion may just get postponed too. Ideally, the meeting should happen at the same time each day. Meetings that are held in the morning, for instance, could set the mood for the work that has to be done during the day.

Start the meeting on time: Ensure that the Stand-up starts on time, even if some development team members are missing. A delay of even five minutes, when multiplied by the number of team members, counts for a lot of potential work wasted.

Peer to peer interaction. All interactions should be on a peer-to-peer basis, and not in the form of a status report made to the Scrum Master. Teamwork is always emphasized in Scrum, and the team should communicate well with each other.

Questions asked and answered: There are three questions that are sought to be asked and answered by each team member.  What did you complete yesterday? What will you do today? Did you find any impediments in your way? Answers should be concise and precise.

Stay focussed: The Scrum Master must keep the team focussed on answering the three questions, and not straying into a random discussion on, say, a particular issue that has been raised by a member. This can remove the focus for the entire team, and will result in the time limit getting out of hand.

A Scrum team that works well together, and understands the principles of Agile in a deeper context, can achieve unprecedented and outstanding results. Make sure your Scrum team follows these simple principles and stays on track!

Usha

Usha Sunil

Blog Author

Writing is Usha's hobby and passion. She has written widely on topics as diverse as training, finance, HR and marketing, and is now into technical writing and education. She keeps an interested eye on new trends in technology, and is currently on a mission to find out what makes the world go around.

Join the Discussion

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

Suggested Blogs

Difference Between Agile and Scrum

Agile describes a set of guiding principles that uses iterative approach for software development, while Scrum is a specific set of rules that are to be followed while practicing the Agile software development. Agile Agile management represents various software-development methodologies that have been influenced by iterative and incremental development, which includes Extreme Programming (XP), Rational Unified Process (RUP), Scrum, and others. Agile process or methods provide an environment where there is constant evolution in requirements and evolution as a result of collaboration between self-organising cross-functional teams. Agile methodologies foster a disciplined project-management approach that encourages a set of best practices, allowing a rapid delivery of high-quality software and enhancing a business approach, which aligns development with the customer needs. The Agile methodologies stand in contrast to the traditional waterfall methodology, where all the requirements are initially analysed and documented before the development begins. While in Agile approach, requirements are like the actual software-development advances within each iteration. This approach provides flexibility in accommodating changes in the requirements and priorities of the business. Also known as Manifesto for Agile Software Development, the Agile Manifesto is a formal declaration of 4 key values and 12 principles supporting an iterative approach to software development. The Agile development methodology enables assessment of project direction throughout the development lifecycle. This is achieved through regular iterations, and when revaluation is done at every iteration, it greatly reduces the development costs and time. Agile helps the companies to build the right product. Benefits of Agile include as follows: Benefits the Customers In the traditional waterfall model, the high-value features are developed and delivered in longer cycles compared to the Agile approach, which enables delivery within short cycles. This enables the vendors to be more responsive to the development requests of the customers. Benefits the Vendors Adopting Agile benefits the vendors by having an improved customer satisfaction and customer retention, leading to more customer contacts through positive references. The Agile allows the vendor’s focus to be on the development effort of high-value features, decrease the overheads, and improve efficiency. Quality With Agile development, there is a regular inspection of the working product, with testing integrated at every iteration, as it develops throughout the lifecycle. This in turn retains the quality of the product and also allows the product owner to make necessary adjustments whenever a quality issue arises. Visibility Agile methodology is a collaborative approach that encourages active user participation throughout the product development. This gives an exceptional and clear visibility of the project’s progress and product development to the stakeholders. Cost Control Agile development process has fixed timescale where the requirements emerge and evolve as the project progresses and the product is developed. This enables a fixed budget. Risk Management In Agile methodology, small incremental releases are made visible to the product owner throughout the development cycle, which helps identify issues at an early stage, and it makes easier to respond to change, if any. Agile development ensures clear visibility, which allows necessary decisions to be taken at the earliest possible opportunity. Scrum Scrum, on the other hand, is a subset of Agile. A Scrum is a simple and flexible Agile methodology for software development. The Scrum is not a technique or a process but a lightweight and simple framework to address complex problems of a project and deliver a high-value product creatively. The major distinguishing attributes of Scrum are as follows: Simplicity The development in Scrum is done in sprints, which are 1, 2, and 3 weeks in length. The Scrum team consists of: Product Owner: The major responsibility of the product owner is to maximize the value of the product and work of the development team. Additional duties include managing the product catalogue. Scrum Master: The development team consists of self-organising professionals who turn the product catalogue into product increment at the end of each sprint. Development Team: The Scrum Masters make sure that the Scrum team is abiding by the Scrum theory and its rules. Flexibility In the traditional waterfall model, when the business and technical requirements are documented and detailed, it results in endless documentation. The Scrum makes use of user stories to describe the functions needed to be developed. A tool called Pivotal Tracker is used to store these user stories in a backlog. If a change needs to be made or a need arises to add to the user stories, in that case the team can adjust as early as the next sprint. This allows the business to change their minds and the development team to be flexible enough to adjust to those changes. The ability to accommodate change is a powerful attribute of the Scrum methodology. Communication and Collaboration In Scrum methodology, the communication between business users takes place on a daily/weekly basis according to the sprint schedule. This close communication and collaboration is a crucial factor, promoting the success of the Scrum methodology. The Scrum team achieves collaboration in following ways: The Product Owner, the Scrum Master, and the development team work closely on a daily basis. Sprint-planning meetings are conducted, which allows the development team to organise its work based on the knowledge gathered from the business priorities. Conducting daily scrum meetings where the development team can account for the work completed, its future prospects, and deal with issues if any. Conducting sprint reviews allows the team members to evaluate their former work by recommending better practices with every sprint. There are more details on Agile & scum differences
Rated 4.0/5 based on 8 customer reviews
2957
Difference Between Agile and Scrum

Agile describes a set of guiding principles that u... Read More

How To Become A Certified Scrum Master- Exam Preparation And Guidance

Introduction to Certified Scrum MasterWho is the Scrum Master?In one of our previous blog posts, Rumesh Wijetunge shared some relevant insights on the role of Scrum Master. Wearing different hats, coach, enabler, facilitator, team leader, problem-solver, s/he is in charge of giving right directions to team members so that they reach objectives. First promoter of Agile mindset, values and principles, the Scrum Master uses the Scrum framework to help a team in understanding, working on, and achieving a common goal.Responsibilities of the Certified Scrum MasterIt is expected from the Certified Scrum Master to promote an Agile way of working and to lead Scrum implementation in order to improve the team's overall performance. It implies these activities:Teaching Agile values and principles and ensuring they have been understood and adopted by the Scrum Team, and even by the whole organization if possible (and relevant)Implementing the Scrum framework so that it fits  the needs expressed by the Scrum TeamListening, observing and reflecting on how the Scrum Team is reacting to first changes, then selecting and adapting Scrum elements accordingly.Protecting Team Members from any interference or troubles that make them losing focus on their primary workAnticipating, identifying and removing any impediments, and coaching Team Members to learn to solve these situations by themselvesHelping the Product Owner to manage the Product Backlog so that time-to-market is reduced and every increment brings value to end customersActing as a Servant LeaderRequirements to become a Certified Scrum MasterGetting some basic knowledge about the Scrum framework is a nice-to-have prerequisite. However, the first mandatory step is to attend a two-day CSM course conducted by a Certified Scrum Trainer® (CST®). This course will prepare you well for the CSM exam by delivering insights about how to organize and support a Scrum Team. The final step is easy: you need to accept the License Agreement and update your Scrum Alliance membership profile. Why you should be a Certified Scrum Master? Becoming a Certified Scrum Master is one way to expand your career opportunities. Indeed, Agile is spreading everywhere in organisations, in all industries. Strongly correlated, software and digitalization are eating the world, so the need for Scrum Masters in software development is increasing. It is also the beginning of a long journey: it enables you to engage with other Scrum practitioners all over the world, to share best practices, to solve common issues and to promote Agile values and continuous improvement.Besides, this certification offers you to learn foundation of Scrum and scope of the role of Scrum Master. And because it is delivered by Scrum Alliance , this is a very valid proof of your Scrum knowledge.What do I need to do to become a CSM? A true belief and strong interest in Agile philosophy will help for sure to get knowledge, to practice efficiently and to stand out among Agile practitioners. Nonetheless, passing the Scrum Alliance certification for Scrum Master lies mainly in learning Scrum fundamentals and attending to the two-day training (see above paragraph c.)a. Why CSM over PSM: Best Scrum Master certification1. Scrum.org courses- Price, Renewal, Pros, and ConsPrice: It includes exam fees but depends on content, duration, trainer and location:US: $1500Europe: 1500 eurosIndia: INR 26,000Renewal: No expiration (lifetime certification)Pros:Course content is officially designed by Scrum.org so all teachers deliver same content. It implies that Scrum.org selects qualified instructors and ensures students learn the same core content.Exam can be taken without attending course - Exam fees are $150There is an online free assessment exam for practisingCons: Exam is much harder than CSM. It requires experience, and deep theoretical knowledge2. Difference between the Scrum Alliance and Scrum.org coursesThe main difference lies in the fact that Scrum.org provides standard curriculum and course content, while training conducted to become CSM depends on individual trainers experience, opinion and knowledge.CSM Certification TrainingSyllabus of Scrum Master certification Scrum Alliance provides a list of selected resources to learn the Scrum framework. People who want to become Certified Scrum Master are invited to read articles from experts like Mike Cohn or Steve Denning, or from other members. One specific advantage with Scrum Alliance lies in their elearning series: a dozen short videos introduce Scrum Theory and Values, Scrum Roles, Scrum Events and Scrum Artifacts. Besides, it is strongly recommended to read those references:the Scrum Guide by Ken Schwaber and Jeff Sutherlandthe Scrum Primer by Pete Deemer, Gabrielle Benefield, Craig Larman and Bas Voddethe Do Better Scrum by Peter Hundermark Not mandatory but relevant to go further, Scrum: A Pocket Guide by Gunther Verheyenand Software in 30 days by Ken Schwaber.Exam and Certification InformationScrum Alliance courses- Price, Renewal, Pros and Cons The CSM course is a two-day (16 hours) course delivered by a Certified Scrum Trainer® (CST®).There is no standard fee, so the price can vary depending on the context: trainer, content, location, date ; the usual range is from 1000 to 1500 euros (or from 1150 to 1750 dollars).It includes two attempts to take the CSM exam and a two-year membership to the new Scrum Alliance® community. Those two attempts have to be used in the next 90 days after attendees receive the welcome email to pass the test. Beyond this duration, they will be prompted to pay $25 to take the exam. Certification is valid for two years, then it requires to be renewed after that.Besides, attendees to the CSM course will be granted with 14 PDUs credits: 10 PDUs in Technical Project Management and 4 PDUs in Leadership. What can be considered as a drawback is that there is no standard content course. Course materials are made by individual trainers, which implies it can be limited by their experience and opinion.Cost of the Scrum Master CertificationThere is no specific cost for the Certification: fee is included into the CSM two-day course. The structure of the examThe exam is composed of 35 multiple-choice and true/false questions. At least 24 correct answers are required to pass the exam, and there is no time limit to answer those questions. Topics covered in the CSM exam As this exam requires to demonstrate an understanding of the key Scrum elements, it covers general Scrum knowledge, Scrum roles, Scrum meetings and Scrum artifacts.Here are the Sample questions of CSM exam 1) What does NOT belong to the agile manifesto's main pillars?Individuals and interactions over processes and toolsWorking software over comprehensive documentationProcesses over peopleCustomer collaboration over contract negotiationAnswer: Processes over people2) How should work be allocated to the team in an Agile project?The Team Leader (ScrumMaster) should allocate specific tasks to individualsTasks should be randomly allocated to team members, using Planning PokerTeam members should self-select tasks appropriate to their skillsThe most complex tasks should be allocated by the Team Leader (ScrumMaster)Answer: Team members should self-select tasks appropriate to their skills3) What are the disadvantages of the classical waterfall model? (Select the best alternative)A)  End-Product has to be fully anticipated beforehandB)  Some requirements are implemented as defined in the beginning of the project, and yet they are not really needed by the customerC)  Each phase is strictly separated- A- A, B- C, B- A, B, CAnswer: A, B, C4) Who is responsible for prioritizing the product backlog?- Product Owner- Project Manager- Lead Developer- Business AnalystAnswer: Product Owner5) What kind of software development projects can be executed by Scrum Project Management Framework?- Complete software packages- Customer projects- Sub-systems, components or parts of bigger systems- All kinds of software development projects- None of the given answersAnswer: All kinds of software development projectsSalary of the Certified Scrum MasterSalary per year Junior Senior US$82,000 - 105,000$105,000 - 120,000Europe38,000 - 55,000 €55,000 - 75,000 €DubaiAED 25,000AED 35,000IndiaRs. 731,983Rs. 1,424,186
Rated 4.5/5 based on 2 customer reviews
5337
How To Become A Certified Scrum Master- Exam Prep...

Introduction to Certified Scrum MasterWho is the S... Read More

How to Transition From Project Manager to a Scrum Master

Scrum Masters and Project Managers are not the same roles. I am going to talk about moving from a Project Manager role to a Scrum Master. Why do we need to talk about it? Because many people think they are the same thing with different artifacts or different language being used. They aren’t.You may be considering a change of roles from Project Manager to Scrum Master. You may be forced into such change as your organization is subjected to an Agile transformation. You may find yourself juggling both the roles and struggling with the competing agendas embedded in the two roles.  What I want you to get from this essay is an appreciation of the differences between the Project Manager and Scrum Master and some ideas about how the role of the Project Manager fits into Agile.The benefits of being a great Scrum MasterThe first and obvious answer is the huge drive to have an Agile delivery capability in almost every organization in the world. It’s a hot new job and having these skills and experiences to improve your employment prospects as you look for work.While there are still more Project Manager jobs than Scrum Master jobs on the jobs boards, the number of Scrum Master and similar jobs continues to grow, while the number of Project Manager jobs appears to be steady, and perhaps even shrinking in some markets.Additionally, more and more Project Manager roles require an understanding of and experience in Agile development and management methods, as project performance seems strongly correlated with the use of Agile methods.So, getting good in-depth experience in Agile working is an important step in your professional development, especially if you are a Project Manager involved in technology projects. Doing a job as a Scrum Master is an excellent way to immerse yourself in Agile world and learn the skills, knowledge, and behavior that will help you be a great manager and leader later in your career.But wait! There’s more.Many, many, many people who adopt the role of Scrum Master find their way into a new and fulfilling career. Scrum Masters and related coach type roles are inherently fulfilling for many people. Scrum Masters report a huge sense of satisfaction in being valuable team members and helping those around them grow in capability and deliver successful outcomes.  Becoming a Scrum Master may be the beginning of a whole new career track for you.Why to switch from Project Manager to a Scrum Master roleLet us have a look at the three key areas from where you can make out the decision on why the Scrum Master can be a great alternative for a typical project management environment:The potential to focus on the current taskDuring a project, the Project Manager has to discuss with the Client team and the Developer team to ensure the project goals. Being a Project Manager, it is very time-consuming and burdening as they have to ensure that the team is adhering to their own high standards.Whereas, Scrum Masters set priorities and target depending on sprint cycle. Scrum Master always keeps an eye on the active sprint. Scrum framework reduces distractions and the stress of achieving several different goals simultaneously. Being a Scrum Master, it is very easy to manage the projects as the Scrum framework allows to-Narrow the focusMeasure the results at each SprintGive the fastest deliveryDifferent ways to manage projectsMostly Project Managers spend much of their lives in:Collecting resourcesVerifying the resourcesEnsuring that everybody has what they wantFacilitating communicationScrum methodology allows to solve queries by communicating with the team members. The team can resolve issues without the help of the Scrum Master and the issues which can’t be solved by the team can be raised during ‘Daily Scrum’. Scrum meetings last for 15 minutes. In those 15 minutes, the Scrum Master will come to know the project status and the roadblocks hindering the project success.The Scrum method allows the teams to carry out communication by:Allowing the teams to communicate to solve issues internallyThe Scrum Master can get project status update in 15 minutes of Scrum meetingThe Scrum Master gets the things that can keep the project runningPrepare for what the client likesClients keep project goals like high ROI (return on investment), quality, reliability and higher lead conversion rates, before approaching any company. Along with the goals, clients want to know about the process and a collaborative relationship.Project manager manages the timeline, limitations, and achievements. They decide on the future aspects of the processes. This method is difficult to manage and works smoothly through changing priorities and resources.  On the flip side, in Scrum method goals, priorities, and resources can be set during Sprint planning. Since Sprint lasts for 2-3 weeks, they set target within a timeframe which allows them to accomplish the target in time and with less errors. The Scrum Master, developers, and teams, all are allowed in the Scrum planning process, so everyone can discuss the process for achieving the client’s requirement. This method allows the client to get the regular status of the project and allows us to create an awesome productTips for transitioning from Project Manager to a good Scrum MasterIf you are a Project Manager entering the Agile world, you probably have the reasons to switch from the Project Manager role to the Scrum Master. You already have a definition of a Project Manager’s role in your head.  It is probably based on the PMI definitions around planning, monitoring, controlling and closing a project. Maybe there is something about the accountability for the outcomes, and using the project management industry’s established methods and practices. That’s all good and a great set of knowledge to have.The best resources to learn what is a Scrum Master, what a Scrum Master does are from reading the Scrum guide and from talking to people who have experience in the role, most of whom are very generous with their time and enthusiastic about sharing knowledge and experiences.  The actual description of the Scrum Master role is very simple, clear and succinct.  The stories you get from the experienced people will help you see the complexity of those clear guidelines applied in complex situations.The most important contributions of the Scrum Master role are enabling the team by helping them unlock value from executing the Scrum framework well, being collectively disciplined and organized as a team, and in spending time and energy clearing impediments to the team’s progress.A Project Manager playing a Scrum Master role for the first time, would not be the first person to make the mistake of thinking the role is all about the process control. But it isn’t. It is an enabler role.As a Project Manager, you might hold accountability for creating a plan and for publishing progress reports against that plan to the Stakeholders.  As a Scrum Master, you are accountable for enabling the team to produce a plan and publish progress reports.You may end up being the person who grabs progress data and publishes it, but you are doing it in service to the team rather than to service your own delivery accountabilities. You may have very little to do with publishing progress reports. Anybody on the team or the team collectively can perform that task.Your job is to help the team understand the need for progress reports, to help them find useful methods to get the job done, and to find the discipline to consistently do the job well.The Scrum Master is advised to use the Scrum framework as a tool to inspect and adapt to both the product demands and the capabilities of the team. As your team learns new things, they will prioritize the opportunities and make changes according to the way they operate.  You can help them identify the opportunities and implement them. There are several easy ways to access methods and tools to solve a variety of problems out there, both inside and beyond the Agile toolkits, but the team should not settle for any obvious best practice. Good practices should be used, not to be settled. Always seek better.We have already looked at how your accountabilities change, but a Scrum Master won’t succeed unless they approach the work with the right attitude.  Each team is different, so you should always assess the expectations of the team and the role you play. Also, you will be able to bridge any gaps by using some fair core values based behaviors that people expect from a Scrum Master.Servant leadership — the watchwordThe Scrum Master role is a Servant Leader role. The Servant leaders seemingly face a conundrum that ‘how do I serve and lead at the same time’.  The answer is that you lead some things with authority based on the expertise and knowledge. You also step aside and let others manage their things based on authority, experience, and roles.For example the Product Owner in Scrum has positional authority on the backlog (that is supposed to be based on knowledge, but is also deeply positional.)You are expected to bring an authority, based on knowledge and experience around the  Scrum, team and system dynamics, and it should be valued by the team. To do this effectively you need to follow some tips for transitioning to the Agile Project Manager.Know your stuffKnowing only what to do leads to cargo cult practices and doesn’t engender a learning organization that continually evolves.  How and why Scrum worksWhy does each of the attributes of Scrum bring value?What problems do they solve and why does that part of Scrum work the way it does?You also need to know why Scrum parts work more effectively when it is executed integratively.New Scrum teams: Start with a Big Bang?If you are working with a team which is new to Scrum or Agile practices, as an effective Scrum Master you should also have some expertise in the way you roll in or implement the new Agile ways of working. Should you do a big bang implementation of Scrum, or roll in one practice at a time? Which one should you start with? Which next?The answer will depend on the circumstances of the team and the Scrum Master should have enough experience and wisdom to have an opinion that the team value because ideally, the teams should be deciding how to roll in the practices.Ask outcome-focused questionsAn important operating method for Scrum Masters is to highlight issues and ask questions.  When and if people express interest in the topic being raised, the Scrum Master may then offer advice and suggestion options. Collectively, the team should engage in the issue and decide what to do.  If the Scrum Master feel that the teams are going to make a mistake, you think about whether the mistake will be small enough to be safe and whether the team will take lessons from the failure. If you see risks, raise them and try to influence the down team with the different paths.As you interact with the team, your experience and advice should become more valued by the team over time.  You should build a consistent track record of helping them become a more successful team. You should not have to try to force change, although sometimes you will feel like you do, and some even rarer times you may feel you have to invoke authority from the management to force something.The importance of feedbackScrum and Agile methodology rely very heavily on fast and transparent feedback. As a Scrum Master, you have an initial feedback system laid out from you in the form of the Scrum ceremonies. These are just the beginning though. You and the team should continuously look to tune and improve your feedback systems so that the team can continually find better ways of delivering better business outcomes.Part of the Scrum Master’s role might be to look at the feedback system, to help the team assess whether they are the right ones and to find better ones.  Sometimes, a Scrum Master finds new ideas about feedback that a team might miss. The team members are all heads down building products and solutions and often prioritize ‘the work’ over ‘the system’.But a Scrum Master can bring an outsider’s perspective, or might be more able to observe the wider system the team operates in. Don’t be afraid of expressing your observations and ideas to the team where you have an insight that they don’t have. That perspective can be very valuable.  You will often be the first to see when a change needs to be made and can let the team know it’s time to start thinking differently.Getting feedback on your own performanceHave a plan for how you are going to grow and become great at the role.  Pursue continuous incremental improvement by setting up regular short cycle feedback systems on yourself.  Pause and reflect on how you are going and what you should do to improve. Do it regularly, and no less frequently than the sprint cycle.  Keep checking with the team whether they need help and what they would like you to help them with, and when you are done, check what they thought of your efforts.Get experience, get training, get a coach or mentor and find a community of practitioners that you can connect with and learn from. Leverage the experience from others, as the people who do this work love to help others and make themselves generously available.Traps in transitioning from Project Manager to a Scrum MasterHere are some of the traps in transition that can be avoided by a Project Manager who has recently assumed the role of a Scrum Master.Responsibility to organize meetingsAgile Manifesto principles believe in building projects collaboratively. Scrum Master arranges meetings for the teams whenever necessary. This is unlike a traditional Project Manager who used to be an administrative assistant to schedule meetings for everyone. Scrum and Agile give an importance to the individuals and interactions over processes and tools.Mistaking the ‘Daily Scrum’ as a ‘Status Update’ taskScrum Master arranges the ‘Stand-ups’ to communicate with the team members. The traditional Project Manager keeps track of everyone’s work to update the project plans and finding out the finishing dates. In Scrum, teams act as self-directing and accountable. So, after their transition to the Scrum Master’s role, the earlier Project Managers should be mindful about their perception of “daily scrum”. The point should be sledgehammered to the minds of these new Scrum Masters that daily scrum is only for the purpose of discussion and is not a status update task.Being a ‘Scrum Master’ is the only jobScrum Master’s role should be multifaceted as an SM has to play the ideal servant-leader role. Also, his role keeps changing in some Agile teams. If any task is incomplete and the Scrum Master is capable of doing it, they should pick up and implement the task. Scrum guide states that “helping the development team to create high-value products”, is one of the services of the Scrum Master. Therefore while transitioning from Project Manager to the Scrum Master, it is important to keep in mind that Scrum Master is not a unidimensional role. It entails multiple aspects.Improper Stakeholder Communication ManagementIn Scrum, the progress is measured as a ‘working software per Agile Manifesto’. The issues are raised, analysed and solved by the team with an external help if necessary. The Scrum Master may not be able to manage the objective the team uses to collaborate. The required deliverables may be set already if there is a governing body such as a portfolio management group or a project management office. In such cases, Scrum Masters should spot the reality that issues are flexible and alter depending on the work committed by the team. Detailing out risks can be ignored, as they will be outdated within a few days or even minutes.ConclusionTransitioning from Project Manager to Scrum Master can be a challenging yet fun. You just need to be very careful. It is important to help with reflection and coaching so that the new Scrum Masters leave some habits behind. When it comes to transitioning to the Scrum Master role, you definitely cannot achieve everything overnight. The first vital step is to get laser-focused. Certifications, as we discussed earlier can be the best if not the only way to do it. All the best for your transition.
Rated 4.5/5 based on 9 customer reviews
1255
How to Transition From Project Manager to a Scrum ...

Scrum Masters and Project Managers are not the sam... Read More

Useful links