New Edition of "First Principles in Scrum: Foundations" Released

***Agile Beyond IT: Scrum in Everyday Life*** When we talk about Scrum, most people picture software development. But the truth is – Agile is a mindset, not just a method. 👉 Imagine planning a family trip: You don’t create a year-long fixed plan. You break it down into smaller steps – destination, budget, bookings. You adapt based on feedback – weather changes, kids’ preferences, last-minute offers. Sounds familiar? That’s Agile in action. I’ve also seen teams in marketing, HR, and even education using Scrum practices to: Work in short, focused iterations. Continuously improve instead of waiting for a “big reveal.” Deliver value faster, with flexibility. 💡 The key takeaway: Scrum isn’t limited to code – it’s about collaboration, adaptability, and delivering value wherever people work together. 🔄 What’s the most surprising place you’ve seen Agile practices at work outside IT? #Agile #Scrum #Leadership #Collaboration #AgileBeyondIT

🇺🇸 Follow the rules or break them? Knowing the right time is the secret to success. You know that discussion about adapting Scrum? "This ceremony doesn't work for us," "let's change this here"... We live this dilemma, right? But calm down! There's a right way to do this "tailoring" without everything turning into a mess. The Japanese concept of Shu-Ha-Ri is like a map for this journey. Think of it as a 3-stage video game: Phase 1: Shu (Obey) This is the "copy and paste" mode. We follow the method's manual to the letter. No trying to reinvent the wheel! The goal is simple: to create a strong foundation and truly understand why every little thing exists. Phase 2: Ha (Break Away) Alright, we've mastered the basics! Now we can start breaking the rules, but INTELLIGENTLY. This is where tailoring really happens. "What if our Daily Scrum was at a different time?", "Let's test a different approach on the Kanban board?". We make changes, but because we understand the impact and the objective. Phase 3: Ri (Transcend) Jedi level! The team doesn't even think about the "rules" anymore. The agile principles are already in the team's blood. Solutions appear naturally and intuitively, creating a way of working that is unique to the team. You don't just do agile, you ARE agile. Moral of the story: before you go customizing everything, it's worth asking yourself: "have we mastered the basics yet?". Tailoring without a foundation is just confusion. With a foundation, it's pure evolution! So, what phase is your team in? #Tailoring #Agile #Scrum #ShuHaRi #ProjectManagement #ContinuousImprovement #Kaizen #AgileLeadership

Are you stuck, feeling down, and worried about writing your dissertation or conducting your research? Read this post. For several months, I have been thinking about and using the application of product management tools (like Scrum Agile) in writing and research. I finally settled with and read about Agile Methodology and mirrored it to my situation—being a husband, dad, and doctoral student. With this fictional story shared, you will find practicable lessons on how to use Agile methodologies to help you stay productive while still being available for your family. Share this post with others, too. #Scrum #PhDLife #Academia #Family #Research

If you're struggling with Scrum. I saw a post on Reddit "Tired of Scrum." I was not surprised so much by the rant against it as much as the number of people who responded who said they were told to do it. I can't help them unfortunately, because public groups in general and Scrum groups in particular don't want any self-promotion. I understand this, but the only way out is for someone to lead the way. My sense is when managers say "do Scrum" they really mean "be effective in small iterations and cadence" (if even that much). If you're trying to use Scrum, I suggest you use it as a base and then improve it - without worrying if you're breaking it's immutability. Sure, avoid change when it's bad. Do change when it's good. Scrum won't tell you how to tell you the difference, but I will. It's not a hard thing to do. In the first comment I've put a few posts that will help. I'm starting a Scrum-> Amplio Scrum soon in Amplio University. Self-guided but live support. Only $49 / month - will take you 3 months - a couple of hours a week. #Amplio #AmplioLearningJourneys quick, iterative learning.

🌟Continuous learning: the real secret behind agility🌟 Think about how a child learns to walk. 👉 They don’t get it right the first time. 👉 They stumble, fall, adjust, and try again. 👉 Every attempt teaches them something new until walking becomes natural. ✨That’s exactly what agility is about — not perfection, but progress through learning. 💡 Agility ≠ just standups or sprints Agile isn’t defined by ceremonies or frameworks. It’s defined by a mindset: • Curiosity to ask “What if we try this?” • Courage to experiment, even if it fails. • Commitment to get a little better, every day. 📌 Where continuous learning shows up in Agile teams • Retrospectives → Not just meetings, but spaces to reflect and improve. • Feedback loops → Listening to customers and adapting quickly. • Cross-learning → Developers, testers, designers sharing skills and perspectives. • Experimentation → Trying a new tool, practice, or approach — and evolving from the results. 🌟 Teams that keep learning don’t fear change. They adapt faster, stay resilient, and deliver real value — because they’re always growing, just like that child learning to walk. 💬 What’s one recent thing you or your team learned that made you more agile? #ScrumMaster #Agile #AgileTesting #AgileCoach #ProductOwner #ContinuousImprovement #ScaledAgile #SAFe #Scrum #Kanban #AgileMindset #Leadership #AgileCommunity #Agile #AgileMethologies #Scrum #ServantLeader #Coach #ScrumOfScrum #ScrumMaster #AgileLeadership

🚀 Why Scrum Isn’t Just for Software Teams Anymore 🧠 When people hear Scrum, they often think of software development. But the truth is, Scrum is far more versatile than that. At its core, Scrum is about: ✅ Working in small, cross-functional teams ✅ Delivering value in short, focused iterations ✅ Continuously inspecting and adapting ✅ Putting people and collaboration over rigid processes Whether you're in marketing, HR, operations, or even education — if your work is complex, Scrum can help you move faster, stay focused, and respond better to change. One of the biggest mindset shifts Scrum encourages: 💡 “Done is better than perfect. Deliver, learn, adapt.” After working with Scrum frameworks across various teams, I’ve seen firsthand how it: 🔹 Boosts transparency 🔹 Enhances team accountability 🔹 Shortens feedback loops 🔹 Builds a culture of continuous improvement If your team is stuck in long planning cycles or struggling with shifting priorities, it might be time to consider a Scrum approach. #Scrum #Agile #Leadership #ProjectManagement #ContinuousImprovement #Teamwork #AgileMindset

If there is one thing we ask students to remember from our courses it is the Principles and Values, the soul of Scrum. As Scrum.org describes "Values are the principles we view as important in the way we live and work. They are the core beliefs that guide our actions, behavior and decisions" These values are universal and cross culturally applicale. We us it to facilitate understanding within Scrum teams and organizaiton. A simplified version in three steps Step 1 - inspect the values Step 2 - individually write down what behaviors indicate application of the values Step 3 - Create a common understanding of the bahaviors How do you apply the scrum values, and how do you make it come alive? You can download the infographic for free at our website. https://lnkd.in/e4HMcDyi 🎁 All our content is 100% free to download 🎁 You can alter all our products and even use them commercially (YES, even commercially) 🎁 We make €2,50 profit if you print our products. this profit goes to our Scrum Facilitators foundation ❌ We don't require your email address to download our products

Iterative without incremental is daydreaming. Incremental without iterative is guesswork. Scrum’s power comes from combining the two. What’s the difference between “iterative” and ”incremental”? And why does Scrum need both? Many people use these words interchangeably—but in Scrum, they point to two complementary superpowers. From the Scrum Guide: “Scrum employs an iterative, incremental approach.” From Cambridge Dictionary: - Iterative – doing something again and again, usually to improve it - Incremental – happening gradually, in a series of small amounts Iterative in Scrum Iteration is about learning loops. Doing something again and again, each time improving based on what you learned last time. In Scrum, the Sprint is the heartbeat of iteration. Every Sprint: - You plan together - You build - You review - You reflect and adapt Then, immediately after one Sprint ends, another begins. Analysis, design, build, validate, release—done again and again. Each loop is a chance to adapt the plan, the product, and the process. Incremental in Scrum Incremental is about delivering in small, usable chunks. In Scrum, the Increment is the output that adds value to your product—piece by piece, Sprint by Sprint. - Product capabilities grow gradually - Users can understand and give feedback on each step - The way of working improves a little each Sprint - Skills in the team increase over time Why both matter? - Only iterative? You could end up improving the wrong thing forever without ever delivering value. - Only incremental? You could deliver lots of small pieces without learning if you’re on the right track. Scrum combines both so you’re constantly learning, and constantly delivering. Your turn: - What are you and your team iterating on right now? - What’s your latest Increment? Share an example—let’s make it visible. Drop a comment—or tag someone whose might benefit from this. These are core concepts I cover in my Professional Scrum courses. Curious to learn more? Watch out for upcoming posts—or contact me directly. Wishing you a wonderful journey. Have fun. Scrum on. #BoostYourScrum #ProfessionalScrum #Scrum #ScrumMaster #Simplify Scrum.org

Scrum isn’t agility. It’s bureaucracy dressed in a hoodie. It’s easy to dunk on Scrum. I’ve done it plenty. But saying “this sucks” is cheap. Offering alternatives is the hard part. Here’s what I’ve learned after years of living inside engineering processes that worked—and a lot that didn’t: 🔄 Principles over process The best teams align on goals, keep updates short, and spend time together solving problems—not reciting status. 🧩 Flow > sprints Sprints create artificial deadlines and fake velocity. Continuous flow, clear visibility of work, and limiting WIP beats the burndown chart every time. 🎯 Outcomes > points Story points don’t matter. Customer adoption, uptime, and cycle time do. Impact beats points every time. 🛠 Habits, not rituals Shipping is a habit. Reflection is a habit. The power comes from consistency and intention—not from a calendar invite. Scrum makes people feel safe because it’s a box to check. But process is a comfort blanket, not a cure. If your team can’t function without heavy rituals, you don’t need more Scrum—you need more trust. #EngineeringLeadership #Agile #ProductDevelopment #TeamCulture #Leadership