Gez Smith的动态

Diving back into one of my favorite reads this year! This book by Jeff Sutherland has been an eye-opener once again. This time around, I've stumbled upon three key takeaways that I just had to share: 1?? Collaboration is key.?It's all about leveraging the collective intelligence and skills of the team to achieve success. 2?? Streamline for success. By identifying and eliminating non-essential tasks, teams can focus their energy on activities that truly drive results. 3?? Always improve. Whether it's through sprint retrospectives or ongoing feedback loops, the focus is on learning from experiences and refining processes to deliver even better outcomes. Have you had the chance to explore this gem yet? ?? If not, I highly recommend adding it to your reading list! If you've got any other book suggestions that have sparked your interest lately, drop them in the comments below! #scrum #productivity #bookrecommendations

?? Boost Team Performance with the "Start, Stop, Continue" Retrospective ?? Simple frameworks often deliver the most impact when it comes to continuous improvement. One of my favorite retrospective techniques is Start, Stop, Continue. It’s quick, straightforward, and focuses on actionable feedback! Here’s how it works: ? Start – What should the team start doing to improve productivity and collaboration? Example: “Let’s start engaging the Product Owner earlier to clarify user stories.” ? Stop – What is holding the team back that should stop? Example: “We should stop overcommitting to stories we can’t complete in a sprint.” ?? Continue – What’s working well that the team should keep doing? Example: “Let’s continue our regular knowledge-sharing sessions—they’ve been super valuable!” This technique encourages reflection and makes it easy to spot patterns, helping teams identify both blockers and strengths. Plus, it’s a great way to reinforce positive habits! Why I love it: 1.It's actionable. 2.Keeps the conversation constructive. 3.Simple, yet effective. Do you use Start, Stop, Continue in your retrospectives? How has it worked for you? #Agile #Scrum #Retrospective #ContinuousImprovement #TeamCollaboration #StartStopContinue

Sprint Retrospective: The Engine of Continuous Improvement ?? How does your team keep improving sprint after sprint? It’s all about the Sprint Retrospective! ?? Purpose: This ceremony is your team’s opportunity to reflect on what worked, what didn’t, and how to improve for the future. It’s where growth happens! How Retrospectives align with Agile principles: ?? Principle 12: "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." This is the heart of the retrospective—continuous improvement! ?? ?? Principle 11: "The best architectures, requirements, and designs emerge from self-organizing teams." Retrospectives empower teams to take ownership of their processes and drive change. ??? ?? Principle 5: "Build projects around motivated individuals." When team members feel heard and see their feedback implemented, motivation soars. ?? ?? Pro Tip: Use tools like Start-Stop-Continue or a simple 3-column board to keep your retrospectives structured and actionable. What’s one improvement your team has made after a retrospective that made a huge difference? Share your story below! ?? #SprintRetrospective #AgileCeremonies #Scrum #ContinuousImprovement #TeamWork #AgileLeadership

Retrospectives can sometimes be challenging, this is our template to make them more fun and engaging: https://lnkd.in/gKbDxdT2

When sprint events become a reason to hold information back until a fixed meeting, you have let your Scrum become an anti-pattern. Don’t wait for the Daily. Don’t wait for the Review. Don’t wait for the Retro. Inspect early. Adapt often.

Last Thursday, we held our latest retrospective. Let's be honest: the same old boring questions every sprint can lead to the same old boring conversations. Been there, done that, bought the t-shirt! To counter this, I started utilizing various creative and engaging techniques to keep these sessions lively yet productive. This time I used *The Weather Report* ! In this technique we used weather metaphors to describe our sprint experience. Each team member shared their personal "weather report" to reflect their feelings and observations about the sprint. Here’s how it works: *Sunny*??: Everything went smoothly, and the team felt positive and productive. *Partly Cloudy* ??: There were some minor issues, but overall, it was a good sprint. *Cloudy* ??: Several challenges and obstacles were encountered, impacting productivity. *Stormy* ???: Significant problems and blockers affected the team's progress. *Tornado*??? : Major disruptions or crises occurred, creating a highly stressful environment. *Rainbow* ?? : Despite challenges, the team found a positive outcome or learned valuable lessons. This structured approach turned our retrospective into a fun and constructive dialogue. The team left with clear insights and actionable steps, ready to make our next sprint the best one yet How do you keep your retrospectives from feeling like a repeat episode? let’s swap some tips and tricks! #Agile #Scrum #Retrospective #ContinuousImprovement #TeamBuilding #ScrumMaster

?? Use the High Port to Detach in Retrospectives ?? In Extreme Ownership, Jocko Willink and Leif Babin talk about the power of detachment in critical situations. One key tactic he describes is moving from looking down the sights of your weapon—where you’re hyper-focused on one target—to holding the weapon at "high port." This move allows you to lift your head, detach, and take in the broader surroundings. ?? This concept applies directly to our teams during a sprint. We’re heads down, focused on completing tasks, just like aiming down the sights. But when the sprint ends, it’s time to go to "high port." The retrospective is that moment where we raise our heads, detach from the specific tasks, and focus on the bigger picture: ?? How are we working as a team? ?? What improvements can we make to our process? ?? What did we miss while we were so focused on the sprint goals? By using the "high port" and detaching during retrospectives, we can gain critical insights that aren’t visible when we’re in the heat of the sprint. This step back is essential for continuous improvement and team growth. Raise your head. Detach. Improve. #Agile #Scrum #Retrospectives #ContinuousImprovement #ExtremeOwnership #Detach

The goal with Agile is to deliver early and often. Only delivering and planning on set cadences is an anti-pattern.

?? For our final Tip #8 on Agile in L&D: Conducting Post-Learning Retrospectives. How do you facilitate post-training discussions? For deeper insights, read the blog in the comments below. #LearningApplication #ContinuousImprovement #AgileHR

?? Agile Tip #18: Show Progress ?? Use tools like burn-down charts or Kanban boards to make progress visible. It’s an easy way to spot potential blockers and keep the team on track. What’s your favorite way to visualize progress? ?? #VisualManagement #ProgressTracking #Agility