Srividya Soma

# some good starting points for a Scrum master to check when you join a new team#: 1.  Which boards the team uses? 2.  What iteration are you in now? 3.  How long is the iteration? 4.  What are the team velocity and capacity? 5.  What are the epics of the product? 6.  Is there a backlog? 7.  Are there stories rollover? 8.  Do Iterations have a goal? 9.  Is the story descripted from the user perspective? 10. Is the story description understandable? 11. Is there an acceptance criteria? 12. What issue type are used in Jira? 13. What is the Workflow? 14. What Is the release schedule? 15. Is there DoD? 16. Are there any Scrum meetings that already scheduled? 17. What are the problems that the team members are facing in the day to day? 18. What works for your team and why?

64

9 Comments

See the Bigger Picture: Value of System Demos in Scaled Agile Scaled Agile Framework (SAFe) relies on System Demos, typically occurring once every 2-4 weeks, to showcase the integrated work of ART (Team of Agile teams). These demos offer a crucial advantage over individual team presentations. Stakeholders gain a holistic view of progress, seeing how features from various teams come together. This fosters early feedback, allowing course correction and ensuring the final product aligns with expectations. System Demos are a key tool for building trust, transparency, and delivering the right solution in a fast-paced environment. #LearningByte #SystemDemos #ScaledAgile #ART #AgileReleaseTrain

6

Uncover the rhythm of your Scrum team. Master the art of velocity - the heartbeat powering your project's progress. Unlock the keys to accelerating value delivery and driving your initiatives forward with unstoppable momentum. https://ow.ly/K8cy50RiXi6 #AgileMethodology #ScrumFramework #TeamProductivity #VelocityMetrics #ProjectDelivery #AgileBestPractices #OperationalEfficiency

3

The values of Scrum Focus starts with “elimination.” Courage starts with “psychological safety.” Openness starts with “vulnerability.” Respect starts with “empathy.” Commitment starts with “Trust.” If these ingredients fall well, an Organization will build a workplace that creates value frequently!! tryScrum

32

3 Comments

Looking to learn how to manage software risk across your enterprise level organization? Download this new white paper from Dark Reading and discover solutions to help you scale your application security program!

1

It was an honor to meet the author of “Comic Agile”tonight who brilliantly summarized the reality when agile is introduced through humor (and tears…) His keynote today was a reminder that agile transformation takes time, each role faces unique challenges and opportunities, impediments are the way, the sooner we can remove impediments the faster we become. And yes, we both agreed that any agile frameworks are tools, that must be customized to organizational context and not blindly followed, fit for purpose. For example, Principle 1 of SAFe: take an economic view (don’t scale unless you have to). Practice is the only test of truth. Stay tuned for my summary soon. https://www.comicagile.net #comicagile Luxshan Ratnaravi

49

2 Comments

Championing Agile Transformation! Transforming organizations one sprint at a time! 🔄 As a Scrum Master, guiding teams through the intricacies of #AgileTransformation is both challenging and exhilarating. Recently, we completed an enterprise-wide adoption that significantly boosted productivity and team morale. 📈 ✨ Highlights: - Consistent Training: Regularly upskilling both seasoned and new team members. - Cultural Shift: Fostering an environment of continuous improvement and open communication. - ROI: Witnessing tangible business value and stakeholder satisfaction. Let's connect and share experiences on driving successful agile transformations! What has been your most challenging yet rewarding transformation story? #Scrum #AgileLeadership #TransformationTuesday #ContinuousImprovement

1

I am excited to share that I have successfully passed the Professional Scrum Product Owner I (PSPO I) certification from Scrum.org. This certification validates my knowledge of the Scrum framework and my ability to support and enable value creation and delivery. Earning PSPO I shows my understanding of how to bridge the gap between strategy and agile product management in order to create valuable products using Scrum.

26

8 Comments

Podcast Topic: Estimation - Development Vs Testing. Do we need to estimate separately for Development and Testing? #learnagilebySelvi #agile #knowledgesharing #podcast https://lnkd.in/gXvPzRFZ

6

Experiment: Observe What is Happening 🔎 Inexperienced Scrum Masters often rush to solve problems, offer suggestions, and show the path forward. While this can be helpful, it can also impede ❌ a team’s ability to learn and grow and undermine their ability to self-organize. This experiment is designed for Scrum Masters to find a better balance between solving problems and enabling growth and autonomy. To try this experiment, do the following: 1️⃣ At the start of a Sprint, ask for permission from the team to step back 🚶‍♂️this Sprint. This is a good moment to talk about self-organization and how you can get in the way of that. As a Scrum Master, you still participate in various events, but not actively. So no facilitation, no suggestions, or taking the lead. You remain available to answer questions or help when the team is stuck. 2️⃣ During the Sprint, observe what is happening as the team does its work. Use the list as described in the next section as inspiration. Whenever you observe something 🧐, don’t jump to conclusions or interpretations. Instead, ask yourself what you are specifically seeing or hearing. 3️⃣ In the Sprint Retrospective, explore what it was like for your team to have you in a passive role. What became possible because of it? Where did they notice self-organization? 4️⃣ If the team is up for this, you can share your factual observations during the Sprint Retrospective. For example, say “I see that 7 out of 10 items are ‘In Progress’ on the first day of the Sprint” or “I noticed that the Daily Scrum usually starts 5 to 8 minutes later as people have to wait for others to join”. Give your team the first opportunity to recognize and make sense of the observations, then share your own in a constructive way. What has the team learned about their work together? Which impediments have you noticed? 🤔 5️⃣ Use your observations to drive the open questions you ask during the Sprint. A well-timed powerful question, built on observations, can create huge insights that would otherwise take months to discover. For example: “This Sprint, we never interacted with our stakeholders. How does this align with our goal to build a valuable product 💰 for them?” Some findings: 👉 The skill to observe what is happening is also one for the Scrum team to learn. You can experiment with rotating the role. The “observer” still does his or her work but takes a passive role during gatherings. 👉 It can be hard to sit on your hands when you’re used to taking the lead. Especially when you notice that the team is struggling. Trust in their ability to figure it out. The flip side is also true; don’t sit on your hands all the time. Scrum Masters have a lot of work to do when they want to help entire organizations work empirically. Consider this experiment as taking a breather and using that time to inform your next steps. Interested in learning more? Check: https://bit.ly/3JFzAQQ

18

Building trust is the first crucial step every Scrum Master should take to foster an open environment. By creating a space where everyone feels comfortable to speak, collaboration and communication are enhanced, ultimately leading to effective delivery of business value. #agilemindset# #scrumteamsuccess# #trustbuilding# #communicationcollaboration# #businessvaluedelivery#

4

1 Comment

I am excited to share that I have successfully passed the Professional Scrum Product Owner I (PSPO I) certification from Scrum.org. This certification validates my knowledge of the Scrum framework and my ability to support and enable value creation and delivery. Earning PSPO I shows my understanding of how to bridge the gap between strategy and agile product management in order to create valuable products using Scrum.

9

#Agile #Scrum #Increment #Userstory Definition of Done- It defines the quality of the increment done in a sprint. So its a set of items or a checklist which a user story has to fulfill to consider it as completed or done. For eg- For a new development DOD can have following points to be considered for all user stories to be treated as Done- 1. Unit testing is done 2. Code review is done 3. All tests are passed, and no major defects are open. 4. Acceptance criteria is met. 5. Test review is done by PO and approved. 6. Increment is of high quality and value and potentially shippable. #AgileMethodology

4

Testing and reviewing new code is critical in pre-production to avoid major errors and service disruptions. Splunk Observability Cloud makes this process easy for engineering teams. Read on to learn how.

10

Testing and reviewing new code is critical in pre-production to avoid major errors and service disruptions. Splunk Observability Cloud makes this process easy for engineering teams. Read on to learn how.

1