Sai Shekar Peddi

OBP is an "Outcome Based Plan" to do Agile Transformation. The link to register is mentioned below. https://lnkd.in/gZv3ncYC Above one is the direct link to register. #agile #webinar #agiletransformation #outcomebased #outcomesmatter

8

✨ 𝐄𝐗𝐏𝐄𝐑𝐈𝐄𝐍𝐂𝐄 𝐏𝐈 𝐏𝐋𝐀𝐍𝐍𝐈𝐍𝐆: 𝐀 𝐆𝐔𝐈𝐃𝐄 𝐅𝐎𝐑 𝐒𝐂𝐑𝐔𝐌 𝐌𝐀𝐒𝐓𝐄𝐑𝐒 by Raja Abhishek Jain✨ 👉 𝐑𝐞𝐠𝐢𝐬𝐭𝐫𝐚𝐭𝐢𝐨𝐧 𝐋𝐢𝐧𝐤: https://lnkd.in/gpp_QU9Z Only 100 spots are available – sign up now! 𝐀𝐠𝐞𝐧𝐝𝐚: 🔸Essential Role of Scrum Masters: Understand the critical responsibilities of Scrum Masters before, during, and after the PI Planning event. 🔸Tool Demonstration: Gain experience with a leading PI Planning tool and see how it can streamline the planning process. 🔸Best Practices and Tips: Discover proven strategies and best practices to ensure smooth and effective PI Planning sessions. 🔸Interactive Learning: Engage in a live demonstration and Q&A session to address your specific questions and challenges. Target Agility - Where Scrum Mastery Unfolds! #ScrumMastersUnite #AgileLearning #ScrumMaster #InterviewPrep #Community #scrum #scrummaster #scrummasterjobs #scrummastertraining #scrummastercertification

45

Artifacts for Transparency   In Scrum, there are several artifacts that can be utilized to maximize a high level of transparency around work and processes.   The domain of the Product Owner (P.O.), the Product Backlog, should be a list of requirements that are ordered based on their significance to the P.O. The transparency is that anyone who looks at this list, can see what the top priority for scheduling is. Note: This is not unlike the long list of to-dos you may have pinned on your refrigerator. 😋   There is also the Sprint Backlog. Think of it as you moving a few of the to-dos off of your long list, and now you have them in a short list that is committed for completion within a set timeframe called a Sprint. Anyone who is wondering what you, or your team is working on, can visit this list and clearly see what's moving. If something isn't showing on the list, that means it isn't being addressed which will then promote conversations around where the missing work is. Boom, transparency. ⚡   Definitions of Ready (DoR) and Definition of Done (DoD) are just what they sound like. Clear points that need to be met before a piece of work is Ready to be pulled into a sprint and when a piece of work is Done from the sprint. A DoR point might be, "The User Story has to be estimated." or "There must be measurable Acceptance Criteria listed." In everyday function, if your life revolves around putting together furniture deliveries, a DoR point might be, "Before piecing together a delivery, ensure all the pieces were received." This will ensure you are not on step 1,000 and the last piece you need is missing. 😡 Had there been a DoR to follow, it would have been transparent the project was not Ready to be started. 🛑   Having recorded artifacts helps keep everyone on the same page and promotes high levels of transparency that in turn produce efficiencies and eliminates waste. As Scrum Masters, our tenant is to encourage our teams to consistently lean into and periodically revisit these artifacts in the pursuit of becoming a high performing team.   #scrum #agile #transparency #scrumartifacts #growthmindset #servantleader #scrummaster #evolve  

11

17 Comments

7 Common Scrum Anti-Patterns From Anti-Patterns to Best Practices: Transform Your Scrum Journey Scrum is a powerful framework that helps teams deliver value consistently, but it’s easy to fall into anti-patterns—habits or practices that may seem productive but harm the team’s effectiveness over time. Here are some common Scrum anti-patterns and how to deal with them: 1) 𝐒𝐜𝐫𝐮𝐦𝐟𝐚𝐥𝐥 (𝐖𝐚𝐭𝐞𝐫𝐟𝐚𝐥𝐥 𝐢𝐧 𝐒𝐜𝐫𝐮𝐦 𝐂𝐥𝐨𝐭𝐡𝐢𝐧𝐠) Teams try to squeeze traditional waterfall processes into Scrum sprints, with all the design happening upfront and testing at the end. To avoid this, encourage incremental development where design, coding, and testing occur continuously throughout the sprint. 2) 𝐎𝐯𝐞𝐫𝐜𝐨𝐦𝐦𝐢𝐭𝐭𝐢𝐧𝐠 𝐭𝐨 𝐭𝐡𝐞 𝐒𝐩𝐫𝐢𝐧𝐭 𝐁𝐚𝐜𝐤𝐥𝐨𝐠 Teams bite off more than they can chew, often due to external pressure. To fix this, focus on realistic sprint planning. Leverage past velocity data and ensure the team owns its commitments without feeling pressured to overdeliver. 3) 𝐓𝐡𝐞 𝐃𝐚𝐢𝐥𝐲 𝐒𝐭𝐚𝐧𝐝-𝐮𝐩 𝐚𝐬 𝐚 𝐒𝐭𝐚𝐭𝐮𝐬 𝐔𝐩𝐝𝐚𝐭𝐞 When team members treat the daily stand-up as a report to the Scrum Master rather than a collaborative problem-solving session, it loses value. Instead, encourage open discussions where team members talk to each other about progress, challenges, and next steps. 4) 𝐈𝐠𝐧𝐨𝐫𝐢𝐧𝐠 𝐓𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐃𝐞𝐛𝐭 Pushing through features without addressing technical debt can lead to long-term productivity issues. Ensure that time is set aside in the sprint to tackle technical debt, either through dedicated backlog items or by embedding debt-reduction tasks into feature work. 5) 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 𝐎𝐰𝐧𝐞𝐫 𝐚𝐬 𝐚 𝐓𝐚𝐬𝐤𝐦𝐚𝐬𝐭𝐞𝐫 When the Product Owner assigns tasks instead of setting goals, it disempowers the team. The Product Owner should focus on prioritizing the backlog while allowing the team to self-organize around how to achieve sprint goals. 6) 𝐒𝐤𝐢𝐩𝐩𝐢𝐧𝐠 𝐑𝐞𝐭𝐫𝐨𝐬𝐩𝐞𝐜𝐭𝐢𝐯𝐞𝐬 𝐨𝐫 𝐌𝐚𝐤𝐢𝐧𝐠 𝐓𝐡𝐞𝐦 𝐒𝐡𝐚𝐥𝐥𝐨𝐰 Some teams either skip retrospectives or treat them as a formality. Retrospectives are essential for continuous improvement. Ensure they’re meaningful by focusing on actionable insights and fostering a safe environment where the team can discuss what’s working and what’s not. 7) 𝐒𝐩𝐫𝐢𝐧𝐭 𝐑𝐞𝐯𝐢𝐞𝐰𝐬 𝐚𝐬 𝐚 𝐅𝐨𝐫𝐦𝐚𝐥 𝐏𝐫𝐞𝐬𝐞𝐧𝐭𝐚𝐭𝐢𝐨𝐧 Sprint reviews should be a collaborative demo with stakeholders, not a PowerPoint presentation. Encourage live demonstrations of working software and open discussions on feedback and potential changes. Dealing with these anti-patterns proactively can help Scrum teams stay on track, improve collaboration, and consistently deliver value. Keep an eye out for them and course-correct when necessary! Want to get more valuable content follow Jitendra Kumar, SPC, SAFe #ScrumMaster #AgileTransformation #scrum #Agile

191

72 Comments

7 𝐒𝐩𝐫𝐢𝐧𝐭 𝐑𝐞𝐭𝐫𝐨𝐬𝐩𝐞𝐜𝐭𝐢𝐯𝐞 𝐌𝐞𝐞𝐭𝐢𝐧𝐠 𝐀𝐧𝐭𝐢-𝐩𝐚𝐭𝐭𝐞𝐫𝐧𝐬 A Sprint Retrospective is a crucial Scrum event for reflecting on the past sprint and identifying improvements. It promotes continuous growth, collaboration, and trust within the team. However, retrospectives can often become repetitive and lose effectiveness. Let us understand the antipattern and solution. 7 Anti-patterns of Sprint Retrospective and Their Solutions 1️⃣ 𝐁𝐥𝐚𝐦𝐞 𝐆𝐚𝐦𝐞 👉𝐀𝐧𝐭𝐢-𝐩𝐚𝐭𝐭𝐞𝐫𝐧: Team members use the retrospective to point fingers, leading to defensiveness and damaging trust. 👉𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Focus on collective responsibility by framing discussions around the question, "What could we, as a team, do better?" Encourage a blameless culture. 2️⃣ 𝐋𝐚𝐜𝐤 𝐨𝐟 𝐏𝐫𝐞𝐩𝐚𝐫𝐚𝐭𝐢𝐨𝐧 👉 𝐀𝐧𝐭𝐢-𝐩𝐚𝐭𝐭𝐞𝐫𝐧: Retrospectives are rushed, with little thought given to the issues at hand. 👉𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Encourage team members to prepare ahead of time by collecting feedback throughout the sprint. The Scrum Master can use tools like surveys to gather insights in advance. 3️⃣ 𝐒𝐚𝐦𝐞 𝐅𝐨𝐫𝐦𝐚𝐭 𝐄𝐯𝐞𝐫𝐲 𝐓𝐢𝐦𝐞 👉𝐀𝐧𝐭𝐢-𝐩𝐚𝐭𝐭𝐞𝐫𝐧: Repeating the same retrospective format every sprint can lead to disengagement and routine behavior. 👉𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Vary the format using different activities (e.g., "Start, Stop, Continue" or "4Ls: Liked, Learned, Lacked, Longed for") to keep engagement high and discussions fresh. 4️⃣ 𝐅𝐨𝐜𝐮𝐬𝐢𝐧𝐠 𝐎𝐧𝐥𝐲 𝐨𝐧 𝐍𝐞𝐠𝐚𝐭𝐢𝐯𝐞𝐬 👉𝐀𝐧𝐭𝐢-𝐩𝐚𝐭𝐭𝐞𝐫𝐧: The team focuses only on what went wrong, ignoring positive outcomes. 👉𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Include a celebration of successes to acknowledge what went well, thus creating a balanced discussion that motivates the team. 5️⃣ 𝐔𝐧𝐜𝐥𝐞𝐚𝐫 𝐀𝐜𝐭𝐢𝐨𝐧 𝐈𝐭𝐞𝐦𝐬 👉𝐀𝐧𝐭𝐢-𝐩𝐚𝐭𝐭𝐞𝐫𝐧: Teams leave the retrospective with vague or no actionable items, leading to no real improvements. 👉𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Ensure that the retrospective ends with specific, measurable, and actionable items. Assign owners and set deadlines to ensure accountability. 6️⃣ 𝐎𝐯𝐞𝐫𝐥𝐨𝐚𝐝𝐢𝐧𝐠 𝐭𝐡𝐞 𝐃𝐢𝐬𝐜𝐮𝐬𝐬𝐢𝐨𝐧 👉𝐀𝐧𝐭𝐢-𝐩𝐚𝐭𝐭𝐞𝐫𝐧: Trying to solve too many problems at once dilutes focus and leads to a lack of real progress. 👉𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Prioritize the most critical issues to address and focus on one or two major improvements per sprint. 7️⃣ 𝐒𝐤𝐢𝐩𝐩𝐢𝐧𝐠 𝐭𝐡𝐞 𝐑𝐞𝐭𝐫𝐨𝐬𝐩𝐞𝐜𝐭𝐢𝐯𝐞 👉𝐀𝐧𝐭𝐢-𝐩𝐚𝐭𝐭𝐞𝐫𝐧: The team may skip retrospectives due to time constraints or because they feel no value is being gained. 👉𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧: Emphasize the importance of continuous improvement and make retrospectives a non-negotiable, protected event. Adjust the length if necessary but never skip it. Addressing these anti-patterns helps teams maximize retrospectives, driving continuous improvement and enhanced performance. Want to get more valuable content follow Jitendra Kumar #Scrum #Agile #SprintRetrospective 

153

43 Comments

11 Scrum Artifacts: A Beginner's Guide [2024] - Simplilearn 11 Scrum Artifacts: A Beginner's Guide [2024]  Simplilearn

6

Course Details Certified Scrum Product Owner (CSPO) helps you equip yourself with all the required knowledge to deliver your Products iteratively and incrementally. It also enables you to understand how to prioritise the Product Backlog to deliver outcomes instead of output. This course helps you understand how a “Discovery” to “Delivery” flow happens and the role of a Product Owner in each step involved in Product Development and Product Management. Who is a Product Owner? A product owner is a value maximizer accountable for maximising the product’s value resulting from the scrum team’s work. Product Owners have a unique and crucial role in helping the team focus on the most valuable item for a customer. Product owners often focus on products and the product’s value in the marketplace while collaborating with the scrum team. What is the Certified Scrum Product Owner course? If you’re ready to grow as a Product Owner, our Certified Scrum Product Owner (CSPO®) course is designed for you. You’ll learn the skills and traits required to grow as a product owner and gain an understanding of the necessary competencies to succeed in your role. Considered the gold certification standard, the CSPO course is an intense and immersive experience. Taught by the award-winning, experienced Scrum trainer at tryScrum, each CSPO class is intense and integrates the real-world challenges of a Product Owner in a complex environment. Our training program gives you hands-on skills to immediately apply in the real world and expand your career opportunities. Once you complete the course, you will be invited to join the product owner community by accepting the Scrum Alliance licensing agreement. Who is This Course for PRODUCT OWNERS | BUSINESS ANALYSTS | PROJECT MANAGERS | PRODUCT MANAGERS | TEAM MEMBERS | DATA ANALYSTS Anyone new to agile will find the CSPO course valuable. Scrum Product Ownership is an emerging and promising career in most industries today. Product owner jobs—and the irreplaceable people skills these roles require—are on the rise. In 2020, LinkedIn named it the #15 emerging jobs, with a 24% annual growth. The World Economic Forum went even further, calling it the #1 job needed for the emerging global workforce. Trainer: Venkatesh Rajamani #cspo #productowner

5

1 Comment

🗓️ 𝗗𝗮𝘆 𝟏𝟎/𝟵𝟬 | 𝐁𝐚𝐜𝐤𝐥𝐨𝐠 𝐆𝐫𝐨𝐨𝐦𝐢𝐧𝐠: 𝐓𝐡𝐞 𝐊𝐞𝐲𝐬𝐭𝐨𝐧𝐞 𝐨𝐟 𝐀𝐠𝐢𝐥𝐞 𝐏𝐥𝐚𝐧𝐧𝐢𝐧𝐠 + The importance of Backlog Grooming in the Scrum process + Objectives and benefits of regular Backlog Grooming sessions + Step-by-step guide to effective Backlog Grooming + Best practices for keeping the Product Backlog clean and prioritized (full info available on the newsletter) 𝐒𝐮𝐛𝐬𝐜𝐫𝐢𝐛𝐞 𝐨𝐧 𝐋𝐢𝐧𝐤𝐞𝐝𝐈𝐧 𝐍𝐞𝐰𝐬𝐥𝐞𝐭𝐭𝐞𝐫: https://lnkd.in/gwaR9Si3 Are you ready to create User Stories that ensure your product hits the mark with your users? Join our targeted LinkedIn Newsletter 𝐀𝐠𝐢𝐥𝐞 𝐆𝐮𝐢𝐝𝐞: 𝐃𝐚𝐢𝐥𝐲 𝐓𝐢𝐩𝐬, where we delve into the nuances of crafting User Stories that drive clarity, collaboration, and user satisfaction. 𝐊𝐞𝐲𝐰𝐨𝐫𝐝𝐬: Backlog Grooming, Scrum, Agile, Sprint Planning, User Stories, Prioritization ___________________ 𝐏𝐫𝐞𝐯𝐢𝐨𝐮𝐬 𝐀𝐫𝐭𝐢𝐜𝐥𝐞: https://lnkd.in/gz7UxCe5? #BacklogGrooming #AgileScrum #Scrum #Agile #ScrumVoice #AgileVoice #ScrumArticle #AgileArticle #ScrumNewsletter #AgileNewsletter #LinkedInTopVoice

4

3 Comments

Arpit Shah’s post reminds me of an earlier discussion on Scrum and Agile practices. Sharing both for a broader perspective! In my earlier post, I highlighted how adopting Scrum without a solid foundation can lead teams into the build trap—focusing more on delivering features than achieving business outcomes. Remember, Scrum isn’t a project management method but an Agile framework. Link: https://lnkd.in/gFf2W2Tx Arpit’s great article simplifies the roles of Scrum Master vs. Technical Program Manager, breaking down key differences in scope, role definition, and focus areas. Definitely worth checking out! #Scrum #Agile #Leadership #ProjectManagement #Teamwork

7

2 Comments

🌟 BA Tip of the Week – Business Analysis Techniques – Glossary🌟 🎯Purpose: Key terms related to a business domain are defined in a glossary. 📚According to BABOK V3: Glossaries are used to provide a common understanding of terms that are used by stakeholders. A term may have different meanings for any two people. A list of terms and established definitions provides a common language that can be used to communicate and exchange ideas. A glossary is organized and continuously accessible to all stakeholders. 📍A term is included in the glossary when: ⏩The term is unique to a domain ⏩There are multiple definitions for the term ⏩The definition implied is outside of the term's common use ⏩There is a reasonable chance of misunderstanding ⁉️Importance of Glossary Creation in Projects 1️⃣Early-Stage Glossary Creation : A glossary should be created at the beginning of a project. It facilitates knowledge transfer and ensures a common understanding among stakeholders 2️⃣Designate a Point of Contact: Identify a responsible person for maintaining and distributing the glossary. This ensures the glossary stays up-to-date and accessible throughout the initiative 3️⃣ Long-Term Benefits: Organizations can leverage the glossary for future initiatives. Glossaries often find additional uses beyond their original purpose, helping streamline future projects. 💡Consideration when creating a glossary: ⏩ Definitions should be clear, concise, and brief ⏩ Acronyms should be spelled out if used in a definition ⏩ Stakeholders should have easy and reliable access to glossaries ⏩ The editing of a glossary should be limited to specific stakeholders. #iiba #IIBAColombo #IIBASriLanka #businessanalysis #srilanka #babok

15

Scrum Cheat Sheet - That summarizes the essentials of Scrum Are you using Scrum in your organization? How has it helped you? Be A Certified Agile Leader with SAFe® 6.0 Certification.🎓 Learn from experts at AgilityPAD who will guide you across your agile career. For any queries & bulk discounts write to us at 📧 [email protected] ☎️ +44 7887 378121 ww.agilitypad.com Image credit to rightful owner #scrum #scrummaster #scaledagile #kanban #scrumban #safeagilist #Safe6 #scaledagileframework #designthinking #scaledagile #agilecoach #agiletransformation #agile #projectmanager #businessagility #ScaledAgile #agilitypad #agilemindset #agiletransformation #scrumtraining #scrumstudy #scrumproductowner #softwaredevelopment #projectmanagement #ProjectManager #Productowner #leadership #leaders

2

Free Scaled Scrum (SPS) Practice Assessment  Prepare and practice for the Scrum.org Scaled Professional Scrum (SPS I) Assessment. https://lnkd.in/d3Zi36VG #scrum #agile #scrummaster #productowner #training #kanban @Scrumdotorg

2

Dear Scrum Master, Thank you for joining the Scrum Metrics webinar and found it helpful. Those who has missed the webinar can opt the recording from below link. Note - You can also opt for the below toolkit which consist 46+ topics Scrum Master needs to know ( Digital recording + Study Material + Templates) . https://lnkd.in/gpS_qQ8r

26

People frequently inquire about choosing between a career as a Scrum Master or a Product Owner. Here's what guided my decision. I hope it proves helpful to you! If you found this useful, follow Anand Pandey for more!

240

11 Comments

🌟𝐌𝐀𝐒𝐓𝐄𝐑𝐈𝐍𝐆 𝐉𝐈𝐑𝐀 𝐀𝐃𝐕𝐀𝐍𝐂𝐄𝐃 𝐑𝐎𝐀𝐃𝐌𝐀𝐏𝐏𝐈𝐍𝐆 𝐅𝐎𝐑 𝐒𝐂𝐑𝐔𝐌 𝐌𝐀𝐒𝐓𝐄𝐑𝐒!🌟by Avishek Patra Starting in another 2 hours! 🗓 11 JUL 🕧 07:00 - 08:30 PM IST 👉 𝐑𝐞𝐠𝐢𝐬𝐭𝐫𝐚𝐭𝐢𝐨𝐧 𝐋𝐢𝐧𝐤: https://lnkd.in/gYwbSfhY 𝐀𝐠𝐞𝐧𝐝𝐚: 📌Effective Timeline Representation: Understand how to use Jira to create clear timelines for software delivery. 📌Visual Project Scheduling: Learn how to visually represent and manage your project schedules using Jira’s advanced roadmapping features. 📌Optimization Techniques: Discover smart strategies to optimize your planning and streamline project management. 📌Practical Demonstrations: See live demonstrations of Jira features in action, showcasing their practical application for Scrum Masters. 📌Interactive Q&A: Engage with the presenter to ask questions, share experiences, and gain insights from real-life use cases. Target Agility - Where Scrum Mastery Unfolds! #ScrumMastersUnite #AgileLearning #ScrumMaster #InterviewPrep #Community #scrum #scrummaster #scrummasterjobs

16

1 Comment

Ultimate Scaled Scrum (SPS) Practice Assessment. Prepare and practice for the Scrum.org Scaled Professional Scrum (SPS) Assessment. https://lnkd.in/dYiQGFQG #scrum #agile #scrummaster #productowner #training #kanban @Scrumdotorg

3