温馨提示：本站仅提供公开网络链接索引服务，不存储、不篡改任何第三方内容，所有内容版权归原作者所有
AI智能索引来源：http://www.linkedin.com/in/weisbart
点击访问原文链接

Adam Weisbart - Weisbart Consulting | 领英

进入原网站 导航首页
领英登录马上加入忘记密码立即加入《用户协议》《隐私政策》《Cookie 政策》忘记密码立即加入《用户协议》《隐私政策》《Cookie 政策》忘记密码立即加入《用户协议》《隐私政策》《Cookie 政策》忘记密码立即加入《用户协议》《隐私政策》《Cookie 政策》加入领英，查看档案忘记密码立即加入《用户协议》《隐私政策》《Cookie 政策》举报此会员档案忘记密码《用户协议》《隐私政策》《Cookie 政策》立即加入3 reasons to limit your retrospectives…Why Mr. Rogers was the best Scrum…Anti-agile: Trick your partner into…The Godmother that puts Agilists to…See all articles忘记密码立即加入《用户协议》《隐私政策》《Cookie 政策》📢 The Remote Facilitator Practitioner…Adam WeisbartYep, you heard right – PayPal monitors…Adam WeisbartIn April, my tenure with Bear Group…Adam Weisbart立即加入，查看全部动态《用户协议》《隐私政策》《Cookie 政策》忘记密码《用户协议》《隐私政策》《Cookie 政策》立即加入Tom Angelopoulos “With Adam's training, I breezed through the CSM exam. Getting through the CSM definitely helped me land my position, where I will actually get to apply Scrum (with executive sponsorship!).”加入领英，即可查看As my time at AWS comes to an end…Adam WeisbartI met Bob over 16 years ago when I was…Adam Weisbarthttps://gofund.me/b8ead694 Bob Sarni…Adam WeisbartBob Sarni has been an immense…Adam WeisbartMy friend, mentor, and a pillar of the…Adam WeisbartDefinitely hope this message spreads…Adam WeisbartAgile Virtual Summit speaker, and all…Adam WeisbartPeter Trudelle查看档案Maurizio Gianola查看档案Muzzammil Khan查看档案David Chappell查看档案Nick Temple查看档案Konda Ankireddypalle查看档案Jeff Yoak查看档案Manish Champsee查看档案Celia House查看档案Sheridan Chambers查看档案Liz White查看档案Manpreet Bhatia查看档案S.C. Lee查看档案John Bennett查看档案Kerry Macca查看档案James Martinez查看档案Peter Hoskins查看档案Stephen Ryan查看档案Richard Dym查看档案Chris Cardinal查看档案Homer Gaines, CPACC Coforma • 3440 位关注者An Accessibility Conformance Report (ACR), more commonly referred to as a VPAT® (Voluntary Product Accessibility Template), is a report that’s typically completed by an Accessibility Professional. It’s an important document to have, and companies should understand what they are and what they are not. https://lnkd.in/e7x5nhgA #Accessibility #A11y #Process 39 1 条评论Chakravarthy Tenneti Seasoned technical writer and… • 3327 位关注者SDK documentation is not supplementary material... it is a vital component of the SDK itself. It lets developers harness the SDK's potential by serving as a highly sophisticated technical bridge. However, the tone must be instructional, and the approach must be simple. Here is a quick explainer video on the need for SDK documentation and its essential components. 19Gleb Bahmutov Mercari US • 8805 位关注者New Cypress blog post showing how to mock the locked down "location.href = ..." assignments in your E2E tests: "Mock The Location Href Property" at https://lnkd.in/eRjSYNfn 11Danny (Danko) Kovatch Ajimeh • 2万 位关注者Here’s the translation and twist: “Have we all become QA engineers in the age of AI? Once upon a time, developers were deep in code. Today, with AI tools cutting through the code for us, our challenge evolves. We’re no longer just writing, we’re examining architecture, ensuring quality, and making sure the machine does the right thing. We’re leveling up, from coders to vibe-coding QA architects of the future. And in this new world, Scrum helps us navigate the shift are you ready to be proactive by creating the new reality or are you just going to wait for it ?”🤪 #FlowVate , scrum on steroids … 5Heemeng Foo Stealth • 4742 位关注者It took a while but I really wanted to document the build (and also do a little bit of clean up of the code/repo). This is the accompanying article to the last post (the one with the video). In it I share some of the key aspects of building Cuttlefish and how the preso/video was produced - from #contextengineering and #vibetroubleshooting the code to #testplanning and how the automated tests were instrumental in making sure existing code was all good while adding new key features. #AI #AIMakerspace #Jira #softwareengineering #softwaretesting https://lnkd.in/gBEk2B4v 10 1 条评论Brad Kinnard Aftermath Technologies • 233 位关注者I created Conversation Stress Tester to look at how chatbots handle pressure. What sets it apart is that it does not stop at injecting stress into a conversation. It also validates the data, attaches reference responses, and produces HuggingFace - ready datasets with metrics on coverage, diversity, and quality. This system creates end-to-end datasets that can be both tested against and trained on. Still in early testing but This system will be available open source on GitHub next week. #Chatbots #ConversationalAI #MachineLearning #NLP #AIEngineering #AdversarialTesting #OpenSourceAI #HuggingFace 1 1 条评论Automation Tech Guru Cognizant • 817 位关注者Automation rarely breaks suddenly. It quietly erodes trust. Coverage improves. Reports look healthy. Release anxiety increases. This usually isn’t about frameworks or AI tools. It’s about what automation isn’t telling you. I’m seeing QA leads realize this only after a production escape. If release confidence is on your shoulders, a short private check often reveals what dashboards hide. 3 1 条评论Shannon Allan Shannon Allan Home Concierge… • 1143 位关注者"𝗝𝘂𝘀𝘁 𝗱𝗼 𝗶𝘁" 𝗶𝘀𝗻’𝘁 𝗷𝘂𝘀𝘁 𝗮 𝘀𝗹𝗼𝗴𝗮𝗻. It’s how I learned to influence without authority As a mid-level QA woman in tech. Waiting for permission wasn’t going to cut it. A colleague who was great at this stuff shared the basics: 🔸 Understand what’s really bugging them 🔸 Bring solutions that help the business 🔸 Show up prepared (always) 🔸 Do what you say you’ll do 🔸 Pick your moments to speak up But here’s what really moved the needle: 𝗜 𝘀𝘁𝗮𝗿𝘁𝗲𝗱 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗿𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽𝘀 𝗯𝗲𝗳𝗼𝗿𝗲 𝗜 𝗻𝗲𝗲𝗱𝗲𝗱 𝘁𝗵𝗲𝗺. Coffee chats with devs. Checking in on product managers’ side projects. Remembering what stressed people out. So when crunch time hit, I wasn’t just “that QA person” I was someone they trusted. And it worked: ✅ I heard about issues early ✅ Devs shifted priorities when I asked ✅ My meetings actually worked because I’d already invested in listening 𝗔𝗻𝗱 𝗵𝗲𝗿𝗲'𝘀 𝘄𝗵𝗲𝗻 𝗶𝘁 𝗮𝗹𝗹 𝗰𝗹𝗶𝗰𝗸𝗲𝗱... A critical customer project. I had to convince leadership to shorten a risky freeze window. They said yes, not because of my job title Because of the trust I'd earned. And because I was clear about the risk and the business impact. 𝗜𝗻𝗳𝗹𝘂𝗲𝗻𝗰𝗲 𝗶𝘀𝗻’𝘁 𝗮𝗯𝗼𝘂𝘁 𝘆𝗼𝘂𝗿 𝘁𝗶𝘁𝗹𝗲. 𝗜𝘁’𝘀 𝗮𝗯𝗼𝘂𝘁 𝘁𝗵𝗲 𝘁𝗿𝘂𝘀𝘁 𝘆𝗼𝘂’𝘃𝗲 𝗯𝘂𝗶𝗹𝘁. People who influence without authority: 1️⃣ 𝗕𝘂𝗶𝗹𝗱 𝗿𝗲𝗮𝗹 𝗿𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽𝘀 – They invest in people, not just projects 2️⃣ 𝗟𝗶𝘀𝘁𝗲𝗻 𝗳𝗶𝗿𝘀𝘁 – They understand what matters to others 3️⃣ 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗲 𝗰𝗹𝗲𝗮𝗿𝗹𝘆 – No jargon, just clarity 4️⃣ 𝗣𝗶𝗰𝗸 𝘁𝗵𝗲𝗶𝗿 𝗯𝗮𝘁𝘁𝗹𝗲𝘀 – They know when to push and when to pause They’re not tricks They’re how real leaders show up. Keep showing up this way, and people will start listening. 𝗪𝗮𝗻𝘁 𝘁𝗼 𝗹𝗲𝗮𝗱 𝗯𝗲𝘆𝗼𝗻𝗱 𝘆𝗼𝘂𝗿 𝗷𝗼𝗯 𝗱𝗲𝘀𝗰𝗿𝗶𝗽𝘁𝗶𝗼𝗻? Start with coffee chats - not PowerPoints. Drop a 👍 if you're trying it. Go book that chat this week. 22 23 条评论Ben F. Loop Software & Testing… • 2万 位关注者A little more detail on my AI in QA workshops: Please reshare to help get out the word. These are free and I want to keep doing them if there is interest. The goal is largely meant to inspire and encourage learning. They will point you in the right direction. 1. An intro to Cursor, Playwright & LLMs This hour-long session will focus on getting you comfortable with Cursor and the tips and tricks that are key for QA engineers using it. I’ll walk you through model selection, how to set context, how to use rules, and more. This is great for anyone who is fairly new to Cursor and wants to start using it. Calendly: https://lnkd.in/gJthqa7b 2. Using Cursor to build your POM This session will leverage Cursor to build out a basic page object model. I’ll show you how to do this using both the DOM and code. Additionally, we’ll cover adding test IDs to the codebase and look at strategies for handling test data. Calendly: https://lnkd.in/gp9M6Gn9 3. Directors only: How can Cursor help your team? These are ad-hoc sessions any manager, director, CTO, etc., can book. I’ve already done several and really enjoy them. They tend to be conversations about your current approach, with me demoing whether or not Cursor can be helpful. They are often fascinating discussions about QA and usually offer a nugget or two that people take away. Calendly: https://lnkd.in/guRf6Cu2 #qa #ai #cursor #learning 65 10 条评论Tom Mango North • 460 位关注者I’ve been writing a series of posts on the design principles behind Looping, a product I’m building to help teams run and evolve software over time. These principles shape the architecture underneath and have helped me prioritize clarity, composability, and long-term maintainability from the start. The latest post in the series is about Composable Services. In Looping, every service follows the same interface: it takes a hash of input and returns either Success() or Failure(). That consistency makes services easy to test, reuse, and chain together without resorting to sprawling conditionals or unpredictable side effects. The post walks through the structure, shows real examples, and touches on how it tracks source chains for observability and event logging. https://lnkd.in/ePkn-pF6 #ruby #rails #softwarearchitecture #buildinpublic 7 2 条评论Matt Weagle Machinify • 1180 位关注者I'm nearly done listening to L. David Marquet's Leadership Is Language and I can't recommend it highly enough it for anyone moving into an EM role. There are many similarities with Todd Conklin's 5 Principles of Human Performance and the values that were expressed in the Agile Manifesto. What sets Leadership as Language apart is that he provides both the framing (eg: Collaborate, not Coerce) and specific, concrete linguistic expressions to manifest those outcomes. For instance, there are many studies that speak to the importance of psychological safety, but very few that provide specific guidance on exactly how to foster that outcome. This book is overflowing with specific linguistic recommendations. Rather than phrasing like X, phrase instead as Y. This actionable guidance is sadly missing in many leadership books. It's a great book and definitely demands an even deeper second reading. (Links in the comment) 11 7 条评论Alex Laats www.PlanofRecord.org • 6613 位关注者In today’s Substack post from the Plan of Record series, I walk through the operational frameworks I’ve relied on to build high-performance product development teams and why they’re essential for diagnosing and fixing what’s broken. I also explain why we had to create the PoR Prioritization Framework to address a critical gap no other model could fill. Here’s the link: https://lnkd.in/ek9J_cqq #SaaS #ProductManagement #EngineeringLeadership #R&D #Prioritization #Execution #CPO #CTO #CPTO 14Patrick Lef QA.tech • 4004 位关注者Speed is seductive. Every product team feels the pressure to launch faster, iterate faster, scale faster. But speed alone isn’t a strategy. If fast features outpace slow foundations, the result isn’t growth — it’s rework, customer pain, and eroded trust. The lesson: sustainable advantage comes from aligning fast and slow. - Fast cycles capture opportunity. - Slow, deliberate QA provides resilience. - Together, they form the only kind of velocity that compounds. Autonomous QA is about embedding that resilience directly into the pipeline. Not slowing things down, but giving speed a structure strong enough to endure. Because in product, the goal isn’t to move fastest. It’s to move farthest. Speed without stability doesn’t scale. In our latest article, we break down why fast and slow must work together in QA: “Fast Features, Slow Foundations”. Full read: https://lnkd.in/dQkcKHGu 1Taras Mankovski Frontside Software • 5112 位关注者> Developers experienced in agile engineering practices like test-driven development tend to be among the most successful at building great software with coding agents, often citing creative techniques enabling agents to verify the correctness of their work I had this experience recently. I wrote a few features of a new testing harness using AI and I realized that working with AI was the workflow that I always wanted. It's almost an idealized version of what Charles Lowell and I described as transparent development. The result was a very well organized, document and tested feature where most of the grunt work was done by AI. The process of ensuring that it had all of the needed context was a forcing function that ensured that it had correct constriants to stay on track and verify it's work. I gotta admin - it was a bit scary and it left me shook. In the past, the currency of knowledge work was information and value in engeering organizations was based on technical skills. AI commodities both of these to an extent that I find difficult to process. It's both exciting and extremely unsettling. 5Bron Davies ProPlans • 1281 位关注者My book talks deeply about this issue - the dichotomy of developer performance vs. culture and how the latter impacts the business more. https://lnkd.in/g-YFyERJ 4Pravin Shinde Visa • 2179 位关注者"Isn't that the role of an architect?" A senior leader asked me this when I was talking about platform product management. It's a fair question and I have heard it before. Platform systems can be incredibly technical, but they need someone to champion the user perspective — to bridge what's technically possible with what users actually need. In some aspects, it's harder to grasp compared to user-facing products. IMO, Here's what makes Platform PMs unique: * Deeply technical system and users * Tough to imagine the product design * Guardrails as core construct * Adoption through alignment * Impact beyond revenue There's an interesting story about how this played out during a critical system failure, and how Platform PM plays a critical role in stability and scale of systems. Give it a read, and let me know your thoughts. https://lnkd.in/gAhRpD-C #Platforms #PlatformProductManagement #DataPlatform #ProductDesign 58 6 条评论Steev Kundukulangara Teradata • 4671 位关注者This is part 1 of my new series: Docs as Systems, not Files. Here’s the real business problem I solved and why writers need to think like system designers. https://lnkd.in/g9mhTi8x 26 4 条评论Paul Littlebury jaffamonkey • 5102 位关注者A golden oldie google talk, "Test is Dead" from 2011, though it is actually about moving away from old ways of testing. Unfortunately, some took the headline to heart. This was the part of the talk that caught my attention at the time. "... the key is if you really want to test something -- and this is the key of the new testamentality, you have to test the idea. I'm not saying that you don't want to eventually build it right. You have to make sure you're building the right thing." https://lnkd.in/e8PdykVF 5Dennis Deacon Vispero® • 8060 位关注者Tatiana Fokina delves into the nuances of WCAG 2.2 criteria, emphasizing the importance of ensuring that focused elements remain visible and unobstructed. She highlights common design pitfalls—such as dropdown menus, sticky headers, and modal dialogs, that can hinder keyboard navigation and user experience. Fokina provides practical examples and testing strategies to help developers and designers create more inclusive web interfaces. Her approach underscores the critical role of visibility in maintaining accessibility standards. https://buff.ly/Bs5pxLK #Accessibility #WCAG #InclusiveDesign #WebDevelopment #KeyboardNavigation #WebDev #DigitalInclusion #UXDesign #A11y #FocusVisibility #DigitalAccessibility #WCAG 4Jeff Stanier, MBA AFTIA Solutions • 1715 位关注者The AFTIA team is proud to share the PDF Accessibility Remediation (PAR) solution to help organizations meet their ADA title II deadlines for accessibility. 23 1 条评论加入领英，查看完整档案关于无障碍模式用户协议隐私政策Cookie 政策版权政策品牌政策访客设置社区准则《用户协议》《隐私政策》《Cookie 政策》忘记密码立即加入《用户协议》《隐私政策》《Cookie 政策》

智能索引记录