LinearB

With the latest round of G2 Grid Reports, LinearB is proud to have been named a leader in the Software Development Analytics Tools Category for the 9th time! ?? Across the Software Development Analytics Tools, DevOps, and Value Stream Management categories, user feedback has helped us receive awards like: – Easiest to do business with – Best support (shoutout to our amazing support team Betsy Rogers and Val Cabral)? – Users most likely to recommend? – Fastest Implementation? – Easiest setup? ? more! Thank you to all of our users who have left us reviews, we love hearing your feedback: ?? “LinearB makes the engineering processes and flows visible by exposing a large number of engineering metrics. It helps me as the VP of R&D have educated discussions with my direct reports and with my CEO. I can identify bottlenecks quickly, measure the team efficiency and developer experience, and improve based on data.” - G2 user If you’re a user who hasn’t left a review yet, we would love to hear from you. Your feedback is our roadmap. Not a user yet? You can try out our Software Engineering Intelligence Platform for free and start your data-driven journey with our DORA metrics dashboard right out of the box. No limitations on contributors, repos, or team size – and no credit card required. #Metrics #Analytics #SoftwareEngineeringIntelligence?

No developer wants to be on a team constantly pressured to deliver over capacity, and no manager wants to explain why their team only delivered 60% of what they promised ? There are two primary metrics to measure your engineering organization’s predictability: planning accuracy and capacity accuracy. Planning accuracy measures the ratio of planned work vs. what was delivered, and it tells you how well your teams prioritize and execute against planned work. Capacity accuracy is the total completed work divided by planned work and tells you if your team is taking on an appropriate amount of work that they can reasonably accomplish. ?????? ???????????? ?????? ???? ???????? ?? ???????????????? ???????????????? ?????????? 85% ?????? ?? ???????????????? ???????????????? ?????????????? 85%-115%. Predictability comes down to tying individual activity to the overall roadmap. You should know at a glance what contributes to your ability to deliver software predictably, enabling you to take action in real-time. Learn more about predictable software delivery here: https://lnkd.in/gxAaUTYW?

"The Bots are Coming!" and our software delivery pipelines aren't ready. This presentation will discuss research on how development organizations are preparing for GenAI in software delivery, identify where existing delivery pipelines may fail, and review the fundamentals necessary to tackle this significant challenge. We're excited to have Yishai Beeri - LinearB, speaking at the upcoming SREday Amsterdam, join us on November 21 2024! Tickets: https://lnkd.in/eTxk4fSa 10% off with the code AMS10

How can you leverage metrics for more meaningful and actionable team conversations and get more out of recurring syncs–like daily stand-ups, weekly check-ins, and sprint retrospectives? ?????? ??????????????: Use metrics to provide context during one-on-one meetings. For example, discuss specific KPIs such as PR review time. Be sure to look at this metric in terms of conducting and waiting for reviews or PR size to highlight areas of strength and opportunities for improvement. ???????????????? ??????????????????????: Leverage data to identify and address bottlenecks in the development process and better inform ceremonies like sprint planning or retrospectives. – If review times are consistently high, discuss strategies to streamline the code review process with automation. – If cycle time is increasing or the project seems to be going off the rails, discuss potential causes, examine risk indicators, and collaboratively develop solutions. ???????? ??????????????????: Ensure individual goals are aligned with team and organizational objectives. Use data to show how individual contributions impact broader goals, fostering a sense of ownership and accountability ?????????????????? ??????????????: Use data to recognize and celebrate team achievements. Highlight metrics that show improvement and acknowledge contributions that led to success. Learn more about how you can leverage metrics and improve team ceremonies in The Engineering Leader’s Guide to Accelerating Developer Productivity: https://lnkd.in/dv5crdih #Data #Metrics #Retrospectives?

Context switching is a productivity killer that creates a poor developer experience and distracts your team from focusing on high-value work. Dependency management tools are creating an influx of bot-generated PRs, which our recent research found accounts for 13.3% of all code submissions today. Not only does this distract your team, but it also poses a security threat. ? If you treat these PRs like housekeeping and only merge them once a week or once a sprint, you may be exposed to potential vulnerabilities without having visibility as they make their way into your pipeline. With AI-generated code on the rise, you can imagine bot-generated PRs could easily escalate to upwards of 50% of all code submissions in the coming years. How can you get ahead of this problem? Teams that implement PR automation can auto-approve 84% of these bot-generated PRs (patch and minor changes) and auto-merge almost half of them, decreasing their overall workload by 6%. Learn more in our recent research report ???????????????? ??????-?????????????????? ?????? & ???????????????? ???????? ???????????????? ???? 6% here: https://lnkd.in/geedeb89 #Automation #ContextSwitching #Productivity?

How do you measure software engineering success? I have the privilege of asking this question to engineering leaders almost daily. The top responses? – Meeting deadlines – Delivering business value – Building products that customers love But when I dig deeper and ask how they track these outcomes, the answers are often: – Guesswork / manual analysis – Team sentiment – Subjective feedback We miss the real picture when we don’t use data-driven, quantitative metrics to measure success. It’s easy to feel like things are going well when we’re not measuring what matters. Fortunately, at LinearB, I also have the privilege of helping these same engineering leaders wrangle their improvement initiatives and adopt the mindset and practices of elite engineering organizations. Ready to start your journey? Read this: https://lnkd.in/gwhDBMcv

A few weeks back,?LinearB?had our?#gtm?offsite in Boston. We shared so much valuable time f2f, and it made our amazing team even stronger ?? We also had customer talks, and we were fortunate to have the one and only Adi Rosha ?? to share her experience as the ultimate champion for eToro <> LinearB Partnership. I had the pleasure of working with Adi for the past two years. Adi is a remarkable person who is sharp, intelligent, data-driven, and process-oriented. Adi helped the eToro Eng Team implement LinearB, a Software Engineering Intelligence Platform and made a huge impact with her outstanding change management skills. I would be extremely lucky to work with more people like her. Thanks Adi for the show! It was highly appreciated!

Too often, engineering leaders think they won’t be able to tie Developer Experience (DevEx) directly to the bottom line. It’s easy to justify new features, but drawing direct lines between bottom-line value and infrastructure investments is far more complex. To help understand the impact of engineering infrastructure investments, we publish a yearly set of Engineering Benchmarks that share insights from more than 2,000 engineering teams around the world, covering more than 3.6 million PRs. Here are three key DevEx indicators from these benchmarks that quantify the bottom-line impact of DevEx investments: ???????????????????? ?????????????????? ???????????? ???? ?????????????????? ???????????????????? If you overinvest in new features and underinvest in the critical infrastructure needed to keep the lights on, you’ll find yourself responding more and more to unexpected situations. Excess time spent on bugs, tech debt, and unplanned work indicates poor DevEx, which directly impacts productivity. Our Benchmarks report found that the average organization invests 15% of its time into DevEx. This category includes improvements to developer productivity and overall work experience, such as enhancing tooling and platforms, adding test automation, restructuring code to reduce technical debt, and reducing backlog. ?????????????? ?????????? ?????????????????????? ?????????????????????? Most of a typical developer's day occurs inside the software cycle: creating, reviewing, merging, and deploying code. Inefficiencies impact developers individually, but the bottlenecks that make them often exist at the team level. Problems such as high coding time, high pickup time, high review time, and high deploy time can indicate issues like poor scoping, communication gaps, uncertainty in the merge process, and poor post-merge experience. These issues severely impact DevEx, and team leads and managers need visibility into cycle time blockers to collaborate with other teams to resolve them. ?????????? ???????????????????? ?????? ?????????????????? Healthy engineering cultures empower developers to improve their environment proactively. DevEx initiatives are more likely to succeed with bottom-up buy-in, and individual empowerment is how you get this buy-in. Optimizing the merge process, nudging developers when their teammates need help, or implementing self-service catalogs for internal dev tooling gives developers the tools to make their lives easier. The key to a successful DevEx initiative is to make the path of least resistance the most likely to result in success. Learn more in our Director of DevEx Ben Lloyd Pearson's blog here: https://lnkd.in/gWfG4Fb5 #DevEx #DeveloperExperience?

Did you miss our workshop on managing bot-generated PRs? Dig into new research that exposes the effects of bots on your team’s developer experience and productivity and learn how you can get ahead of the problem to reduce your team’s workload by 6% ?? Access the workshop with our Director of Developer Experience Ben Lloyd Pearson and CTO Yishai Beeri here: https://lnkd.in/gPNafTfR #Automation #Bots #SDLC

We’re excited to be platinum sponsors for this year’s DevOps Days Tel Aviv coming up on October 30th and 31st! ?? Dev Interrupted Hebrew is also a media sponsor for the event, and ICYMI – we released episodes with keynote speakers from the conference: ??? A Peep into DevOps Dysfunctions, Liat Ashkenazi, SVP Engineering and GM Israel, OwnBackup https://lnkd.in/gStH4GTM ??? No Ops?! Your Software Doesn't Exist - Andrew Clay Shafer and John Willis https://lnkd.in/gDknaWt2 If you’re in the Tel Aviv area, you can register in the comments below, and we look forward to seeing you there! #DevOps #DevOpsDays #DevOpsDaysTLV