Emilia Krzowska

🔥 NEW ARTICLE: "Scrum Certificates: Imaginary Competences – Why We Pay Thousands for Worthless Paper?" 🔥 Martin Fowler, one of the Agile Manifesto signatories, stated bluntly: "Certification is not proof of skill; it's proof of the ability to pass a certification test." Research by Justin Kruger and David Dunning shows how two-day certification trainings can lead to a false sense of mastery – their famous Dunning-Kruger effect in action. Daniel Kahneman, Nobel laureate, describes this as the "illusion of knowledge" in his groundbreaking work. The annual State of Agile Report reveals that despite growing numbers of certified practitioners, 48% of respondents still report problems implementing Agile due to lack of experience and skills. Meanwhile, Amy Edmondson's research at Harvard Business School proves that psychological safety – crucial for Agile teams – requires competencies impossible to verify with multiple-choice tests. Alistair Cockburn, Dave Thomas, and Henrik Kniberg have all raised important concerns about the certification industry's impact on authentic agility. Read my full analysis here: https://lnkd.in/dAHqaqPf What has been your experience with the gap between certificates and real skills? #AgileAlchemist #Scrum #AgileCertification #ScrumMaster #ProductOwner #LearningByDoing

10

Vercel require every developer to ship one polish fix every Wednesday. 1,000+ micro-improvements later, the experience doesn’t just work. It feels effortless. That matters because users can’t always tell you why something feels off. But they feel it. And they leave. The small stuff compounds: a smoother flow, a clearer error message, a loading state that doesn’t feel broken. Individually, they’re invisible. Together, they’re the difference between something people tolerate and something they trust enough to convert on. You don’t get that by waiting for a big redesign. You get it by building a culture where small improvements are everyone’s job, every week. Polish isn’t perfectionism. It’s a compounding investment in trust.

15

2 komentarze

This week, Irina Bindule and I attended AgileByExample Conference 2025 in Warsaw — two days of real stories, no theory, no textbook talk. One of the strongest impressions again — Dmytro Yarmak 🇺🇦 . We first heard him two years ago in Tallinn at Agile Saturday, when his talk “A true story of Agile coaching in Ukrainian Armed Forces” completely reshaped how I saw coaching. Now it felt even deeper. Key insights: • The shift from firefighting to proactive work — even in military structures there’s a space between command and control: there is an option in between. • If I have information, I have power — information gives choice, and choice brings responsibility. • Trust can’t be ordered. Dmytro traveled to sites, knew people by name. • Knowing “why” prevents endless rework of what. • After Action Review — a format that works equally well in the field and in software teams. • Motivation isn’t external. Purpose, autonomy, mastery remain the three anchors in any system. Hearing Dmytro again, you realize — these principles aren’t from books. They’re lived. They demand practice, not discussion.

45

1 komentarz

As I logged into work this morning at Commerzbank Digital Technology Center Prague, I wasn’t thinking about where I broke off last Friday. My mind was focused instead on something bigger: What is the current state of our product? As QA, I start each day by reviewing the results of our morning automated test run, a smoke test of high signal checks that run on critical user flows before most of the team even logs on. They answer key questions such as: ❓Did anything critical happen overnight? ❓Are core workflows intact? ❓Are the environments clean and stable enough for deeper testing? These morning smoke tests give us a realtime pulse on our product’s health and help us make that shift from a reactive narrative to a more proactive, systems aware mindset. How does your team leverage automation/your automation portfolio to find issues before they become blockers? #TestAutomation #QualityAssurance #SoftwareTesting

10

Just listened to Michal Ostruszka on "Better Software Design" podcast discussing event delivery patterns, and one insight really hit home: Most developers (myself included) jump straight to complex messaging patterns because they're "cool" or "trending." It's hard to say cool, without thinking distributed systems. Apparently, here's the crash course in messaging reality: ❌ "The network is reliable" (it's not) ❌ "Messages always arrive in order" (they don't) ❌ "One message = one delivery" (prepare for duplicates) The pragmatic approach:  1. Start with Fire & Forget + monitoring 2. Add complexity only when manual intervention becomes unmanageable 3. Choose patterns based on business impact, not technical coolness Before implementing that shiny new Outbox pattern, it's worth to ask: "Will this failure happen once a year or once a minute?". 🎧 Worth a listen: https://lnkd.in/dt9fcJbE

6

1 komentarz

Startups don’t fail because people are lazy. They fail because ownership is unclear. I’ve seen teams work 14-hour days — yet still miss launch deadlines. Designers polish, engineers fix bugs, marketing drafts campaigns… but nobody knows who’s accountable. That’s where the RACI Matrix comes in. A deceptively simple framework that clarifies: - Responsible → Who does the work - Accountable → Who owns success/failure - Consulted → Whose input matters - Informed → Who needs updates In this carousel, you’ll find: ✅ A startup launch story that shows why RACI matters ✅ A breakdown of each role with examples ✅ Slack’s case snapshot of applying RACI at scale ✅ A mini-playbook & pitfalls to avoid And the best part? You don’t have to stop at theory. You can practise the RACI Matrix in a Generally Critical Startup Simulation — because #TheoryIsNotEnough. Simulation Links in Profile. #Leadership #Execution #RACI #StartupLife #GenerallyCritical

22

3 komentarze

What if some of the most popular “laws” of software engineering are actually myths? At the upcoming Agile Warsaw meeting, we will challenge the commonly used principles and theories that shape the way teams and systems are designed — and ask when they are helpful and when they are misleading. 🎯 Main topics 🔍 How “laws” turn into myths ⚠️ Signs of improper use of models 🧭 More conscious and responsible decision-making in complex environments 👩‍🏫 Speaker: Uladzimir Ziankevich — engineering leader and agile coach with over 15 years of experience, known for his critical thinking and product-oriented approach. 👉 Join us if you prefer to think for yourself rather than blindly follow patterns. Registration: https://lnkd.in/dD_TfJyH Special thanks to DXC Technology for their hospitality, coffee, tea, light snacks, and QAgile for recording of the session.

7

Breaking the unwritten rules of testing can feel risky, but it often helps teams build automation that is more adaptable and easier to maintain. At this year’s Tester Summit 2025 (online), Krzysztof Kijas will explore when stepping outside standard patterns leads to more effective test design. He will also dive into how Agents and MCP can be used in creative, purposeful ways to improve quality - from exploring websites and running accessibility checks to creating custom instructions and dedicated agents that take over repetitive tasks.   Additionally, he will cover key security considerations, showing how to apply automation and AI safely without introducing new risks.   It’s a talk for testers who want to look past routine guidelines and bring a more flexible mindset into their daily work. If you’re joining on 9 December, make sure to catch his session. It brings a clear, practical perspective on automation without sticking to rigid rules. 👉 Register your free spot here: https://testersummit.pl

26

5 komentarzy

Why the 'Why' Matters—Product Owner Communication Lessons Helping Product Owners shine, and dealing with PO anti-patterns. Stories by Simina Fodor https://lnkd.in/dQYSzcQw #agile #lean #kanban #scrum #leadership @duarte_vasco

1

Hiring based on polish means you’ll miss out on potential Some of the strongest engineers don’t have flashy Figma decks or shiny resumes They ship, iterate, and solve real-world problems—quietly but impactfully Know where to look Hire beyond the surface #StartupHiring #TechRecruiting #HiddenTalent #HorusRecruiting

1

How is being a project manager in a bank different from running projects in outsourcing? After 1,5 year of managing IT projects in a bank, I’ve noticed how different the sense of responsibility feels when you’re part of the internal product vs working as an external team. In a bank, you’re part of the product and the long‑term strategy. 1️⃣ You dive deeper into business processes, bank culture and see how your decisions affect real people: colleges and clients. 2️⃣ The focus is on stability, integrations, prod monitoring and compliance. 3️⃣ There’s a strong emphasis on internal infrastructure and cross‑team dependencies. In outsourcing: 1️⃣ The main goal is to deliver results for the client - on time and within budget. 2️⃣ You have to balance between technical quality and client expectations. 3️⃣ Communication becomes your most powerful tool + enhancing negotiation skills. If banking projects are built around infrastructure, prod stability and regulatory compliance, outsourcing demands agility and the ability to adapt quickly when priorities and client’s direction change. I believe strong project managers can combine the best of both worlds: ✅ the structure and risk awareness of corporate environments, ✅ within the adaptability and focus on results and client’s satisfaction.

41

1 komentarz

Stop Making These Mentoring Mistakes (The Questions Everyone's Too Afraid to Ask) Yesterday, together with Karolina Kordyś we shared our mentor-mentee journey at Online Scrum Master Summit. Two questions came up repeatedly from the audience, and they deserve honest answers. "How do you ask someone to be your mentor when everyone is so busy?" Don't ask for "mentoring" - ask for something specific. Instead of: "Would you be my mentor?" Try: "I'm working on [specific challenge]. Could I ask you 3 questions about your experience?" Start small: Ask for a 15-minute coffee chat, not a 6-month commitment Come prepared with specific questions Follow up with what you implemented My mentoring relationship with Karolina started through a networking connection who mentioned a mentoring program. Most successful relationships start informally and grow over time. The truth: Don't ask for mentoring - ask for advice, and let the relationship develop naturally. "How much does mentoring cost?" In most cases: Nothing. - Workplace mentoring programs are typically free - Industry programs are usually free or very low-cost - Informal relationships are based on mutual benefit When it does cost money: Executive coaching (different from mentoring) Specialized programs with extensive resources What mentors get in return: - Fresh perspectives and reverse mentoring - Satisfaction from helping others grow - Expanded networks - Leadership skill development My Experience: Looking back at my journey with Karolina: Time investment: 4-5 hours per month Real investment: Being committed, prepared, and open to feedback The Bottom Line Don't let fear of "bothering" someone or cost concerns stop you. The key is to: Start small - ask for advice, not commitment Be specific - know what you want to learn Show value - demonstrate you'll act on guidance Look for programs - many organizations offer structured mentoring Remember: my career change started with frustration and asking "What can we do different?" Mentoring was the accelerator that turned scattered efforts into focused action. Have you had a mentoring experience? What questions do you still have about these relationships? Feel free to connect if you'd like to share experiences or learn more about my career change journey. Online Scrum Master Summit Scrum.org Women in Agile Europe

40

2 komentarze

🍳Who knew that cooking and building AI-native applications could have so much in common? Jolanta and I explored the ways that the developer journey mirrors the evolution from an experimental cook to a professional chef. Both journeys require creativity, planning, and the ability to scale from simple beginnings to complex operations. Through a culinary lens, the article breaks down how developers move from setup and experimentation (Day 0), to production readiness (Day 1), to long-term reliability and scaling (Day 2). Whether you're using Weaviate Cloud or open source, it’s about finding the right balance between creativity, control and consistency. This was my final technical blog with the Weaviate team so it's bittersweet but I am deeply grateful to my former colleagues who ensured that this piece was published after my layoff. Seeing it live reminds me that meaningful work continues to speak for itself and I'm proud of what we built together. Read the full article here 👇 🔗 https://lnkd.in/eJPRmHud

4

It's the 'English Weekend' on my profile! But today... there is no code. No architecture patterns. No rants about AI or corporate Agile. To be completely transparent: this post was scheduled automatically. As you are reading this, I am currently cruising down a highway somewhere in Poland. Today, I made a very strategic, highly calculated decision: I packed my family into the car, paid for ridiculously expensive fuel, ate some completely unhealthy roadside junk food, and we are heading to a place whose "uniqueness" very few people actually believe in. Why? Just because. And here is the biggest plot twist of the week:  I did not bring my laptop. (I know, shocking for an IT guy). We talk a lot on this profile about discipline, continuous learning, stepping out of your comfort zone, and being a "One-Man Army." But here is the brutal truth that we often forget in our industry's hustle culture: You cannot run a server at 100% CPU capacity forever without it eventually melting down. Your brain works the exact same way. A hard reset is not a sign of weakness or a lack of ambition. It is a critical maintenance requirement. If you don't intentionally change your perspective, step away from the glowing screens, and do something completely "unproductive," you will have zero energy to face the real engineering challenges on Monday. The bugs will wait. The CI/CD pipeline will survive without you constantly refreshing the dashboard. The framework documentation will still be there tomorrow. Give yourself permission to completely disconnect. Be present with your people. Eat the bad food. Drive to the weird places. Recharge your batteries. What is your completely "unproductive" plan for this weekend? How do you force yourself to close the IDE in your head? 👇 #WorkLifeBalance #MentalHealth #DeveloperLife #Disconnect #WeekendVibes #ITProfessional #BurnoutPrevention https://lnkd.in/d6QuzChK - Chill, debug, enjoy the code!

3

🔍 The Sin of “L” – Literalism: when a Scrum Master treats the Scrum Guide like holy scripture. One of the talks at yesterday’s Scrum Summit in Warsaw really hit home for me: being overly literal in agile can kill its spirit. 📌 “Because the Scrum Guide says so…” — how many times have we heard that? Sticking strictly to the letter, without understanding the intent, the team’s context, or the actual goals, often turns agile into a set of empty rituals. Instead of empathy — checklists. Instead of conversation — quotes from the guide. This slide was part of a brilliant presentation by Radek Orszewski who tackled agile’s “deadly sins” with humor and spot-on insights. ➡️ It reminded me that the hardest part of agile isn’t knowing the framework — it’s applying it with flexibility, empathy, and common sense. That’s exactly what this conference was about — and I’m truly grateful to have been a part of it. #agile #scrum #scrummaster #leadership #ScrumSummit #RadekOrszewski #agilecoaching #continuouslearning #peoplefirst

11

1 komentarz

🚀 Excited to launch my latest project 👉 Zenix! After months of building bit by bit (and refactoring way too many times 😅), it’s finally ready with that extra layer of polish. Zenix is an end-to-end platform that simplifies Indian tax prep 👉 no more spreadsheet chaos, no more juggling PDFs. With this, I might just replace a few CAs (kidding… or am I? 😂). 🎥 Check out the full demo: edited entirely by yours truly. 🧩 Tech Stack Breakdown Frontend: React 18 + TypeScript SPA powered by Vite, styled with Chakra UI, Tailwind, and Material UI. Routing and state flow via React Router, context-based auth guards, toast notifications, Axios, Framer Motion for animations, Lucide/React Icons, and Recharts for analytics visualizations. Backend: Built with FastAPI (async routes) handling document ingestion, uploads, tax logic, and analytics. Uses Pydantic for configuration, centralized logging, and async SQLAlchemy for data access. Document intelligence routes PDFs/CSVs/XLS/images to processors (Form 16, payslips, or bank statements). There’s also a Node/Express sidecar with Multer + pdf-parse for auxiliary pipelines. AI Power: Landing AI drives extraction. OpenAI is used for insight generation, it composes regime-specific tax summaries, deductions, and spending recommendations from structured prompts. Database: PostgreSQL with async + sync engines, JSON fields, and models covering everything from assessment rollups to categorized transactions. Auth: bcrypt via Passlib, JWT-based tokens with strict verification, and multi-level route protection. (Still expanding on security because in finance, it’s everything.) 💡 Still a lot more to do, but I’m proud of how far it’s come. Would love to hear your thoughts, suggestions, or even your “CA panic” reactions 😄 #Zenix #TaxAutomation #FastAPI #React #OpenAI #LandingAI #FinTech #IndieDev #Python #TypeScript #Vite #AI #ProjectLaunch #DeveloperJourney #StartupLife

33

4 komentarze