Caleb A. Smith

A lot of product work fails to land, not because it’s wrong, but because it’s framed the wrong way. Let's break down how shifting from features to business outcomes changes your influence, focus, and credibility as a PM. Listen to the full episode with David Nash on The Product Porch Podcast

7

How a 9th Grader Used Scrum to Conquer an English Project—Twice as Fast What if your teen could cut their project time in half—and actually enjoy the process? That’s exactly what Noah did using a simple Scrum board. For a major 9th-grade English assignment, he kicked off Day 1 by breaking down the entire project into clear, visual tasks. From article writing to comprehension slides, everything had its own sticky note and column. Instead of feeling overwhelmed, he had one clear goal: “Finish in one week, not two.” By creating a backlog and organizing it into "To Do," "Doing," and "Done" columns, he built a system that made each step feel doable. Pro Tip from Noah: “Once I see all the work laid out, it doesn’t feel impossible—it feels like a game plan.” This is the power of mini-Scrum: clarity, ownership, and momentum. Follow along this week as we share his daily board updates—and if you want to empower your teen to manage school with confidence, check out the book he wrote to teach them how. 👉 Follow us on LinkedIn for the series and visit the Scrum For Teens to learn more! #ScrumForTeens #ParentingTips #StudentSuccess #TimeManagement #HighSchoolHacks #ScrumInSchool

2

2 Comments

Five days can change your product direction. Design sprints align teams around complex challenges through structured problem-solving. You move from vague ideas to tested prototypes in one week, saving months of misaligned development work. Speed matters when you need clarity fast. https://lnkd.in/eUe6_eQ3 #DesignSprints #ProductStrategy #AgileMethodology #HighlandSolutions #RapidPrototyping

2

Reflections from Our Recent PI Planning Event – Growing in Flow and Collaboration - A Kanban Reflection We just wrapped up our recent PI Planning event in Memphis, TN — and this one stood out. Not because everything went perfectly (it didn’t), but because of how differently the teams approached challenges this time. Over the past few quarters, I’ve seen both our Scrum and Kanban teams evolve — moving away from reactive problem-solving toward proactive system thinking. And that shift was clear in Memphis. 🌱 What’s Improving ✅ Better conversations. Instead of hearing “You need to get this done,” I heard, “Let’s look at priorities, dependencies, and constraints.” That’s a huge cultural shift — from command and control to collaboration and shared accountability. ✅ Self-driven improvement. Teams are starting to identify their own process bottlenecks and taking the initiative to address them. No waiting for top-down fixes — just continuous learning and adjustment. ✅ Working together, not apart. Less finger-pointing. More curiosity. More collective ownership when things got tough. That’s what maturity looks like — whether you use Scrum, Kanban, or a hybrid flow model within SAFe. 🔍 What We Can Improve 🔸 PO availability. We noticed Product Owners being pulled in multiple directions during PI Planning. Next time, we’ll ensure the PO’s stay anchored in a designated room to maintain steady feedback loops with their teams. 🔸 Early dependency visibility. We’ll begin identifying and documenting dependencies at least three weeks before PI Planning. This gives teams and ARTs more time to align and mitigate cross-team risks early. Small adjustments like these have a big impact — they create smoother flow and more predictable delivery. 💡 The Bigger Reflection Whether in Scrum or Kanban, agility at scale isn’t about velocity charts or story counts. It’s about how we learn together, align around value, and continuously improve the system that supports us. In this PI, I saw evidence of that shift — from individuals managing tasks to teams managing flow. That’s what sustainable agility looks like in practice: • Teams owning their improvement journey • Product thinking guiding prioritization • Conversations focused on value and constraints, not blame We’re still learning, still evolving — but we’re moving in the right direction. And that’s exactly what agility is supposed to be: a journey, not a destination. #Agile #SAFe #PIPlanning #Kanban #Scrum #Leadership #Flow #ContinuousImprovement #Teamwork #AgileMindset

2

Staying on top of trends is key to being a great Scrum Master—after all, you’re helping your team stay agile literally and figuratively. Here are some ways to stay sharp: 🌐 Stay Plugged In - Follow Agile Thought Leaders: Folks like Lyssa Adkins, Mike Cohn, or Melissa Perri often post insights on LinkedIn and Twitter/X. - Join Communities: Online groups like the Agile Alliance, Reddit’s r/scrum, or the Scrum Master Toolbox community are buzzing with real-time discussions. - Podcasts & Newsletters: Check out Scrum Master Toolbox Podcast, Agile for Humans, or newsletters like Agile Weekly for bite-sized trend updates. 🎓 Invest in Learning - Certifications: Stay fresh with advanced Scrum certifications like A-CSM or Certified Scrum Professional (CSP). - Webinars and Meetups: Platforms like Meetup.com often host virtual Agile events where ideas fly faster than Post-its in a retro. 📚 Read with Purpose - Blogs & Articles: Medium, InfoQ, and the Scrum.org blog are treasure troves for Agile trend spotting. - Books: Keep an eye out for new releases that focus on agility in hybrid environments, team coaching, or Agile in AI-driven workplaces. 💬 Be a Mentor and a Learner Teaching others or mentoring junior Scrum Masters is a sneaky-good way to stay on trend—it forces you to articulate modern practices and adapt when others bring fresh perspectives.

11

2 Comments

Are you running daily standups the wrong way? Most Scrum Masters make this mistake. Watch to find out how to fix it, and follow for more Scrum tips!

3

🚀 Developing Transformation Roadmaps that Align Multi-Domain Teams Successful transformation isn’t about isolated projects, it’s about synchronizing technology, operations, product, finance, and compliance toward a shared vision. A strong roadmap acts as the alignment engine that connects strategy to execution. Begin with a clear 🌟 North Star, assess current capabilities, and identify gaps. Cluster initiatives into strategic themes💡 digital modernization, 🎧 customer experience, 🔐 compliance, so every domain understands the outcomes they power. Translate themes into value streams and epics, enabling teams to see how their work drives measurable business impact. Use 🤝 joint planning, 🔗 dependency mapping, and 📊 shared capacity models to maintain alignment. A modern roadmap must be iterative, time-phased, and flexible, adapting to shifts in markets, technology, and regulation. Embed transparent governance, continuous feedback loops, and data-driven checkpoints to ensure progress stays on track. A great roadmap is more than a plan, it’s the bridge between strategy and execution, ensuring every team moves with clarity, intent, and shared purpose. 🌐✨ ⏩ Empower your teams to move with clarity, alignment, and confidence. 📌 Follow Sagar K for insights on driving enterprise transformation and building high-performance, cross-functional teams. ♻️ Repost to inspire strategic alignment and smarter transformation in your network. #DigitalTransformation #AgileDelivery #EnterpriseArchitecture #ChangeLeadership #ProductStrategy #Roadmapping #TransformationLeadership #BusinessStrategy #CrossFunctionalTeams #FutureReady

2