TestGuild’s Post

True agility means being able to scale your team, along with the capacity and throughput of IT change within your pipeline to meet your business demands. These four key items help enable agility. 1. Service teams provide the agility in resourcing flexing up and down; 2. virtual workers provide the scale and capacity to execute the throughput of work; 3. Good test design specification ensure suitable coverage and risk mitigation; 4. Strong estimation models accurately provide effort and planning date for each sprint cycle. For more information, visit bit.ly/3jtsotd #pinnacleqm #IT #informationtechnology #itconsulting #cloudtechnology #cloudtech #innovation #manualtesting #qatesting #tester #testautomation #tech

What are the hidden quality risks to “Shift Left” and the impact on an organization. Without proper analysis and a solid mitigation plan, these risks can easily go unnoticed. In my latest article, I explore the complexities of navigating the Forming and Storming stages of the Shift Left approach. I share tips on analyzing the impact on your team and managing quality risks. Take a look to discover practical strategies for maintaining high standards amidst change! I'd love to hear your thoughts. #ShiftLeft #QualityAssurance #SoftwareEngineering #ContinuousImprovement #OrganizationalChange #RiskManagement #DevOps #TestAutomation #SoftwareTesting #TechLeadership #QualityManagement #SoftwareDevelopment #EngineeringExcellence #ProcessImprovement Read the full article here: https://lnkd.in/et7RHhZz

True agility means being able to scale your team, along with the capacity and throughput of IT change within your pipeline to meet your business demands. These four key items help enable agility. 1. Service teams provide the agility in resourcing flexing up and down; 2. virtual workers provide the scale and capacity to execute the throughput of work; 3. Good test design specification ensure suitable coverage and risk mitigation; 4. Strong estimation models accurately provide effort and planning date for each sprint cycle. For more information, visit bit.ly/3jtsotd #pinnacleqm #IT #informationtechnology #itconsulting #cloudtechnology #cloudtech #innovation #manualtesting #qatesting #tester #testautomation #tech

True agility means being able to scale your team, along with the capacity and throughput of IT change within your pipeline to meet your business demands. These four key items help enable agility. 1. Service teams provide the agility in resourcing flexing up and down; 2. Virtual workers provide the scale and capacity to execute the throughput of work; 3. Good test design specification ensure suitable coverage and risk mitigation; 4. Strong estimation models accurately provide effort and planning date for each sprint cycle. For more information, visit bit.ly/3jtsotd #pinnacleqm #IT #informationtechnology #itconsulting #cloudtechnology #cloudtech #innovation #manualtesting #qatesting #tester #testautomation #tech

Angela Kelly and I had the opportunity to speak with James Governor of RedMonk about the growing importance of #Observability, earlier and earlier in the software development lifecycle. We discuss the factors shaping this change, as companies strive to ship software faster, safely, with ever tighter feedback loops. #platformengineering #shiftleft #shiftdown Dynatrace

💅𝗛𝗮𝗻𝗱𝗹𝗶𝗻𝗴 𝗲𝗿𝗿𝗼𝗿𝘀 𝗹𝗶𝗸𝗲 𝗮 𝗽𝗿𝗼 𝗼𝗿 𝗻𝗮𝗵? 𝗟𝗲𝘁’𝘀 𝘁𝗮𝗹𝗸 𝗗𝗲𝗮𝗱 𝗟𝗲𝘁𝘁𝗲𝗿 𝗤𝘂𝗲𝘂𝗲𝘀 💀 In the "𝗙𝗶𝗿𝗲 𝗮𝗻𝗱 𝗙𝗼𝗿𝗴𝗲𝘁" pattern, the consumer is responsible for processing the message, but what happens when something goes wrong? Let's continue our discussion on asynchronous messaging with error handling. 🔎 𝗪𝗵𝗮𝘁 𝗔𝗿𝗲 𝗗𝗲𝗮𝗱 𝗟𝗲𝘁𝘁𝗲𝗿𝘀? When a message can't be processed after multiple retries, it moves to a Dead Letter Queue, allowing you to isolate and investigate the failure without disrupting the rest of the system. Here's a breakdown of the key strategies that will help keep your systems resilient and reliable 🚀 ✅ 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲𝗱 𝗥𝗲𝘁𝗿𝗶𝗲𝘀 Ensure your system is idempotent—so retrying a message won’t create duplicates or errors. Configure retries up to 10 times before moving it to the DLQ for further analysis. ✅ 𝗖𝗹𝗶𝗲𝗻𝘁 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 Notifying clients of failures through WebSockets can help reduce dead letters. Though it breaks from traditional async, it's useful when immediate feedback is needed. ✅ 𝗣𝗿𝗼𝗮𝗰𝘁𝗶𝘃𝗲 𝗔𝗹𝗲𝗿𝘁𝗶𝗻𝗴 Dead letters signal issues. Use tools like PagerDuty, Opsgenie, or Splunk to monitor queues and alert you of errors, preventing small problems from escalating. ✅ 𝗛𝗮𝗻𝗱𝗹𝗶𝗻𝗴 𝗗𝗲𝗮𝗱 𝗟𝗲𝘁𝘁𝗲𝗿𝘀 𝗶𝗻 𝗧𝗼𝗽𝗶𝗰𝘀 For systems using topics, employ Forwarding or Failover Queues to manage dead letters efficiently and ensure no message is left unhandled. Asynchronous systems are fast but tricky to manage. With proper tools like retries, DLQ management, and proactive alerts, you can build robust, reliable systems. Want to know more? Check out the 𝗳𝘂𝗹𝗹 𝗮𝗿𝘁𝗶𝗰𝗹𝗲 𝗼𝗻 𝗺𝘆 𝗠𝗲𝗱𝗶𝘂𝗺 𝗽𝗮𝗴𝗲 to dive deeper into Dead Letter Queues and learn how to build resilient systems with best practices in error handling! Follow for more 😊 #TechInsights #AsynchronousMessaging #DLQ #Microservices #ErrorHandling #SoftwareArchitecture #CloudEngineering #DevOps

Continuing on trends that I've noticed working with SRE & Platform teams: Trend #2: Observability is gotten easier ➜ alerting has become noisier. With increasing ease of instrumentation and reducing cost of telemetry data storage, teams today are storing more data than ever. Often teams are orchestrating alerts on metrics through codified scripts -- this is causing a bloat of alerts and make it harder for teams to differentiate noise from a useful alert. Some measures that I've seen teams do to manage this growing noise: 1. Setup analytics on alerts to identify noisy alerts and discard them 2. Make on-call engineer responsible to turn off / report on every noisy alert at the end of their rotation 3. Bi-weekly engineering meetings to discuss the alerts from last 2 weeks -- mark actionability against each of them and create Action Items to either take action against the root cause of the alert (if it was a concerning alert) or remove/change threshold (if it was not useful) Is there any other practice that your team followed to improve the quality of alerts? Would love to hear. P.S.: I built a bot that instantly provides you insights on noisy alerts in your Slack channel: https://lnkd.in/e6T_yG78 #alerting #observability

💡By 2026, Gartner predicts 80% of large software organizations will have dedicated platform engineering teams. Organizations often struggle with long release cycles and complex compliance needs. Enter platform engineering—a game-changing approach that allows dev teams to focus on what they do best. Ready to optimize your development process? Dive into the benefits of platform engineering and learn how to set up your team for success: https://bit.ly/4dIDdCz #softwaredevelopment #platformengineering