Jay Walters

Most SR&ED claims don't fail because of weak tech 👇 They fail because of missing documentation. Versioned design docs, commit messages that explain intent, and tagged sprint notes matter as much as the code itself. Here's a practical guide on building SR&ED-ready documentation that your future self (and your CFO) will thank you for. 🔗 https://lnkd.in/gE5wRugi Oh, and Canada Revenue Agency - Agence du revenu du Canada will thank you too. Make sure your SR&ED applications are defensible. #SRED #IRAP #RDTaxCredits #CRA

1

Most QA problems aren’t about tools or people, they’re about processes. If your testers are chasing bugs manually, your devs are guessing coverage, and your releases feel like fire drills, that’s not a resource issue. That’s a design flaw. Process is the real framework. Get that right, and everything else starts to click. #ProcessEngineering #SoftwareTesting #QualityOps #TestAutomation

24

2 Comments

🚨 Big News! Just launched my new course platform — built for Manual Testers who want to become SDETs! 🎯 I’ve officially dropped my new website → 🔗 https://lnkd.in/giMHjNwn If you’ve ever felt stuck in manual testing or unsure where to start with automation — this is exactly for you. 💡 What’s Inside: ✅ Step-by-step roadmap from Manual Tester → SDET ✅ Full GitHub framework repo to start building from Day 1 ✅ Real-world project to implement what you learn ✅ Write industry-level test cases in a guided setup ✅ Downloadable cheat sheet to save time in interviews and real projects 📌 Whether you're just starting or looking to transition your career — this course is built with real project needs in mind, not just theory. 🎁 Bonus: Comment your email + "I'm in" on my latest YouTube video teaser (https://lnkd.in/gCydxD4e) and get 20% OFF on the course! Let’s grow together. Let’s automate the right way. 🚀 #NotAnSDETYet? Let's change that. #TechByJerry #SDET #AutomationTesting #JavaSelenium #RealWorldProjects #LearnAutomation #SDET2025 #ManualToAutomation #CareerSwitch #GitHubFramework #TestAutomation #TopmateCourses

16

2 Comments

Most QA pros have tracked tests in Excel at some point. It works—until it doesn’t. ⚠️ Version chaos across drives and inboxes ⚠️ Weak password protection ⚠️ Clunky reporting and traceability Modern testing needs more than spreadsheets. From project management platforms like ClickUp or Airtable to dedicated test management tools, there are better ways to track, manage, and report. We break down the best alternatives and where TestMonitor fits in. https://bit.ly/49VXbuk #TestManagement

13

2 Comments

Playwright just released Playwright Agents, and it’s a big deal for the QA community. 🚀 The new agents can plan, generate, and even fix Playwright tests, helping teams spend less time on maintenance and more time on meaningful testing. It’s great to see automation tools evolving in ways that actually make our work faster, smarter, and more reliable!

8

STOP COLLECTING CERTIFICATES. START CHOOSING THE RIGHT ONE. Most people do certifications blindly. Wrong order. Wrong reason. Zero impact. Here’s a clean, no-fluff guide on what to do when. WHO ARE YOU Product or Scrum Master in delivery mode Engineering lead handling flow and ops Manager scaling multiple teams Career switcher exploring Agile basics WHAT TO PICK AND WHEN SCRUM When: Building new products, time-boxed sprints, cross-functional team Pick: CSM or PSM Why: Clarity on roles, ceremonies, sprint discipline Avoid if: Your work is mostly tickets, BAU, high interrupt rate KANBAN When: Support, maintenance, DevOps, multiple inflow sources Pick: KMP path (KSD, KSI) or Team Kanban Practitioner Why: Flow, WIP limits, cycle time, continuous delivery Avoid if: Your org demands strict sprint commitments and story point targets SAFe When: 3+ teams, shared dependencies, portfolio governance Pick: SSM or SASM for team level, SA for leaders Why: Roles at scale, PI Planning, alignment across trains Avoid if: You have one or two teams and no real scaling pain AGILE FOUNDATIONS When: You want breadth across Scrum, Kanban, XP, Lean Pick: ICP (ICAgile) or PMI-ACP Why: Principles, patterns, broad mindset Avoid if: You need immediate, role-specific tactics this quarter FAST DECISION RULES One team, product build, need cadence → Scrum Many interrupts, SLAs, BAU, support → Kanban Multiple teams, shared roadmap, governance → SAFe Exploring or pivoting careers → Agile foundations first ROLE-BASED SHORTLIST Scrum Master new to role → PSM I or CSM, then KMP basics Product Owner → Scrum plus product discovery add-ons DevOps/Platform → Kanban track first, then Scrum add-on if needed SM or APM with 4+ teams → SAFe team-level cert, then LPM concepts Program/Portfolio leader → SAFe SA or LPM after a foundations cert COMMON MISTAKES Doing SAFe with a single team Using Scrum for pure ops work Chasing badges without applying practices Skipping metrics: lead time, cycle time, flow efficiency, escape rate APPLY IT IN 30 DAYS Week 1: Map your work type and demand pattern Week 2: Pick the track using the decision rules above Week 3: Pilot 2-3 practices (WIP limits or Sprint Goal or PI prep) Week 4: Track one metric and one outcome; share results OUTCOME YOU WANT Team flow improves Predictability increases Less status noise, more delivered value Cert supports your context, not the other way around NEXT Comment your role + team size + work type. I’ll suggest a custom path. Like ,Share & Follow... 𝑻𝒂𝒌𝒆 𝒕𝒉𝒆 𝑨 𝒕𝒐 𝒁 𝑺𝒄𝒓𝒖𝒎 & 𝑨𝑰 𝒕𝒐𝒐𝒍𝒌𝒊𝒕 𝒉𝒆𝒓𝒆 -  https://lnkd.in/gUFsSFvR

29

3 Comments

I keep hearing teams say they don't practice BDD because they can't figure out the automation part. That's backwards. BDD isn't about automation. It's about clarity. The Given/When/Then format is a thinking tool that surfaces assumptions, reveals edge cases, and creates shared understanding—before you write a single test. The conversation comes first. The automation decisions come later, strategically placed where they're most valuable and cheapest to maintain. What if we stopped letting concerns about automation block the conversations that create clarity? https://lnkd.in/giYPC6pV #BDD #SoftwareDevelopment #Testing #TeamCommunication

4

4 Comments