METAGILE Academy

Science Just Rediscovered a Rule Scrum Never Forgot Every good team runs on one quiet belief. You cannot improve what you cannot see. That belief has a name in our world. Empiricism. It is the reason Scrum exists at all, and it rests on three pillars Jeff Sutherland has taught for decades. Transparency. The work is visible and honest. Inspection. You examine what is really happening, not what you hoped. Adaptation. You change based on what you found. Simple to say. Hard to live. This week a new research tool caught my attention, and it made those three words feel current again. Anthropic released Claude Science, an AI workbench for researchers. Every figure it produces arrives with the exact code that made it, the environment it ran in, a plain language note on how it was built, and the full history. In other words, the work inspects itself. Nothing hidden. Every result traceable back to its source. That is transparency and inspection, built into the tool. At METAGILE Academy have taught over 300 people to run teams this way. The pattern never changes. Teams that make their work visible get better. Teams that hide it stay stuck, no matter how talented they are. The tools will keep changing. The principle will not. If you made one hidden thing visible on your team this week, what would it be? #Scrum #AgileLeadership #Empiricism #ScrumMaster #ContinuousImprovement

1,100+ GitHub stars in 3 days — I didn't expect this. I built an open-source PM Skills Marketplace for Claude: 100+ skills and commands that turn AI into a product management partner. Not generic prompts. Structured skills that actually know PM frameworks. 8 plugins covering the full PM lifecycle: → Product Discovery: problem & solution space exploration → Product Strategy: vision, business model, strategy docs → Execution: PRDs, OKRs, roadmaps, sprint planning, user stories → Market Research: personas, segmentation, TAM/SAM/SOM → Data & Analytics: cohorts, A/B testing, retention analysis → Go-to-Market: GTM strategy, beachhead, ICP, growth loops → Marketing & Growth: positioning, North Star Metric → PM Toolkit: including PM resume review Built for Claude Code and Cowork. Compatible with Gemini CLI, Cursor, Codex CLI, and Kiro. Repo URL + instructions for Claude Code & Cowork: https://lnkd.in/dxdTj24P Want to contribute? The repo is open. Check CONTRIBUTING[.]md. For more about Cowork, see the Ultimate Guide for PMs: https://lnkd.in/dyY-jhvG

A samurai wrote the best Agile book 400 years before Agile existed. In 1645, Miyamoto Musashi retired to a cave and wrote "The Book of Five Rings." He had fought over 60 duels to the death. Never lost once. The book was not about sword techniques. It was about strategy, adaptability, and mastering fundamentals so deeply that you could respond to any situation without hesitation. I have read it seven times. Every time I find another principle that applies directly to how I coach teams. Here is what a 17th century samurai understood that most companies still get wrong. "Do not have a favourite weapon." Musashi trained in every weapon available. He won duels using a wooden sword carved from an oar. The warrior who depends on one weapon is predictable and vulnerable. This is the strongest argument against defaulting to Scrum I have ever encountered. Alistair Cockburn has made this same case for decades. The methodology must fit the ecosystem. The framework is a tool. The moment you depend on it, it becomes a limitation. "Perception is strong and sight is weak." Seeing is surface level. Perceiving is understanding what is actually happening. Teams see velocity going up and assume they are improving. They see ceremonies happening and assume Scrum is working. But is the team delivering value? Is the Product Owner making real decisions or just managing a list? Metrics without understanding are just numbers on a wall. "Think lightly of yourself and deeply of the world." Ego is the greatest threat. Not the opponent. Not the weapon. The best Scrum Masters and Agile Coaches I have worked with do not need to be the smartest person in the room. They think deeply about the team and lightly of themselves. Robert Greenleaf described this as servant leadership. Musashi wrote it four centuries earlier. "From one thing, know ten thousand things." Mastering one discipline gives insight into all disciplines. Geoscience taught me systems thinking. Aerospace taught me inspection. Environmental science taught me collaboration. Every domain sharpened my Agile coaching. David Epstein documented this in "Range." Generalists who connect knowledge across fields outperform narrow specialists in complex environments. "There is more than one path to the top of the mountain." No single correct approach. Only the approach that fits your context. The Scrum Guide reflects this. It is intentionally lean. It provides boundaries, not instructions. The teams that thrive understand this. The ones that fail are looking for a fixed recipe. A samurai in 1645 understood adaptability, ego, and contextual strategy better than most organizations do today. Have you ever found unexpected Agile wisdom in a book that had nothing to do with Agile? #Framework #Agile #Leadership #ScrumMaster #AgileCoaching #ContinuousImprovement

Most candidates treat job applications as one big blur. Hiring teams do not. Each step has a very specific purpose. How to think about each step when applying for a job: 1. CV Purpose: Give fast context about your skills and experience. Key takeaway: The CV is written for machines first, humans second. Pass automated filtering. Gets the hiring manager to read your introduction letter. Example: If the job asks for Python and SQL, those words must appear clearly in your CV, then your CV shows up in the pile worth looking at. 2. Introduction letter Purpose: Explain who you are and why this role and company make sense. Key takeaway: The letter is what gets you the first interview. Example: Link your past work to their product, not your life story. 3. First interview Purpose: Confirm you are real, clear, and consistent with your application. Key takeaway: This is a human filter, not a deep skills test. Example: Use short STAR stories to explain how you handled real situations. 4. Second interview Purpose: Check culture fit, mindset, and professional maturity. Key takeaway: Managers want to know how you think and work with others. Example: Explain how you deal with ownership, feedback, or conflict. 5. Technical interview Purpose: Validate that you can actually do what you claim you can do. Key takeaway: Skills are proven by problem-solving, not titles. Example: Walk through how you would solve a real task step by step. 6. Team interview Purpose: Let the team decide if they want to work with you daily. Key takeaway: People hire individuals they trust and can collaborate with. Example: Listen well, ask smart questions, and be easy to talk to. Final note - Processes vary by company. - The intent behind each step almost never does. When you understand the purpose of each step, you stop overthinking and start performing. Comment and tell me WDYT. #interview #application #hiring #tips #cv #job

Is your "Lead #QA" actually a bottleneck in disguise? #SCRUM #MANTRA 2/5: The Scrum Guide is radical: No sub-teams. No #hierarchies. Yet, many organizations still cling to a "QA Manager" or "Lead Tester" sitting outside the Scrum Team. The Conflict: 1. The external lead wants to #control the "how." 2. The Scrum Team is #accountable for the "Definition of Done." The Shift: In high-performing Scrum, the "Lead" becomes a #Coach. They don't #approve the work; they #enable the Developers to own the #quality themselves. Can a team truly be self-managed if an outsider has the final "Sign-off" on quality? Gustavo Avila, I’d love your take on this tension too. #ScrumMaster #Leadership #AgileTransformation #DoD #scrummantra Here go to the SCRUM MANTRA 3/5: Testing vs. Checking https://lnkd.in/e5shncJU Source: METAGILE Academy - Scrum Mastery Series: Preparation for the PSM I Certification

Signs Your Company Is Doing “Fake Agile” (aka Zombie Scrum) Agile was designed to help teams respond to change, deliver value early, and continuously learn. But in many organizations, Agile looks alive on the surface, ceremonies are running, boards are updated, and roles exist, yet the real spirit is missing. This is often called Fake Agile or Zombie Scrum. Here are some clear signs your company might be trapped in it. 1. Scrum events exist only as rituals. Daily Scrums feel like status reporting to managers. Retrospectives produce action items that never get implemented. Sprint Reviews are demos with no real feedback. The meetings happen, but learning doesn’t. 2. teams are “Agile” in name but not in autonomy. Work is still fully dictated top down. Teams cannot change scope, experiment, or challenge priorities. When decisions are centralized, agility becomes impossible. 3. success is measured by output, not outcomes. Velocity, story points, and deadlines dominate conversations, while customer value, business impact, and learning are ignored. Teams deliver more, but not better. 4. Agile is used as a control mechanism. Micromanagement is hidden behind Jira boards and burndown charts. Instead of trust and empowerment, there is pressure, fear, and constant urgency. 5. there is no real adaptation. The same problems appear sprint after sprint, but nothing changes. When teams stop improving, Scrum becomes a zombie: moving, but lifeless. Real Agile is not about frameworks, it’s about mindset, data informed decisions, and continuous improvement aligned with strategy. If you recognize these patterns, it’s not a team failure. It’s usually a system and leadership problem. If you want to move from Zombie Scrum to real, outcome driven Agile, let’s connect and discuss. I will be happy to help your organizations turn Agile into measurable business impact. #Agile #Scrum #FakeAgile #ProjectManagement #Leadership