Implementing Agile Methodologies for Teams

Agile vs Lean vs Design Thinking. (Finally explained in plain language.) 3 methodologies. 3 different strengths. All essential for different moments. Here's what each actually does: 💡 Agile builds software that adapts as you learn. Sprint by sprint. Feature by feature. Feedback loop by feedback loop. 💡 Lean strips waste from any process. Less inventory. Less waiting. More value delivered faster. 💡 Design Thinking starts with human needs. Watch. Listen. Prototype. Test with real humans. Real-world applications that show the difference. Startup examples: Agile: Spotify's 2-week sprints ship 1000+ updates daily Lean: Toyota eliminated 7 types of waste, became #1 Design Thinking: IDEO redesigned shopping carts by watching shoppers struggle Enterprise transformations: Agile: ING dissolved departments for 2500+ squads Lean: GE Six Sigma saved $12 billion in 5 years Design Thinking: IBM trained 100,000+ employees, added $20M revenue The practical breakdown: When Agile shines: → Digital products need constant updates → Customer needs shift monthly → Teams need clear 2-week goals When Lean dominates: → Processes have too many steps → Costs spiral out of control → Speed to market matters most When Design Thinking wins: → Users struggle but can't say why → Innovation needs a human spark → Problems are complex and fuzzy Here's how they complement each other: Design Thinking discovers what to build. Lean ensures you build it efficiently. Agile helps you build it adaptively. Each methodology asks different questions: Agile: "What can we ship in 2 weeks?" Lean: "What step adds no value?" Design Thinking: "What does the user really need?" Together they create something powerful: Products people love. Built efficiently. Delivered continuously. Master one and you solve problems. Master all three and you transform organizations. Which methodology fits your current challenge? 👉 Repost to help more founders choose the  right framework at the right time. Follow Christian Rebernik for more on building high-performing teams and delivering smarter results.

Scrum as a Service: When Agile Teams Become Ticket Processors Scrum as a Service is when Agile teams are execution units, taking orders instead of owning value delivery. They don’t solve problems; or shaping the product, they just code and close Jira issues. It’s what happens when companies adopt Scrum mechanically but keep traditional thinking and control structures intact. Symptoms of Scrum as a Service 1) No Product Ownership The PO is a backlog manager, not a decision-maker. Teams can’t challenge priorities. The backlog is a job assignment queue. Sprint Planning is a scheduling exercise, not a conversation about functional or technical trade-offs. 2) No Cross-Discipline Collaboration UX, DevOps, and Security exist outside the team, creating slow handoffs. Developers get fully fleshed-out requirements, not problems to solve. Agile teams are ticket processors, not value creators. 3) Nothing Changes Daily Scrums become status meetings for managers. Retros don’t lead to improvements, just performance reviews. Teams are judged by team outputs like velocity, not business outcomes. How This Happens 1) No Organizational Change Leadership keeps command and control, just renaming old roles. 2) Waterfall Thinking Teams have fixed scope and deadlines, no room for continuous discovery or progressive elaboration. 3) POs as Middlemen, Not Leaders POs relay stakeholder demands instead of shaping product strategy. 4) SMs are Managers. Not Coaches SMs push teams to move faster rather than helping them achieve a sustainable pace. How to Fix It 1) Give Teams Ownership Let teams define and prioritize their backlog. Facilitate direct feedback loops with users, not just stakeholder requests. Make POs strategic leaders, not order-takers. 2) Tear Down Silos Embed UX, DevOps, QA, and Security into the Scrum team. Stop treating devs as coders for hire. Make them coequal partners in product thinking. 3) Shift to Outcome Metrics Stop measuring success by velocity, throughput, or tickets. Track customer impact, retention, usability, and product adoption. Ask: Are we solving problems or just releasing code? 4) Decentralize Decision-Making Replace top-down roadmaps with team-driven prioritization. Let teams influence scope, trade-offs, and release planning. Encourage teams to experiment and innovate. 5) Foster Continuous Improvement Make retros actionable. Give teams time for technical excellence, like refactoring, automation, and innovation. Shift from feature delivery to sustainable, high-quality product development. From Execution Teams to Product Teams Scrum teams should be value creators, not feature factories. Agile is meant to empower teams, not turn them into Jira clerks. If teams can’t challenge priorities, shape solutions, adjust processes, or innovate, then you don’t have Agile. You have Scrum as a Service. Does your organization trust teams to own the product? If not, Scrum isn’t the problem. Your structure is.

"Start by asking for criticism, not by giving it. Don’t dish it out before you show you can take it." One of the biggest mistakes leaders make when trying to create a culture of feedback is skipping the most important step: soliciting feedback first. It’s easy to assume that because you’re open to giving feedback, others will be open to receiving it. But if you haven’t proven that you can take it yourself, you’re not setting the right example. People are naturally hesitant to challenge their boss directly. The risk feels high. That’s why it’s on you to make it safe - to show that you truly want to hear what they think, that you won’t get defensive, and that their candor will be met with appreciation, not punishment. Try this: In your next 1:1, ask, “What’s one thing I could do better?” Then, embrace the discomfort. Stay silent, let them respond, and listen with the intent to understand - not to reply. Feedback is a two-way street. When you lead by example, you create an environment where honesty and growth thrive. What’s one small way you’ve worked to make it easier for people to give you feedback? Let’s learn from each other.

Let's deploy an ML model to production. Step by step ⬇️ 𝗘𝘅𝗮𝗺𝗽𝗹𝗲 Imagine today is your first day as an ML engineer at Uber, and your task is to improve the ML service that predicts the Estimated Time of Arrival (ETA), which gives users an estimate of when their driver will arrive. 𝗔𝘀 𝗮 𝘀𝘁𝗮𝗿𝘁𝗲𝗿 You -> define the problem -> talk to other data engineers and ML engineers in the team -> expand the set of model features, and -> train a promising ML model. You are happy with the results, so it is time to deploy So far you have 4 things: -> the model pickle -> a predict function, that maps input features to output predictions, using the model artifact. -> A FastAPI wrapper around your Python code, to build the REST API, and -> A Dockerfile to package everything in an isolated box. How do you deploy this code as a production ready API? 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻 -> 𝗧𝗵𝗲 𝗠𝗟𝗢𝗽𝘀 𝘄𝗮𝘆 Let’s go step by step 𝗦𝘁𝗲𝗽 𝟭 → Push code to new branch and open Pull Request (PR) Use git and Github/Gitlab to track code changes. I recommend you develop your code in a non-master branch, where you work, and push changes to remote. Once you are happy with the results, you open a Pull Request 𝗦𝘁𝗲𝗽 𝟮 → Continuous Integration (CI) The CI pipeline is a github action that is triggered automatically every time you open a Pull Request. The end goal is to make sure that your new code version, and model artifact are actually good and deserve to be promoted to production. The CI steps in this case are: -> Unit tests, e.g. make sure you feature engineering functions work as expected -> Trains the model and generates the model artifact. -> Validates the ML model performance and possible biases, using a library like PyTest or Giskard At the end, the pipeline checks can either → fail, so you need to work further on your code, or move to another project with higher priori → pass, so your model is ready to be deployed. In this case, the CI pipeline pushes the model to your model registry, from where it can later be deployed, and your branch “my_new_model” gets merged to master. 𝗦𝘁𝗲𝗽 𝟯 → Continuous Deployment (CD) The Continuos Deployment (CD) pipeline is another github action that is triggered automatically after successful completion of the CI pipeline. The role of the CD pipeline is to deploy the Dockerfile you wrote as a production ready API. In this case, our github action -> Pushes the Docker image to Uber’s docker registry, -> Triggers the deployment to your compute platform, for example - Kubernetes, with kubectl - AWS Lambda, or - Serverless platforms, like Beam or Cerebrium that do not require Docker images. ---- Hi there! It's Pau 👋 Every day I share free, hands-on content, on production-grade ML, to help you build real-world ML products. 𝗙𝗼𝗹𝗹𝗼𝘄 𝗺𝗲 and 𝗰𝗹𝗶𝗰𝗸 𝗼𝗻 𝘁𝗵𝗲 🔔 so you don't miss what's coming next #machinelearning #mlops #realworldml

Autonomy is often wrongly confused with independence. This mistake negatively affects accountability. People sometimes mistakenly think that giving people autonomy means leaving them completely to their own devices (this is independence). In the organizational sense, autonomy is not the opposite of structure—it’s the freedom to operate WITHIN a structure that supports continuous improvement and accountability. A Lean mindset and approach helps leaders to understand how to foster BOTH accountability and autonomy. Lean leaders do this by intentionally moving away from making people feel like they are "being held accountable" (which feels imposed) and inspiring them to "take accountability" (a sense of ownership that naturally fosters autonomy). Here’s how you can adopt this approach in YOUR team: 🟢 Be clear about goals, roles, and responsibilities: Use tools like RACI charts or visual management boards to clarify who does what. 🔴 Define success together: Involve the team in setting performance standards or KPIs so they have a say in what they’re working toward. 🟣 Encourage regular 1:1 check-ins and team huddles: create spaces for discussing challenges without fear. 🟡 Engage people in problem-solving: Use structured techniques and Kaizen to involve the team in addressing inefficiencies. 🔵 Ask for their ideas first: Instead of directing what needs to change, coach them with powerful questions like, “What do you think is the best next step?” 🟤 Use visual management: Team dashboards or Kanban boards make progress visible, reduce micromanagement and highlight areas needing attention. 🟠 Review metrics as a team: Make this part of regular meetings, so progress and accountability are a collective effort. ⚫ Own your commitments: If you make a mistake or miss a deadline, acknowledge it openly. ⚪ Model humility: Admit when you don’t have all the answers and seek input from the team. (This makes people feel valued!!) 🤔Reflection time for leaders... Are you balancing structure and flexibility in your team? Which of the above could you act on to shape a culture of autonomy?

The most powerful feedback conversations take under 60 seconds. Most managers spend months avoiding them. We tell ourselves we're too busy. Too rushed between meetings, too focused on the next decision, too worried about upsetting someone. So we say nothing. And instead of changing bad traits, they fester. Small performance issues become deeply ingrained habits. Good people leave feeling unseen. Here's what I've learned after 40 years in business: feedback doesn't need to be a grand, scheduled, HR-approved conversation. It needs to be honest, specific, timely, and it needs to become part of how you lead every single day. The one-minute rule:  Praise or reprimand, do it immediately after the moment, not weeks later or a half-year review. The closer to the act, the more it lands. Never mix praise with criticism in the same conversation:  If you do, people will only remember the negative. The praise disappears. Keep them entirely separate. The emotional bank account:  Think of your relationship with every colleague like a bank balance. Positive feedback, recognition, and genuine interest build deposits over time. Critical feedback makes a withdrawal. The mistake most leaders make isn't giving too much feedback:  It's making it a monologue. Real feedback is a two-way dialogue. Ask "How do you think that meeting went?" or "What could have been done differently?" instead of issuing a verdict. Be specific. Be direct. Drop the softeners:  If you open with "maybe" or "you might want to consider," the advice rarely gets followed. Candour isn't cruelty, it's respect. The more people trust you, the faster mistakes get corrected. There's also a strong business case here beyond culture. Research backed by JP Morgan data shows that companies placing a genuine premium on employee satisfaction - built in large part through strong feedback cultures - consistently outperform those focused purely on financial metrics. And critically, don't just give feedback. Ask for it yourself, regularly. The willingness to hear hard truths about your own leadership is what separates good managers from great ones. Start there. The relationships, the trust, and the performance will follow. What's the best piece of feedback you've ever received? Did it change the way you work? Every week, I share what works in business and leadership - lessons learned from 40 years of building. If that sounds useful, subscribe to my newsletter here: https://lnkd.in/ergDQtiK

🔍 Have you ever wondered how some companies keep things running smoothly, even when challenges pop up? Here’s a little insight: They’re often using Lean principles, a set of practices focused on making things simpler, faster, and more effective by cutting out the clutter. But Lean is about more than just efficiency; it’s about connecting people with their work in meaningful ways. Take visual management as an example. It’s all about making information visible and accessible. Imagine Walking into an office and immediately seeing a Kanban board showing where each project stands or an “out-of-stock” card on an inventory shelf. These aren’t just clever tools—they make work easier to understand and create a sense of ownership and accountability. And the results? Employees feel empowered to make decisions on the spot, without waiting for formal reports or meetings. According to recent studies, visual management can increase task accuracy by up to 60% in workplaces that adopt it. Then there’s gemba, or what Toyota calls the “go-and-see” mindset. Instead of guessing what’s going on from an office, managers head to the shop floor. They observe, listen, and understand what’s happening right at the point of action. Toyota Motor Corporation leads the way here, with most of its supervisors spending time on the production floor daily. And it pays off—problems get resolved faster, and solutions are based on firsthand observations, not assumptions. Finally, Continuous improvement is at the heart of Lean. It’s the mindset of always looking for ways to do things better, even if only by a tiny bit. Every tweak, every little fix, adds up over time, ensuring that the company is always moving toward giving customers more value. In fact, companies that embrace continuous improvement report a 15-20% increase in productivity over time, as noted by the Lean Enterprise Institute. And here’s what often goes unnoticed: Lean only works because it values people. Real, day-to-day improvements come from the employees who are involved in the work and whose insights and ideas shape better processes. When people feel heard, productivity grows—by as much as 30% in companies with strong employee engagement practices. So, Next time you hear about Lean, think beyond the jargon. At its core, it’s about creating a work environment where people feel connected to their roles, confident in their abilities, and motivated to make a difference every day. That’s the real impact of Lean.

Many organizations adopting an Agile or Product Operating Model often face a similar challenge: how to scale their efforts without the process becoming a rigid, 'mechanical' imitation that loses the original spirit of agility. While the universal aspiration is to have fast-moving, outcome-aligned, always-learning teams, real-world compromises in large-scale implementations can lead to a fixation on framework mechanics rather than strategic intent. The Agile Product Operating Model (APOM) Guiding Principles document compiles key insights gathered over two years across various industries (automotive, biotech, banking, retail, software, etc.). It addresses these scaling challenges by shifting the focus from a prescriptive framework to core principles. I wrote a blog post that addresses questions about the guiding principles and their intent. Here are some highlights from the blog. * From Framework to Principles: The APOM principles are designed to be a tool for assessment, not a new, rigid process. They allow you to look at any existing framework, pattern, or approach you use (like Scrum or SAFe) and determine if your implementation is correctly aligning with the underlying intent of the principle. * Focus on Behaviors: Instead of describing explicit roles or job titles, which are often loosely interpreted or appended to existing positions, the principles focus on behaviors. This allows organizations to map the required actions and accountabilities to their own unique context and existing structure. * Bridging the Gap to Implementation: The principles describe an ideal state. To move toward this state, the document suggests using the Guiding Principles and the APOM overview whitepaper to develop an assessment survey. This provides a structured, empirical starting point for analyzing the current operating model and planning improvements. * AI and the Future of the Operating Model: I also examine AI's significant impact. While AI speeds up product capabilities and improves delivery, the core principles still apply. Organizations with a strong, agile, and evidence-based product operating model are best positioned to leverage AI to become faster, smaller, and flatter. Ultimately, the fundamentals of successful product delivery remain: align teams to clear outcomes, enable frequent learning and delivery, empower them to own their work, and remove impediments. But getting there can be a challenge :-) Here is the blog.  https://lnkd.in/eTn6Em2v

𝗛𝗥: 𝗔 𝗣𝗼𝘄𝗲𝗿𝗵𝗼𝘂𝘀𝗲 𝗼𝗳 𝗣𝗼𝘀𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝗶𝗲𝘀! As HR leaders, we have the power to transform workplaces by fostering open dialogue, nurturing talent, and creating an environment where people truly thrive. 𝗘𝘃𝗲𝗿𝘆 𝗰𝗼𝗻𝘃𝗲𝗿𝘀𝗮𝘁𝗶𝗼𝗻 𝘄𝗲 𝗳𝗮𝗰𝗶𝗹𝗶𝘁𝗮𝘁𝗲 𝗵𝗮𝘀 𝘁𝗵𝗲 𝗽𝗼𝘁𝗲𝗻𝘁𝗶𝗮𝗹 𝘁𝗼 𝗱𝗿𝗶𝘃𝗲 𝗰𝗵𝗮𝗻𝗴𝗲! Recently, in a high-energy HR strategy meet, we explored a game-changing concept—𝗥𝗮𝗱𝗶𝗰𝗮𝗹 𝗖𝗮𝗻𝗱𝗼𝗿—the powerful balance of giving direct, honest feedback while genuinely caring. The conversations were raw, insightful, and deeply thought-provoking. The discussion reinforced a fundamental fact that honest conversations, when done right, fuel trust, engagement, and performance. Here are a few ways you can practice radical candor in your leadership style: 1️⃣ 𝗚𝗶𝘃𝗲 𝗽𝗿𝗼𝗺𝗽𝘁 & 𝗛𝗼𝗻𝗲𝘀𝘁 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 Example: Instead of waiting for a monthly/quarterly review, say: "Hey, I noticed in today's meeting that your presentation was great, but your conclusion lacked clarity. Try summarizing key takeaways in 3/4 bullets next time—it’ll make your point clearer!" 📌 Tip: Feedback is most effective when it is instant, so it stays relevant and actionable. 2️⃣ 𝗕𝗲 𝗗𝗶𝗿𝗲𝗰𝘁 𝗯𝘂𝘁 𝗖𝗮𝗿𝗲 Example: If an employee misses deadlines, instead of avoiding the conversation, say, "I see you've been struggling lately. I know you’re capable, so let’s discuss what’s blocking you. How can I support you in managing priorities better?" 📌 Tip: Difficult or tough conversations become easier when people know your feedback comes from a place of care, not criticism. 3️⃣ 𝗕𝘂𝗶𝗹𝗱 𝗮 𝗖𝘂𝗹𝘁𝘂𝗿𝗲 𝗼𝗳 𝗢𝗽𝗲𝗻 𝗗𝗶𝗮𝗹𝗼𝗴𝘂𝗲 Example: Invite feedback on your leadership: "I want to ensure I’m supporting the team effectively. What’s one thing I could do better to help you succeed?" or "What can I do to set you up for success?" 📌 Tip: When leaders model openness to feedback, employees are encouraged to do the same, creating a culture of trust. Radical candor isn’t about being harsh or overly soft—it’s about finding the right balance to build trust, drive performance, and create a thriving workplace. Don't be nice; be kind! #Humanresources #Leadership #RadicalCandour How do you incorporate radical candor in your leadership style?

Most teams don’t have a talent problem. They have a challenge problem. It’s not that people aren’t smart, skilled, or hardworking. It’s that they play it too safe in conversations, avoid tough questions, and hesitate to push each other’s thinking. 👇 The result? Slow decisions, missed opportunities, and a team that feels collaborative but isn’t truly high-performing. A leadership team I worked with had all the right ingredients: experience, ambition, and expertise, but their discussions stayed surface-level. They weren’t failing, but they weren’t excelling either. So, we made some tweaks.  Not by forcing more meetings, but by shifting how they work together. Here are 6 practices you can also try: 1️⃣ Mental Model Mapping Instead of debating what to do, map out how each team member thinks about a challenge. Ask everyone to write down: - What assumptions they are making - What past experiences shape their views - What risks they foresee Comparing these “mental maps” exposes team blind spots and enhances collective intelligence. 2️⃣ Curiosity Round Before giving feedback, asking this question first: “What was your thought process behind this?”. It opens up constructive dialogue instead of triggering defensiveness. 3️⃣ "Energy Audit" Method Instead of assigning tasks based only on skills, tracking what energizes or drains each team member helps optimize workflows and prevent burnout. 4️⃣ "Mistake-Learning" Sprint Once a month, instead of analyzing success stories, pick a past team failure and collaboratively discuss: - What went right despite the failure? - What invisible factors played a role? - How would we approach it differently now? 5️⃣ Red Team vs. Blue Team For big decisions, split the team into: - The Red Team (critics) who try to poke holes in the idea - The Blue Team (defenders) who justify why it will work This forces teams to think through risks and opportunities instead of making rushed choices. 6️⃣ One Bold Experiment Encourage teams to propose and test one out-of-the-box idea every quarter, with permission to fail. - Frame it as a low-risk experiment rather than a big change - Assign a “learning lead” to document what works - Celebrate insights, not just outcomes This keeps teams innovative without fear of failure. P.S.: Which one would make the biggest difference in your team? --------------------------------- Hi, I’m Susanna. I help leaders and organizations build high-performing teams through psychological safety and inclusive leadership. 🚀 Visit my website to book a free discovery call!