<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Emre Dundar on Medium]]></title>
        <description><![CDATA[Stories by Emre Dundar on Medium]]></description>
        <link>https://medium.com/@emredundar?source=rss-cf1aed6d40d9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*U4ErggdCItwWDJ1lIiRDuA.png</url>
            <title>Stories by Emre Dundar on Medium</title>
            <link>https://medium.com/@emredundar?source=rss-cf1aed6d40d9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 17:42:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@emredundar/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Best Engineering Metrics Tools for Software Teams in 2026]]></title>
            <link>https://emredundar.medium.com/best-engineering-metrics-tools-for-software-teams-in-2026-4c07b83ed1d0?source=rss-cf1aed6d40d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c07b83ed1d0</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Emre Dundar]]></dc:creator>
            <pubDate>Fri, 04 Sep 2026 06:43:23 GMT</pubDate>
            <atom:updated>2026-09-04T06:43:23.130Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Compare Oobeya, Swarmia, LinearB, DX, Jellyfish, and Apache DevLake across engineering metrics, DORA, developer experience, AI metrics, SDLC coverage, and governance needs.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/819/0*oFfdhiiY7rK-pL-A.png" /></figure><p>The best engineering metrics tool is not the one with the longest feature list. It is the one that helps your team make better engineering decisions without turning software delivery into a surveillance program.</p><p>For many software teams in 2026, the strongest candidates to evaluate include <strong>Oobeya</strong>, <strong>Swarmia</strong>, <strong>LinearB</strong>, <strong>DX</strong>, <strong>Jellyfish</strong>, and <strong>Apache DevLake</strong>. They overlap in the broad engineering metrics category, but they are not interchangeable.</p><p><strong>Quick answer:</strong> choose based on the problem you are trying to solve.</p><ul><li>Choose <strong>Oobeya</strong> when you need broad <a href="https://oobeya.io/engineering-metrics">engineering metrics</a> and SDLC intelligence across delivery, quality, workflow, testing, security, developer productivity, AI-assisted development, and governance.</li><li>Choose <strong>Swarmia</strong> when your main priority is team-focused engineering effectiveness, working agreements, DORA, SPACE, developer experience surveys, and productivity improvement loops.</li><li>Choose <strong>LinearB</strong> when your main priority is development workflow automation, pull request orchestration, engineering goals, and developer productivity reporting.</li><li>Choose <strong>DX</strong> when your main priority is developer experience measurement, research-backed productivity frameworks, surveys, benchmarks, and AI measurement.</li><li>Choose <strong>Jellyfish</strong> when your main priority is engineering management, investment visibility, allocation, business alignment, and AI-integrated engineering reporting.</li><li>Choose <strong>Apache DevLake</strong> when you want an open-source engineering data platform that your team can install, customize, and extend.</li></ul><p>No tool is universally best. A platform that is excellent for PR automation may not be the best system of record for quality and governance. A platform that is flexible and open source may require more internal ownership than a managed product. A platform with strong DevEx surveys may not be the right answer if your immediate need is deployment data, security analytics, or on-premises control.</p><p>Use this guide as a buyer framework, then validate each product against your real toolchain, <a href="https://oobeya.io/developer-productivity">developer productivity</a> goals, and <a href="https://oobeya.io/ai-impact">AI impact</a> measurement needs.</p><h3>How to Evaluate Engineering Metrics Tools</h3><p>Before comparing vendors, decide what your engineering metrics program must answer. The most useful platforms usually help teams connect multiple types of evidence instead of optimizing one number in isolation.</p><h4>1. Data Coverage</h4><p>Look for coverage across the tools where work actually happens: issue trackers, source control, pull requests, CI/CD, deployment tools, test systems, code quality tools, security scanners, observability platforms, incident systems, and AI coding assistants.</p><p>The key question is not “does it integrate with GitHub or Jira?” It is “can it connect the right events into a trustworthy model of how work moves through our SDLC?”</p><h4>2. DORA Metrics</h4><p><a href="https://oobeya.io/dora-metrics-four-key">DORA metrics</a> remain a useful baseline for delivery performance, especially deployment frequency, lead time for changes, change failure rate, and recovery time. But DORA metrics are only as trustworthy as their definitions.</p><p>When evaluating tools, ask:</p><ul><li>How are deployments detected?</li><li>How are incidents or failures defined?</li><li>Can release, CI/CD, and issue data be connected?</li><li>Can the platform explain why a DORA metric changed?</li><li>Can teams compare trends against <a href="https://oobeya.io/benchmarks">benchmarks</a> without turning benchmarks into a scoreboard?</li></ul><h4>3. Developer Experience</h4><p>Developer experience is not a soft add-on. Friction in local development, review flow, CI wait time, unclear requirements, and tool sprawl can all shape delivery outcomes.</p><p>Some platforms emphasize surveys and qualitative feedback. Others focus more on workflow and system signals. The best choice depends on whether you need sentiment data, operational bottleneck data, or both.</p><h4>4. Delivery Workflow</h4><p>Pull request flow, review time, batch size, cycle time, CI duration, blocked work, and handoffs often reveal bottlenecks faster than executive dashboards do.</p><p>If review automation and PR orchestration are central, evaluate workflow-focused platforms carefully. If the workflow data must be interpreted alongside quality, testing, security, and AI impact, evaluate broader engineering intelligence platforms.</p><h4>5. Quality and Reliability</h4><p>Speed without quality is not productivity. A good engineering metrics platform should help teams see whether faster delivery is increasing escaped defects, rework, vulnerabilities, failed builds, incidents, or customer-facing risk.</p><p>For teams using tools such as SonarQube, Snyk, Veracode, test management systems, observability platforms, or incident tools, quality context should be part of the evaluation.</p><h4>6. Project and Investment Data</h4><p>Engineering leaders often need to know not only how fast teams move, but also where engineering effort goes. This includes roadmap work, maintenance, technical debt, customer support, infrastructure, security, and strategic initiatives.</p><p>If allocation and business alignment are central, compare each platform’s ability to connect engineering work with planning and investment views.</p><h4>7. AI Metrics</h4><p>AI coding assistants changed the buyer checklist. Teams now need to understand adoption, code origin, AI-assisted pull request patterns, review load, quality impact, token cost, and whether AI is improving outcomes rather than simply increasing activity.</p><p>Start with <a href="https://oobeya.io/ai-impact">AI Impact</a>, then ask vendors how they connect AI usage to delivery, quality, rework, developer experience, and business outcomes.</p><h4>8. Deployment, Security, and Governance</h4><p>Some organizations can use a SaaS-only model. Others need private cloud, on-premises deployment, local LLM options, strict data residency, single sign-on, access control, auditability, or vendor governance.</p><p>This is often the deciding factor for banks, insurers, telecoms, government suppliers, and enterprises with strict engineering data policies.</p><h4>9. Usability</h4><p>The tool should make good decisions easier. If every useful answer requires a data analyst, dashboard maintainer, or custom SQL expert, adoption may stall.</p><p>Ask who the product is actually built for: engineering managers, platform teams, executives, developer productivity teams, finance, data teams, or individual development teams.</p><h4>10. Organizational Scale</h4><p>Scale does not only mean company size. A single team with complex compliance needs may require tighter governance than a larger SaaS company. A large organization with autonomous teams may need flexible definitions rather than one global dashboard.</p><p>The better question is: can the platform support your measurement maturity today and your operating model tomorrow?</p><h3><strong>Engineering Metrics Tools Compared</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HlZ6LzSLk6UxvDf06qKNXw.png" /><figcaption>Engineering Metrics Tools comparison table</figcaption></figure><h4>1. <a href="https://oobeya.io/">Oobeya</a></h4><p><strong>Best for:</strong> teams that need broad software engineering intelligence across many SDLC domains.</p><p>Oobeya fits teams that need to connect delivery metrics, workflow signals, quality data, test analytics, security context, developer productivity, <a href="https://oobeya.io/ai-impact">AI impact</a>, and executive reporting in one operating view.</p><p>Its buyer question is usually not “how many PRs did we merge?” but “what is happening across the SDLC, why is it happening, and where should leaders act?”</p><p><strong>Key strengths</strong></p><ul><li>Broad <a href="https://oobeya.io/engineering-metrics">engineering metrics</a> coverage across delivery, workflow, quality, team, and AI-assisted development signals</li><li>DORA and flow context connected with adjacent SDLC data</li><li>AI Impact, AI Chat, AI Insights, and AI IDE Plugin for interpreting AI-assisted development</li><li>Benchmarks and reporting for leadership context</li><li>Cloud, private cloud, and on-premise deployment options for organizations with stricter governance needs</li></ul><p><strong>Important considerations</strong></p><p>Oobeya works best when an organization wants an engineering intelligence layer, not only a narrow dashboard for one workflow. Teams should identify which data sources matter most before rollout.</p><p><strong>Typical fit</strong></p><p>Oobeya fits CTOs, VPs of Engineering, engineering directors, platform teams, transformation leaders, and engineering managers who need trusted visibility across teams, tools, vendors, and AI-assisted development programs.</p><p>Related pages: <a href="https://oobeya.io/engineering-metrics">Oobeya Engineering Metrics</a>, <a href="https://oobeya.io/dora-metrics-four-key">DORA Metrics</a>, <a href="https://oobeya.io/benchmarks">Benchmarks</a>, <a href="https://oobeya.io/comparison">Comparison Hub</a>.</p><h4>2. Swarmia</h4><p><strong>Best for:</strong> team-focused engineering effectiveness and developer productivity improvement.</p><p>Swarmia publicly positions itself around developer productivity, engineering intelligence, DORA, SPACE, working agreements, developer experience surveys, issue metrics, CI visibility, software capitalization, and AI adoption and cost measurement. Its product pages emphasize helping teams identify bottlenecks, improve productivity, and build feedback loops.</p><p><strong>Key strengths</strong></p><ul><li>Developer productivity and engineering metrics focus</li><li>DORA and SPACE positioning</li><li>Working agreements and team-level improvement loops</li><li>Developer experience surveys and qualitative feedback</li><li>AI adoption, productivity impact, and cost visibility in public positioning</li></ul><p><strong>Important considerations</strong></p><p>Swarmia can be a strong fit for teams that want structured productivity improvement and team habits. If your evaluation requires deep quality, test, security, deployment model, or enterprise governance requirements, validate those needs carefully against the product.</p><p><strong>Typical fit</strong></p><p>Swarmia often fits engineering organizations that want team-level productivity analytics, DORA and SPACE adoption, developer experience feedback, and operational improvement loops.</p><p>For a direct vendor comparison, see <a href="https://oobeya.io/oobeya-vs-swarmia">Oobeya vs Swarmia</a>.</p><h4>3. LinearB</h4><p><strong>Best for:</strong> development workflow automation, pull request orchestration, and productivity reporting.</p><p>LinearB publicly emphasizes workflow automation, programmable workflows, pull request routing, code review automation, DORA, engineering goals, benchmarks, developer experience, and AI workflow governance. This makes it especially relevant when the buying question is “how do we improve PR flow and automate best practices?”</p><p><strong>Key strengths</strong></p><ul><li>Workflow automation and PR orchestration</li><li>Pull request routing, labels, auto-merge policies, and code review automations</li><li>Engineering metrics, goals, benchmarks, and productivity reporting</li><li>AI workflow governance and AI code review positioning</li><li>Integrations with common development tools</li></ul><p><strong>Important considerations</strong></p><p>LinearB may be a strong option when workflow automation is the center of the program. If the decision requires broader SDLC intelligence across quality, testing, security, enterprise reporting, or deployment control, compare scope carefully.</p><p><strong>Typical fit</strong></p><p>LinearB often fits teams that want to improve code review flow, enforce workflow policies, reduce developer toil around PRs, and connect productivity goals with automation.</p><p>For a direct vendor comparison, see <a href="https://oobeya.io/oobeya-vs-linearb">Oobeya vs LinearB</a>.</p><h4>4. DX (GetDX)</h4><p><strong>Best for:</strong> developer experience, productivity measurement frameworks, surveys, and AI measurement.</p><p>DX publicly emphasizes developer experience measurement, developer productivity, research-backed methods, benchmarking, the DX Core 4 framework, DORA, SPACE, and AI measurement. Its materials position DX around combining experience data, system metrics, and AI-specific measurement.</p><p><strong>Key strengths</strong></p><ul><li>Developer experience measurement and surveys</li><li>DX Core 4 framework spanning speed, effectiveness, quality, and business impact</li><li>DORA, SPACE, and DevEx-oriented productivity measurement</li><li>Benchmarks and research-backed measurement programs</li><li>AI Measurement Framework for adoption, impact, and cost</li></ul><p><strong>Important considerations</strong></p><p>DX can be compelling when the engineering organization wants a structured DevEx and productivity program. If the immediate need is operational analytics across quality, testing, security, incident context, deployment models, or broader governance, validate coverage carefully.</p><p><strong>Typical fit</strong></p><p>DX often fits developer productivity teams, DevEx leaders, platform teams, and engineering executives that want a research-backed measurement program combining surveys, system metrics, benchmarks, and AI measurement.</p><p>For direct comparison context, see <a href="https://oobeya.io/oobeya-vs-dx">Oobeya vs DX</a>.</p><h4>5. Jellyfish</h4><p><strong>Best for:</strong> engineering management, investment allocation, and business alignment.</p><p>Jellyfish publicly positions itself as an engineering management and software engineering intelligence platform. Its materials emphasize allocations, business alignment, engineering and product operations, delivery management, team health, AI-integrated engineering intelligence, and enterprise-grade integrations and controls.</p><p><strong>Key strengths</strong></p><ul><li>Engineering investment and allocation visibility</li><li>Business alignment for engineering leadership</li><li>Engineering management reporting and team health</li><li>AI-integrated engineering intelligence positioning</li><li>Enterprise-grade integrations, security, identity, and compliance messaging</li></ul><p><strong>Important considerations</strong></p><p>Jellyfish may be a strong fit when the main question is where engineering effort is going and how it aligns with business priorities. If your top need is deep workflow-level quality, testing, security analytics, or on-premise deployment, validate those areas directly.</p><p><strong>Typical fit</strong></p><p>Jellyfish often fits engineering executives, finance-adjacent engineering leaders, product and engineering operations teams, and organizations that need to explain engineering investment to the business.</p><p>For direct comparison context, see <a href="https://oobeya.io/oobeya-vs-jellyfish">Oobeya vs Jellyfish</a>.</p><h4>6. Apache DevLake</h4><p><strong>Best for:</strong> teams that want an open-source dev data platform they can customize.</p><p>Apache DevLake describes itself as an open-source dev data platform that ingests, analyzes, and visualizes fragmented data from DevOps tools. Its public documentation highlights DORA dashboards, SDLC data integration, Grafana dashboards, custom metrics, and extensibility.</p><p><strong>Key strengths</strong></p><ul><li>Open-source engineering data foundation</li><li>DORA dashboards and engineering metrics</li><li>Data ingestion from common DevOps tools</li><li>Custom SQL, Grafana dashboards, and extensibility</li><li>Good fit for teams with internal data engineering capability</li></ul><p><strong>Important considerations</strong></p><p>Apache DevLake can reduce vendor lock-in and increase flexibility, but it also requires internal ownership. Someone must manage setup, integrations, data definitions, dashboard governance, upgrades, and interpretation.</p><p><strong>Typical fit</strong></p><p>Apache DevLake often fits engineering organizations with data engineering capacity, open-source preference, and a desire to build a customized engineering analytics layer.</p><p>For direct comparison context, see <a href="https://oobeya.io/oobeya-vs-apache-devlake-incubating">Oobeya vs Apache DevLake</a>.</p><h3>How to Choose the Right Engineering Metrics Tool</h3><h4>If You Are Just Starting</h4><p>Start with a small set of metrics: cycle time, deployment frequency, change failure rate, recovery time, review time, escaped defects, and developer feedback. Avoid beginning with individual productivity scores.</p><p>Look for a product that helps your teams trust the definitions. If engineers do not believe the data, the program will become dashboard theater.</p><h4>If You Already Track DORA</h4><p>Ask what DORA is missing. DORA can show that delivery is slowing down, but it may not explain whether the cause is review queues, flaky CI, unclear requirements, quality debt, overloaded teams, or release governance.</p><p>At that stage, compare platforms by how well they connect DORA to workflow, quality, project, and developer experience context.</p><h4>If AI Measurement Is a Priority</h4><p>Do not measure AI only by license activation or prompt volume. Useful AI metrics connect usage to outcomes: review load, cycle time, code churn, quality, vulnerabilities, test failures, developer experience, and business impact.</p><p>AI can increase output while hiding new bottlenecks. The platform should help you separate activity from durable improvement.</p><h4>If Governance Matters</h4><p>If your organization has strict rules around source code, engineering data, customer data, AI model usage, or regional data residency, include deployment architecture early in the evaluation.</p><p>Questions to ask:</p><ul><li>Is SaaS acceptable?</li><li>Is private cloud required?</li><li>Is on-premise required?</li><li>Can the platform support SSO, role-based access, and audit requirements?</li><li>How are AI features deployed and governed?</li><li>Can sensitive engineering data remain inside approved environments?</li></ul><h4>If You Need Executive Reporting</h4><p>Executives usually do not need more metrics. They need a clear explanation of delivery health, risk, quality, investment, and trend direction.</p><p>Look for a platform that can answer:</p><ul><li>Are teams delivering faster without increasing risk?</li><li>Where is engineering effort going?</li><li>Which bottlenecks are slowing delivery?</li><li>Are AI investments improving outcomes?</li><li>Which teams need support, not pressure?</li><li>Which risks need leadership action?</li></ul><h3>Common Mistakes When Buying Engineering Metrics Tools</h3><p><strong>Mistake 1: Buying for dashboards instead of decisions.</strong> A dashboard is useful only if it changes what teams do next.</p><p><strong>Mistake 2: Overweighting activity metrics.</strong> Commit count, PR count, and ticket count are easy to collect, but they do not prove value.</p><p><strong>Mistake 3: Treating DORA as the whole program.</strong> DORA is a strong delivery lens, not a complete engineering intelligence system.</p><p><strong>Mistake 4: Ignoring developer trust.</strong> If the platform feels like surveillance, engineers will resist it and the data will become less useful.</p><p><strong>Mistake 5: Forgetting quality.</strong> Faster delivery with more rework, defects, and incidents is not productivity.</p><p><strong>Mistake 6: Leaving AI out of the model.</strong> AI-assisted development is now part of how software is built. It needs measurement, guardrails, and outcome context.</p><h3>Final Recommendation</h3><p>Shortlist tools by your primary operating question:</p><ul><li>Need broad SDLC engineering intelligence? Start with <a href="https://oobeya.io/"><strong>Oobeya</strong></a>.</li><li>Need team productivity loops and working agreements? Evaluate <strong>Swarmia</strong>.</li><li>Need PR automation and workflow orchestration? Evaluate <strong>LinearB</strong>.</li><li>Need DevEx and productivity measurement frameworks? Evaluate <strong>DX</strong>.</li><li>Need investment allocation and business alignment? Evaluate <strong>Jellyfish</strong>.</li><li>Need open-source flexibility and internal ownership? Evaluate <strong>Apache DevLake</strong>.</li></ul><p>Then run the same proof-of-fit exercise for every vendor: connect your real data sources, define your DORA events, inspect quality and workflow context, test AI measurement, review governance requirements, and ask whether engineering managers can use the output without a data team.</p><h3>Frequently Asked Questions</h3><h4>What is an engineering metrics tool?</h4><p>An engineering metrics tool helps software teams collect and interpret data about delivery, workflow, quality, productivity, developer experience, reliability, and engineering outcomes. The best tools connect metrics to decisions instead of simply reporting activity.</p><h4>What metrics should software teams track first?</h4><p>Most teams should start with cycle time, deployment frequency, lead time for changes, change failure rate, recovery time, review time, escaped defects, work in progress, and developer feedback. Add AI metrics once AI coding assistants or agents become material to the delivery process.</p><h4>Are DORA metrics enough?</h4><p>DORA metrics are useful, but they are not enough by themselves. They should be interpreted alongside quality, workflow, project, developer experience, team health, and AI-assisted development signals.</p><h4>Which engineering metrics tool is best for AI-assisted development?</h4><p>The best choice depends on what you need to measure. Oobeya is relevant when AI impact must be interpreted alongside delivery, quality, review, workflow, and governance context. DX is relevant for AI measurement frameworks and DevEx-oriented productivity measurement. Swarmia, LinearB, and Jellyfish also publish AI-related measurement and governance positioning.</p><h4>How do you avoid using engineering metrics for surveillance?</h4><p>Measure the engineering system, not individual output. Avoid ranking engineers by commit count, PR count, story points, or lines of code. Use metrics to identify bottlenecks, reduce friction, improve quality, and support teams.</p><h4>Should a small software team use an engineering metrics platform?</h4><p>Yes, if the team has recurring delivery, quality, workflow, or planning problems that cannot be understood from existing tools. Smaller teams should keep the metric set simple and avoid over-instrumentation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c07b83ed1d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Advanced DevOps Insights: A Guide to Azure DevOps DORA Metrics]]></title>
            <link>https://emredundar.medium.com/advanced-devops-insights-a-guide-to-azure-devops-dora-metrics-18fdc9131559?source=rss-cf1aed6d40d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/18fdc9131559</guid>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[dora-metrics]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <dc:creator><![CDATA[Emre Dundar]]></dc:creator>
            <pubDate>Tue, 05 May 2026 13:56:34 GMT</pubDate>
            <atom:updated>2026-05-05T13:56:34.651Z</atom:updated>
            <content:encoded><![CDATA[<p>For modern software teams, data-driven decision-making is the cornerstone of achieving engineering excellence. By integrating the Oobeya Software Engineering Intelligence Platform with Microsoft Azure DevOps, you can seamlessly measure DORA metrics and other key engineering metrics, and enhance your team performance and well-being.</p><p>Whether you are an engineering manager, a DevOps enthusiast, a Platform Engineer, or a development team lead, this integration simplifies tracking and improving your software delivery performance.</p><h3>The Importance of Tracking Azure DevOps DORA Metrics</h3><p>DORA (DevOps Research and Assessment) metrics are vital indicators of an organization’s software delivery performance. They include:</p><ul><li><strong>Deployment Frequency:</strong> How often an organization successfully releases to production.</li><li><strong>Lead Time for Changes:</strong> The time it takes for a commit to get into production.</li><li><a href="https://oobeya.io/blog/what-is-the-impact-of-mttr-mean-time-to-recovery-on-software-quality"><strong>Mean Time to Recovery</strong></a><strong>:</strong> The time it takes to recover from a failure in production.</li><li><strong>Change Failure Rate:</strong> The percentage of deployments causing a failure in production.Oobeya Azure DevOps DORA Metrics</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*T84DSVOGCyG5XX9s.jpg" /><figcaption>Oobeya Azure DevOps DORA Metrics</figcaption></figure><h3>Why DORA Metrics Matter</h3><ol><li><strong>Continuous Improvement:</strong> By tracking these metrics, teams can identify bottlenecks, streamline processes, and continuously improve their delivery cycles.</li><li><strong>Business Impact:</strong> Faster and more reliable delivery can lead to a competitive advantage, improved customer satisfaction, and higher business agility.</li><li><strong>Team Performance:</strong> Understanding these metrics helps in gauging team performance and providing actionable insights to enhance productivity and efficiency.</li></ol><h3>Visibility into Engineering Flow: Why It Matters</h3><p>Engineering teams need visibility into their flow to ensure smooth operations and high-quality outcomes. Here’s why visibility is crucial:</p><ol><li><strong>Identify Bottlenecks:</strong> Clear visibility helps in pinpointing stages where delays occur, enabling teams to address and resolve issues promptly.</li><li><strong>Optimize Processes:</strong> With a transparent view of workflows, teams can optimize processes for better efficiency and reduced waste.</li><li><strong>Enhance Collaboration:</strong> Visibility fosters better communication and collaboration among team members, ensuring everyone is on the same page.</li><li><strong>Boost Morale:</strong> When teams see the direct impact of their work on project success, it boosts morale and motivation.</li></ol><h3>Oobeya: A Strong Partner of the Azure DevOps Ecosystem</h3><p>Oobeya is a powerful ally for organizations using Azure DevOps. By integrating with Azure DevOps, Oobeya enhances your ability to track and improve engineering performance through comprehensive metrics and insights. Here’s why Oobeya stands out:</p><ol><li><strong>Seamless Integration:</strong> Oobeya connects effortlessly with Azure DevOps, allowing you to integrate your repositories, pipelines, releases, and boards in minutes by generating one access token (only read permissions for selected scopes are required).</li><li><strong>Robust Metrics:</strong> Oobeya provides accurate DORA metrics and other key metrics, helping you make data-driven decisions.</li><li><strong>Aligning with the SPACE Framework:</strong> Oobeya automatically detects the symptoms of inefficiencies and bottlenecks within the software development and delivery processes, offering a detailed <a href="https://docs.oobeya.io/symptoms/symptoms-catalog">symptoms catalog</a> that resonates with SPACE dimensions. Oobeya provides actionable insights into Satisfaction and well-being, Performance, Activity, Communication and collaboration, Efficiency and flow.</li><li><strong>Customization:</strong> Tailor your integration by selecting specific pipelines, stages, environments, release strategies (git-flow, long-lived branches, git tags), and development practices (trunk-based or pull-request-based) to suit your organization’s needs.</li><li><strong>Comprehensive Reporting:</strong> Gain deep insights through advanced reporting features, helping you analyze and improve every aspect of your development process on a multi-dimensional level.</li><li><strong>ADO Version Support:</strong> Oobeya supports both Azure DevOps Cloud and Server environments, ensuring compatibility across different setups.</li></ol><h3>Getting Started: A Comprehensive Guide</h3><h4>Step 1: Provide an Azure DevOps Token</h4><p>To begin, generate an Azure DevOps (ADO) personal access token. This token allows Oobeya to access your repositories, pipelines, pull requests, and work items. Oobeya integration requires only read permissions for the selected scopes. <a href="https://docs.oobeya.io/integrations/all-integrations/scm-addons/azure-devops-integration">Learn more about Azure DevOps &amp; Oobeya Integration</a></p><h4>Step 2: Connect Your Accounts</h4><p>Link your Oobeya account to your Azure DevOps environment. This process is straightforward and can be completed in minutes.</p><h4>Step 3: Start Analyzing Your Data</h4><p>Choose your repositories and pipelines to analyze. Specify your release strategy and development practices to ensure accurate metrics.</p><h3>Advanced Features of Oobeya and Azure DevOps Integration</h3><h4>1. Comprehensive Azure DevOps DORA Metrics Measurement For Different Workflows And Practices</h4><p>Oobeya enables you to:</p><ul><li><strong>Add Multiple Deployment Pipelines:</strong> Aggregate DORA metrics across multiple deployment pipelines within a single repository. (If you have a repository and multiple delivery pipelines linked to it.)</li><li><strong>Select Pipelines from Different Projects:</strong> Fine-tune DORA metrics calculation by selecting pipelines and releases from different projects. (If you manage pipeline definitions and runs in a different Azure DevOps project.)</li><li><strong>Support Various Release and Development Strategies:</strong> Measure DORA metrics accurately whether you use Gitflow, long-lived branches, or Git tags. Specify whether your team follows a trunk-based or pull-request-driven development practice.</li></ul><h4>2. Advanced Data Analytics and Reporting</h4><p>With Oobeya, you can:</p><ul><li><strong>Analyze Coding, Code Review, and Delivery Activities:</strong> Generate insightful reports by analyzing repositories, commits, pull requests, and delivery pipelines across the Azure DevOps workflow.</li><li><strong>Analyze Agile Boards:</strong> Generate insightful reports by analyzing scrum and kanban boards from Azure Boards.</li><li><strong>Group Analysis Results:</strong> View all metrics at various levels, including repository, product, team, and organization. (Note that Oobeya is a team-focused platform.)</li></ul><h3>Additional Integrations and Features</h3><h4>Azure DevOps Cloud and Server Support</h4><p>Oobeya supports both Azure DevOps Cloud and Server environments, ensuring flexibility for different organizational setups.</p><h4>Comprehensive Module Compatibility</h4><p>The platform works seamlessly with Azure DevOps Repos, Azure Boards, Pipelines, and Releases modules.</p><h4>Microsoft Entra (Azure AD) Integration</h4><p>For enhanced security and streamlined user management, Oobeya integrates with Microsoft Entra (Azure AD). This enables single sign-on (SSO) and robust authentication settings.</p><h4>Resources to Get You Started</h4><ul><li><a href="https://docs.oobeya.io/integrations/all-integrations/scm-addons/azure-devops-integration">Learn more about Azure DevOps &amp; Oobeya Integration</a></li><li><a href="https://docs.oobeya.io/deployment-analytics/how-to-calculate-dora-metrics-for-azure-devops">How To Measure DORA Metrics for Azure DevOps</a></li><li><a href="https://docs.oobeya.io/administration/user-management-single-sign-on-auth-settings/azure-ad-integration">Azure AD Integration</a></li></ul><h3>Conclusion</h3><p>Integrating Oobeya with Azure DevOps transforms how you measure and improve your software engineering performance. With robust support for DORA metrics, customizable analytics, and comprehensive reporting, Oobeya empowers your team to achieve new levels of efficiency and reliability.</p><p><a href="https://oobeya.io/get-started-with-oobeya/">Start your integration today</a> and unlock the full potential of your software development and delivery process.</p><p><em>Originally published at </em><a href="https://oobeya.io/blog/advanced-devops-insights-oobeyas-guide-to-azure-devops-dora-metrics"><em>https://oobeya.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18fdc9131559" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Identify Productivity Eaters: Top 5 Tools For Engineering Managers In 2024]]></title>
            <link>https://emredundar.medium.com/top-5-tools-for-engineering-managers-in-2024-8773a0c8031a?source=rss-cf1aed6d40d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/8773a0c8031a</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Emre Dundar]]></dc:creator>
            <pubDate>Mon, 20 May 2024 13:58:48 GMT</pubDate>
            <atom:updated>2024-05-20T13:59:54.639Z</atom:updated>
            <content:encoded><![CDATA[<p>Engineering managers are continually seeking the best tools to boost team productivity, streamline processes, enhance employee experience, and maintain quality. With a myriad of options available, it can be challenging to identify which tools truly stand out. This post highlights five standout tools that every engineering manager should consider integrating into their workflow.</p><h3>Why I Wrote This Blog Post</h3><p>I often hear the question, “What are tools I can use as an Engineering Manager?” so here is a post answering this question. I frequently talk to engineering managers and listen to their requirements and experiences with tools. I also check the pulse of the market and try new tools as a product leader in this field.</p><p>Before diving into the list, I want to clarify a few points about its creation. This list excludes tools commonly used by teams, such as Jira, Linear, Git tools, and Slack. Instead, I’ve highlighted the most innovative and exceptional tools across various categories like employee experience, engineering intelligence, code quality, security, and collaboration. This article is not driven by any hype.</p><h3>1. Packmind (Collaboration)</h3><blockquote>Amplify knowledge, improve engineering performance: Accelerate your team’s skill growth and improve coding standards by intelligently integrating the best coding practices directly within your familiar coding environments and tailored to your unique context.</blockquote><p>Packmind is a standout tool for enhancing collaboration and knowledge sharing within engineering teams. It offers a comprehensive approach to embedding coding standards and best practices directly into your workflow.</p><h4>Key Features:</h4><ul><li><strong>Coding Standards:</strong> Automatically scans your repository to identify good coding standards and problematic patterns.</li><li><strong>Best Practices:</strong> Provides a comprehensive set of best coding practices based on principles of clean code.</li><li><strong>Onboarding:</strong> Effortlessly onboard new developers on your coding standards.</li><li><strong>Knowledge Sharing: </strong>Breaks down knowledge silos within teams, promoting better collaboration.</li></ul><p>Discover more about Packmind <a href="https://www.packmind.com/">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bQbCfqlEZ4DWTBUpSu7m6Q.png" /><figcaption>Packmind</figcaption></figure><h3>2. Oobeya (Engineering Intelligence)</h3><blockquote>Accurate Metrics. Clear Insights. Data-Driven Decisions: Empowering engineering leaders to identify SDLC bottlenecks, assess team productivity, and improve engineering efficiency with top-notch data-driven insights.</blockquote><p>Oobeya stands out with its innovative approach to automatically detecting and addressing development and delivery symptoms. By leveraging key engineering metrics and hundreds of data points, Oobeya enables software organizations to effortlessly identify recurring anti-patterns, bottlenecks, and roadblocks. With actionable insights derived from in-depth metrics and data analytics, Oobeya empowers engineering leaders to take proactive steps toward optimizing their processes and cultivating healthy, effective teams.</p><h4>Key Features:</h4><ul><li><strong>Advanced Analytics: </strong>Provides in-depth analytics for repositories, delivery pipelines, issue tracking, agile boards, etc.</li><li><strong>Key Engineering Metrics: </strong>Measures and tracks over 50 key engineering metrics effortlessly (DORA, SPACE, agile metrics, cycle time, pull request analytics, etc.).</li><li><strong>Integration Catalog:</strong> Integrates with over 20 DevOps tools (Git tools, Jira, Azure Boards, CI/CD tools, APM tools, Sonarqube).</li><li><strong>Team Insights: </strong>Assesses the current situation of engineering excellence and provides smart suggestions for improvement areas.</li></ul><p>Explore the benefits of Oobeya <a href="https://oobeya.io/">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8VVreCrSauJc1JOlU_LBUQ.png" /><figcaption>Oobeya Software Engineering Intelligence Platform</figcaption></figure><h3>3. DeepSource (Code Quality)</h3><blockquote>The Code Health Platform: Build maintainable and secure software with the power of static analysis and AI.</blockquote><p>DeepSource stands out with its ability to automate the code review process, catching issues before they become costly problems. Its real-time feedback loop helps developers adhere to best practices, ensuring a high standard of code quality across the team. This tool’s extensive language support and integration capabilities make it a versatile addition to any engineering manager’s toolkit. You may replace all other tools you use to write clean and secure code with the DeepSource platform.</p><h4>Key Features:</h4><ul><li><strong>Automated Code Reviews:</strong> Analyzes every pull request to find and fix code quality issues before merging to the main branch.</li><li><strong>Security Detection:</strong> Identifies and highlights potential security risks.</li><li><strong>Continuous Integration: </strong>Integrates seamlessly with your CI/CD pipeline for continuous code analysis.</li><li><strong>Multi-language Support: </strong>Supports multiple programming languages including Infrastructure-as-code analysis.</li></ul><p>Check out DeepSource <a href="https://deepsource.com/">here</a>.</p><h3>4. CultureAmp (Employee Experience)</h3><blockquote>An employee experience that people love: Get the employee engagement, performance, and development tools and insights you need to build a category-defining culture.</blockquote><p>CultureAmp is an employee engagement platform that helps engineering managers foster a positive work environment and enhance team morale. By providing insights into employee satisfaction, CultureAmp enables managers to take proactive steps to address concerns and improve overall team dynamics. Its detailed analytics enable engineering managers to pinpoint specific areas for improvement, ensuring targeted and effective interventions.</p><h4>Key Features:</h4><ul><li><strong>Employee Surveys:</strong> Conducts regular surveys to gauge employee satisfaction and gather feedback.</li><li><strong>Comprehensive Analytics:</strong> Provides deep data and insights across your entire employee experience.</li><li><strong>Feedback Tools:</strong> Customizable feedback tools, goal-tracking features, and ready-to-use surveys.</li><li><strong>Employee Development: </strong>Aligns individual development with company goals, driving personal growth and business success.</li></ul><p>Learn more about CultureAmp <a href="https://www.cultureamp.com/">here</a>.</p><h3>5. Invicti (Application Security)</h3><blockquote>Application Security Testing For Tech Companies: Secure every website, web app, and API. Even if you have thousands of them. Only with Invicti.</blockquote><p>Invicti is a leading web application security tool that helps engineering managers ensure the security of their applications. By providing comprehensive security testing and real-time vulnerability detection, Invicti helps teams maintain robust security standards. Its easy-to-use platform and powerful features make it a top choice for managing application security. This tool’s detailed reports and actionable insights enable engineering managers to address security issues swiftly and effectively.</p><h4>Key Features:</h4><ul><li><strong>Comprehensive Security Analysis: </strong>Performs automated scans to detect security vulnerabilities.</li><li><strong>Detailed Reports: </strong>Provides detailed reports with actionable insights to fix security issues.</li><li><strong>Continuous Monitoring: </strong>Continuously monitors applications for new vulnerabilities.</li><li><strong>Integration: </strong>Integrates with tools and workflows your developers use daily (50+ integrations).</li></ul><p>Explore Invicti <a href="https://www.invicti.com/">here</a>.</p><h3>The Final: The Productivity Eaters</h3><p>In 2024, engineering managers have access to a range of powerful tools designed to enhance productivity, streamline workflows, and maintain code quality. By integrating these standout tools into your engineering management strategy, you can ensure that your team operates at peak efficiency and delivers high-quality results. From project management and team dynamics to code quality and security, these tools provide comprehensive solutions to the challenges faced by engineering managers today.</p><p>I have picked my favorite five for you, but you can research each market and find alternatives to these products. Packmind defines the problem as “Poor knowledge sharing &amp; coding practices are <em>productivity eaters</em>”. Engineering Managers cannot measure productivity in software development, but they can find all the “productivity eaters” for their organizations. These five tools help you identify your productivity eaters and build healthy and effective development teams!</p><p>Thanks for reading! If you’d like more information about these tools and practices, visit my <a href="https://www.linkedin.com/in/emredundar/">LinkedIn profile</a> and feel free to chat with me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8773a0c8031a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond DORA Metrics: Identifying Symptoms That Lead To Poor DORA Metrics]]></title>
            <link>https://emredundar.medium.com/beyond-dora-metrics-identifying-symptoms-that-lead-to-poor-dora-metrics-7a410bd9f56b?source=rss-cf1aed6d40d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a410bd9f56b</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[dora]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Emre Dundar]]></dc:creator>
            <pubDate>Fri, 17 Mar 2023 20:21:51 GMT</pubDate>
            <atom:updated>2023-03-17T20:21:51.230Z</atom:updated>
            <content:encoded><![CDATA[<h4>Explore the correlation between team symptoms and DORA Metrics. Take your team’s productivity and well-being to the next level with this insightful guide.</h4><p>Software development is a challenging and constantly evolving field that requires a high level of teamwork, collaboration, and productivity. To measure the effectiveness of their development processes, teams often turn to <strong>DORA (DevOps Research and Assessment) metrics</strong>, which are industry-standard measures of software delivery performance. However, measuring DORA metrics alone is not enough to improve software development processes. To truly thrive, teams need to identify and address the root causes of all issues affecting their metrics.</p><p>This is where <strong><em>symptoms</em></strong> come in. Symptoms are indicators of underlying problems in the development process that can <strong>lead to poor DORA metrics</strong>. By identifying and addressing symptoms, teams can improve their development processes and, in turn, improve their DORA metrics. In this article, we’ll explore the correlation between team symptoms and DORA Metrics and how addressing symptoms can help teams boost their software delivery performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sWzbWAtfelSunhXnRDnFcA.png" /></figure><h4>Oobeya Symptoms Overview</h4><p>The Oobeya Symptoms module is a powerful tool for identifying and resolving problems in software development and delivery processes. In Oobeya, a <a href="https://docs.oobeya.io/symptoms/symptoms-catalog">symptom</a> is a recurring anti-pattern, bad practice, bottleneck, or roadblock in the software development and delivery process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WrWCvemF9ZzySB-i8Kd2Kw.png" /><figcaption>Oobeya Symptoms</figcaption></figure><p><strong>Symptoms are automatically detected by Oobeya</strong>, leveraging over 50 key engineering metrics, and can be used to identify areas where improvements can be made to the software development and delivery process. By addressing the underlying causes of these symptoms, teams can improve their software development and delivery processes and achieve better outcomes.</p><h4>Understanding DORA Metrics</h4><p>As software development teams strive to improve their processes and deliver high-quality products quickly, it’s important to have a way to measure progress and identify areas for improvement. DORA metrics are a set of four key performance indicators that can help teams measure their delivery performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VU9s6-PThfo44njRpPenMA.png" /><figcaption>Oobeya DORA Metrics</figcaption></figure><h3>Symptoms That Affect DORA Metrics</h3><p>Symptoms are indicators of problems or <strong>inefficiencies</strong> in your software development process. Various symptoms can impact DORA metrics. Some of the <strong>most common symptoms</strong> include a <em>recurring high rework rate, high technical debt on SonarQube, oversize pull requests, a high cognitive load, lightning pull requests, </em>and<em> a high pull request revert rate</em>. These symptoms can <strong>slow down team performance</strong> and <strong>impact DORA metrics</strong> in various ways.</p><p>Symptoms can have a significant impact on DORA metrics. For example, having high technical debt and complexity can <strong>increase lead time for changes</strong>, while oversize pull requests can <strong>decrease deployment frequency</strong>. Lightning pull requests and having high code quality bugs can <strong>increase the change failure rate</strong> and <strong>time to restore service</strong>. By understanding the relationship between symptoms and DORA metrics, teams can take proactive measures to improve performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LpnAAk8oQPCGmv_0UNnSHw.png" /><figcaption>Symptoms that affect DORA Metrics</figcaption></figure><p>Here are some examples of how the <a href="https://oobeya.io/dora-metrics-four-key/">DORA Metrics</a> are correlated with specific symptoms:</p><h4>1. Lead Time For Changes (LTC)</h4><p>This measures the amount of time it takes a commit to get into production. The best thing you can do to reduce Change Lead Time is to identify software development waste and bottlenecks. <strong>Lead Time for Changes</strong> is correlated with the following symptoms:</p><ul><li><strong>Recurring high rework rate: </strong>A high LTC may indicate that code changes are not being thoroughly reviewed or tested, resulting in the need for frequent rework. Learn more about this symptom <a href="https://docs.oobeya.io/symptoms/symptoms-catalog/s1-recurring-high-rework-rate">here</a>.</li><li><strong>High technical debt on Sonarqube:</strong> A high LTC may indicate that technical debt is accumulating in the codebase, making it more difficult and time-consuming to make changes in the codebase. Learn more about this symptom <a href="https://docs.oobeya.io/symptoms/symptoms-catalog/s6-high-technical-debt-on-sonar">here</a>.</li><li><strong>Oversize Pull Requests: </strong>A high LTC may be a result of large, complex code changes that are difficult to review and test, leading to delays in the delivery process. Learn more about this symptom <a href="https://docs.oobeya.io/symptoms/symptoms-catalog/s11-oversize-pull-requests">here</a>.</li></ul><p>Learn more about how to reduce Lead Time For Changes:</p><p><a href="https://betterprogramming.pub/how-to-reduce-lead-time-for-changes-optimizing-dora-metrics-e97d47e11701">How To Reduce Lead Time for Changes (Optimizing DORA Metrics)</a></p><h4>2. Deployment Frequency (DF)</h4><p>This measures how often code changes are deployed to production. <strong>Deployment Frequency</strong> is correlated with the following symptoms:</p><ul><li><strong>Recurring high cognitive load:</strong> A low DF may indicate that team members are experiencing a high cognitive load due to a lack of resources or poor planning process, leading to lower productivity, poor developer experience, and increased stress. Learn more about this symptom <a href="https://docs.oobeya.io/symptoms/symptoms-catalog/s2-recurring-high-cognitive-load">here</a>.</li><li><strong>Oversize Pull Requests: </strong>High-performing software teams release often and in small batches. A low DF may also be a result of large, complex code changes that are difficult to review and test, leading to a reviewer bottleneck in the delivery process. Learn more about this symptom <a href="https://docs.oobeya.io/symptoms/symptoms-catalog/s11-oversize-pull-requests">here</a>.</li></ul><h4>3. Change Failure Rate (CFR)</h4><p>This measures the percentage of deployments causing a failure in production. The failures can significantly impact the stability and reliability of software systems, making it crucial for organizations to detect and resolve them as quickly as possible. <strong>Change Failure Rate</strong> is correlated with the following symptoms:</p><ul><li><strong>Lightning Pull Requests: </strong>A high Change Failure Rate may be a sign that the team’s code review procedure is weak, which causes unstable and unreliable code. Pull Requests merged in 1–2 min without sufficient review or testing may introduce bugs or other issues that can lead to production failures. Learn more about this symptom <a href="https://docs.oobeya.io/symptoms/symptoms-catalog/s10-lightning-pull-requests">here</a>.</li><li><strong>High Technical Debt on Sonarqube: </strong>High technical debt means that there are a lot of issues that need to be fixed, and this can increase the probability of failures in production. Learn more about this symptom <a href="https://docs.oobeya.io/symptoms/symptoms-catalog/s6-high-technical-debt-on-sonar">here</a>.</li><li><strong>High Pull Request Revert Rate: </strong>Pull Requests that are reverted frequently can indicate issues with the code or the development process. If Pull Requests are reverted frequently, it can lead to delays and decreased confidence in the development process.</li></ul><p>Discover how Oobeya detects production failures and calculates CFR:</p><p><a href="https://blog.devops.dev/dora-metrics-tracking-how-to-effectively-detect-production-failures-calculate-change-failure-dcf14042964a">DORA Metrics Tracking: How to Effectively Detect Production Failures &amp; Calculate Change Failure…</a></p><h4>4. Mean Time to Restore Service (MTTR)</h4><p>This measures how long it takes to restore service after a production incident. <strong>Time to Restore Service</strong> is correlated with the following symptoms:</p><ul><li><strong>High Technical Debt on Sonarqube:</strong> High technical debt and complexity can slow down the process of restoring service after a failure.</li><li><strong>Recurring high cognitive load:</strong> A high MTTR may be caused by knowledge silos within the team as a result of a lack of knowledge-sharing culture. The recurring high cognitive load may be a sign of knowledge silos.</li></ul><h4>Improving Team Health and Performance By Leveraging Auto-detected Symptoms and DORA Metrics</h4><p>To optimize team performance, it is crucial to identify and address symptoms that hinder productivity and teamwork. Fortunately, teams can leverage a range of tools and strategies to pinpoint such symptoms, such as Oobeya, which can automatically detect them based on predefined rules. Once identified, teams can take necessary actions to address the symptoms, including improving the code review process, reducing technical debt, and establishing clear knowledge-sharing procedures. By spotting and addressing symptoms, teams can improve DORA Metrics and achieve better business outcomes while fostering a healthier and more productive team.</p><p>Discover what Oobeya offers:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fapp.storylane.io%2Fdemo%2Fl6bz80qutw12&amp;display_name=Storylane&amp;url=https%3A%2F%2Fapp.storylane.io%2Fdemo%2Fl6bz80qutw12&amp;image=https%3A%2F%2Fstorylane-prod-published-pages.s3.us-east-2.amazonaws.com%2Fcompany%2Fcompany_fec01528-91c8-407e-87cb-afbdc2d8d5f0%2Fproject%2Fproject_469326f0-8466-46da-89d2-4a737cc301f4%2Fpreview.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=storylane" width="750" height="407" frameborder="0" scrolling="no"><a href="https://medium.com/media/830c1153d77026f0e4c1569e71b43a54/href">https://medium.com/media/830c1153d77026f0e4c1569e71b43a54/href</a></iframe><h4>Additional Resources</h4><ul><li>Original post: <a href="https://oobeya.io/blog/beyond-dora-metrics-identifying-symptoms-that-lead-to-poor-dora-metrics/">https://oobeya.io/blog/beyond-dora-metrics-identifying-symptoms-that-lead-to-poor-dora-metrics/</a></li><li>Oobeya Symptoms Catalog: <a href="https://docs.oobeya.io/symptoms/symptoms-catalog">https://docs.oobeya.io/symptoms/symptoms-catalog</a></li><li>Optimizing Team Performance in Software Development with Oobeya Team Health Module: <a href="https://oobeya.io/blog/optimizing-team-performance-in-software-development/">https://oobeya.io/blog/optimizing-team-performance-in-software-development/</a></li></ul><h4>Previous Articles About DORA Metrics</h4><ul><li>How to Measure DORA Metrics Accurately: <a href="https://oobeya.io/blog/how-to-measure-dora-metrics-accurately/">https://oobeya.io/blog/how-to-measure-dora-metrics-accurately/</a></li><li>How To Reduce Lead Time For Changes (Optimizing DORA Metrics): <a href="https://oobeya.io/blog/how-to-reduce-lead-time-for-changes-dora-metrics/">https://oobeya.io/blog/how-to-reduce-lead-time-for-changes-dora-metrics/</a></li><li>DORA Metrics Tracking: How to Effectively Detect Production Failures: <a href="https://oobeya.io/blog/dora-metrics-tracking-how-to-effectively-detect-production-failures/">https://oobeya.io/blog/dora-metrics-tracking-how-to-effectively-detect-production-failures/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a410bd9f56b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimizing Team Performance in Software Development]]></title>
            <link>https://emredundar.medium.com/optimizing-team-performance-in-software-development-5244fb89ef20?source=rss-cf1aed6d40d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/5244fb89ef20</guid>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[development-tools]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Emre Dundar]]></dc:creator>
            <pubDate>Mon, 13 Feb 2023 14:04:22 GMT</pubDate>
            <atom:updated>2023-02-13T14:04:22.007Z</atom:updated>
            <content:encoded><![CDATA[<h4>Optimizing team performance in software development requires a holistic approach that addresses both technical and cultural aspects of the development process.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*geLa7zMhU1D2eVcM" /><figcaption>Photo by <a href="https://unsplash.com/@joshuaryanphoto?utm_source=medium&amp;utm_medium=referral">Joshua Reddekopp</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In today’s fast-paced digital landscape, software development organizations are under constant pressure to deliver high-quality products in a timely manner. To meet this challenge, organizations need to identify and eliminate inefficiencies in their software development processes. This is where the <a href="https://oobeya.io/">Oobeya</a> Team Health Module comes in, providing a comprehensive solution to optimize team performance in software development.</p><p>The Oobeya Team Health Module is comprised of two main components: <strong>Team Symptoms</strong> and <strong>Team Scorecard</strong>. These components work together to help organizations improve team well-being, performance, and productivity.</p><h3>Team Symptoms: Detecting and Addressing Problems in the Development Process</h3><p>The Oobeya Symptoms module is a powerful tool for identifying and resolving problems in software development and delivery processes. The Oobeya Symptoms module collects and analyzes data from various sources to automatically detect recurring issues such as anti-patterns, bad practices, and bottlenecks that may be hindering team performance. Upon identifying these issues, the module alerts teams to potential problems and provides recommendations and solutions to resolve them. This allows teams to take proactive measures to improve their processes and avoid obstacles that could impact their performance and health.</p><figure><img alt="Oobeya Team Symptoms" src="https://cdn-images-1.medium.com/max/960/0*HxOunKpSs8EmOqvt" /></figure><h4>Available Symptoms (Coming More Soon)</h4><p>The Oobeya Symptoms module currently includes the following symptoms:</p><ol><li>Recurring high rework rate</li><li>Recurring high cognitive load</li><li>High weekend activity</li><li>High technical debt on Sonarqube</li><li>High vulnerabilities on Sonarqube</li><li>High code quality bugs on Sonarqube</li><li>Unreviewed Pull Requests</li><li>Lightning Pull Requests</li><li>Oversize Pull Requests</li></ol><blockquote>See the Oobeya Symptoms Catalog <a href="https://docs.oobeya.io/symptoms/symptoms-catalog">here</a>.</blockquote><h3>Team Scorecard: A Comprehensive View of Team Metrics and Progress</h3><p>The Team Scorecard provides teams with an all-encompassing view of their metrics and progress. The Scorecard automatically fetches data from <a href="https://oobeya.io/integrations/">integrations</a>, eliminating the need for manual work and enabling teams to maintain standards across all their tools. The Scorecard consists of multiple team-based metrics, which come from different data sources such as <a href="https://docs.oobeya.io/integrations/scm-addons/github-integrations">GitHub</a>, <a href="https://docs.oobeya.io/integrations/scm-addons/gitlab-addon">GitLab</a>, <a href="https://docs.oobeya.io/integrations/scm-addons/azure-devops-integration">Azure DevOps</a>, <a href="https://docs.oobeya.io/integrations/scm-addons/bitbucket-server-integration">Bitbucket</a>, <a href="https://docs.oobeya.io/integrations/project-management-addons/jira-cloud-integration">Jira</a>, <a href="https://docs.oobeya.io/integrations/scm-addons/jenkins-integration">Jenkins</a>, <a href="https://docs.oobeya.io/integrations/code-quality-addons/sonarqube-integration">Sonar</a>, Veracode, <a href="https://docs.oobeya.io/integrations/apm-monitoring-addons/new-relic-integration">New Relic</a>, DataDog, Dynatrace, and more. The historical data and team-based summaries provided by the Scorecard give teams deep visibility into their progress, bottlenecks, and areas for improvement, enabling them to make data-driven decisions and track the overall health of their teams.</p><figure><img alt="Oobeya Team Scorecard" src="https://cdn-images-1.medium.com/max/960/0*Pr7X25RSY9uYULsQ" /></figure><h3>Optimizing Team Performance in Software Development</h3><p>Optimizing team performance in software development requires a comprehensive approach that addresses both technical and cultural aspects of the development process. Here are some strategies to help optimize team performance:</p><ol><li><strong>Clear Communication:</strong> Ensure that team members have a clear understanding of their roles, responsibilities, and expectations. Encourage open communication channels and foster an environment where team members can freely share ideas, concerns, and feedback.</li><li><strong>Process Optimization:</strong> Evaluate and streamline development processes to eliminate bottlenecks and inefficiencies. Encourage teams to continuously improve processes through regular retrospectives and process improvement initiatives.</li><li><strong>Collaboration Tools:</strong> Utilize collaboration tools such as code review, version control systems, and project management software to increase transparency, efficiency, and accountability.</li><li><strong>Agile Methodology:</strong> Adopt an agile methodology such as Scrum or Kanban to better manage work and continuously improve.</li><li><strong>Team Metrics:</strong> Track and measure team progress using metrics such as cycle time, code review, DORA metrics, and code quality metrics. Use these metrics to identify areas for improvement and track progress over time.</li><li><strong>Continuous Learning:</strong> Encourage continuous learning through training, mentorship programs, and skill-building activities. This helps team members stay up-to-date on the latest technologies and best practices.</li><li><strong>Employee Engagement:</strong> Foster a positive work environment that values employee engagement and well-being. Regularly check in with team members to understand their needs, and provide support to help them achieve their personal and professional goals.</li><li><strong>Data-Driven Insights:</strong> Utilize data-driven insights to make informed decisions and track progress. Tools like <a href="https://oobeya.io/">Oobeya</a>’s Team Health module, which includes Team Symptoms and Team Scorecard components, can help teams gather and analyze data from various sources to identify issues and track progress over time.</li></ol><p>Optimizing team performance in software development requires a holistic approach that addresses both technical and cultural aspects of the development process. By implementing these strategies, organizations can improve the overall performance and productivity of their software development teams, delivering high-quality products in a timely and efficient manner.</p><h4>Resources</h4><ul><li>See the original post here: <a href="https://oobeya.io/blog/optimizing-team-performance-in-software-development/">https://oobeya.io/blog/optimizing-team-performance-in-software-development/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5244fb89ef20" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DORA Metrics Tracking: How to Effectively Detect Production Failures & Calculate Change Failure…]]></title>
            <link>https://blog.devops.dev/dora-metrics-tracking-how-to-effectively-detect-production-failures-calculate-change-failure-dcf14042964a?source=rss-cf1aed6d40d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcf14042964a</guid>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[dora-metrics]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[incident-management]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Emre Dundar]]></dc:creator>
            <pubDate>Mon, 30 Jan 2023 13:02:23 GMT</pubDate>
            <atom:updated>2023-02-02T13:26:15.374Z</atom:updated>
            <content:encoded><![CDATA[<h3>DORA Metrics Tracking: How to Effectively Detect Production Failures</h3><h4>Detecting production failures is the most critical and challenging component of tracking DORA metrics. While it can be challenging, organizations can overcome these challenges by using the right tools and following best practices.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WasAhAnAbbpJtcdZH6yY1A.png" /></figure><h4>Quick Intro: What Are DORA Metrics?</h4><p><a href="https://devops-research.com/">DORA (DevOps Research and Assessment)</a> <a href="https://oobeya.io/dora-metrics-four-key/">metrics</a> are a set of metrics that measure the performance of DevOps practices and processes in organizations. The metrics include <a href="https://oobeya.io/dora-metrics-four-key/">lead time, deployment frequency, mean time to restore, change failure rate</a>, and they aim to provide a comprehensive view of an organization’s ability to deliver value to customers. Learn more about DORA Metrics here: <a href="https://oobeya.io/blog/how-to-measure-dora-metrics-accurately/">https://oobeya.io/blog/how-to-measure-dora-metrics-accurately/</a></p><h3>What Is A Production Failure?</h3><p>One critical component of tracking <a href="https://oobeya.io/dora-metrics-four-key/">DORA metrics</a> is detecting production failures. Production failures occur when a change to the software system results in an unintended outcome, causing the system to malfunction or become unavailable. These failures can significantly impact the stability and reliability of software systems, making it crucial for organizations to detect and resolve them as quickly as possible.</p><h3>The Most Challenging Part of DORA Metrics Tracking: Detecting Production Failures</h3><p>However, detecting production failures can be a challenging task for organizations. One of the biggest challenges is automatically detecting production failures, which can be difficult due to the complexity of software systems and the limited visibility into production systems. Additionally, organizations are often overwhelmed by the sheer volume of data to be analyzed, making it difficult to identify and resolve failures quickly.</p><p>To overcome these challenges, organizations can use a variety of solutions and tools to detect production failures, including monitoring, log analysis, error tracking, user feedback, performance testing, change, and incident management. These tools can provide organizations with real-time insights into the performance and stability of their systems, allowing them to quickly detect and resolve failures.</p><p>In addition to using the right tools, organizations can also follow best practices for detecting production failures. These best practices include conducting regular health checks and setting up real-time alerts. By following these best practices, organizations can improve their ability to detect production failures and improve the stability and reliability of their software systems.</p><h3>How Oobeya Detects Production Failures and Calculates Change Failure Rate + MTTR</h3><p><a href="https://oobeya.io/">Oobeya</a> is a software engineering intelligence platform that allows software development organizations to gather and analyze data from various sources to make informed decisions and optimize their development and delivery processes.</p><p><a href="https://oobeya.io/">Oobeya</a> is also a <a href="https://oobeya.io/dora-metrics-four-key/">DORA Metrics Tracking tool</a> that provides valuable insights into the effectiveness of software development and delivery.</p><p>Oobeya has a unique mechanism for calculating <a href="https://oobeya.io/dora-metrics-four-key/">DORA Metrics</a> across platforms/tools (VCS, CICD, and APM-Incident Management tools) so that any organization can accurately and effortlessly track the journey of a commit from development to production deployment. Furthermore, no changes to workflows or pipelines are required; Oobeya seamlessly integrates with existing tools (GitHub, GitLab, Azure DevOps, Bitbucket, Jenkins, TeamCity, GitHub Actions, GitLab CI, Azure Pipelines, Releases, and more) to calculate DORA metrics.</p><p>Oobeya analyzes all deployments, detects production failures, and ties them back to production deployments.</p><p>Oobeya calculates all four key DORA Metrics. The <strong>Change Failure Rate</strong> (CFR) is the percentage of deployments causing a failure in production. This metric provides a clear and concise representation of the stability and reliability of software systems. Oobeya uses the health status of each deployment to calculate the CFR metric.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FIq4QEUhXQ6vtVllmaMIfQ.png" /><figcaption>Oobeya DORA Metrics — Change Failure Rate CFR</figcaption></figure><p>In Oobeya, each analyzed production deployment has a health status, which is either <strong>Success</strong> or <strong>Failure</strong>. Oobeya sets the health status of each deployment by using four methods: manual health status setting, API call, hotfix pattern detection, and tracking incidents from APM/Incident Management tools.</p><h4>1- Setting health status manually</h4><p>In this method, the health status of each deployment is set manually by a user. This method is useful when there is a need for verification, for example, when there is a complex deployment that involves multiple systems and applications or where you don’t have any mechanism to detect and track failures automatically by the tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hdjzQWRcLk1aGbmA8W_-mQ.png" /><figcaption>Setting deployment health status manually</figcaption></figure><h4>2- Setting health status via an API call</h4><p>Oobeya provides an API that can be used to set the health status of each deployment.</p><h4>3- Detecting hotfix naming patterns in the branch name, PR, and deployment title</h4><p>To identify hotfix deployments, Oobeya looks for naming patterns in the branch name, Pull Request title, and deployment title. Because hotfix deployments are used to fix critical production issues, Oobeya sets the health status of previous deployments to Failure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xsxLsIYniQwdFEBrwYLvpg.png" /><figcaption>Setting naming patterns</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0IA_EDbMCR6B_FGfsoSHaw.png" /><figcaption>Automatically detected Failure</figcaption></figure><h4>4- Tracking incidents from Application Performance / Incident Management tools</h4><p>Oobeya integrates with <a href="https://oobeya.io/integrations/">Application Performance Management (APM) and Incident Management tools</a> to track incidents in production. If these tools detect an incident in production, Oobeya sets the health status of the most recent deployment prior to the incident to Failure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lpUoOXNdUjzQWdaI1oSfZQ.png" /><figcaption>Oobeya — DORA Metrics Incident Source</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R74N6qJBZKPK3OqZnOV3xQ.png" /><figcaption>Automatically detected by tracking New Relic Incidents and Alerts</figcaption></figure><p><em>P.S. New Relic is ready to use, and DataDog, Sentry, Dynatrace, PagerDuty, OpsGenie, ServiceNow, and more are coming soon.</em></p><p>In addition to automatically and manually setting the health status of deployments and calculating the CFR, Oobeya also provides other three key DORA Metrics and detailed insights into each deployment. This includes information about the deployment time, deployment size (small, medium, large, and gigantic), contributors, and the link to the deployment pipeline. You can group multiple analyses to get a holistic view of DORA Metrics across your organization in the Oobeya Engineering Intelligence Platform.</p><p>In conclusion, detecting production failures is the most critical and challenging component of tracking DORA metrics. While it can be challenging, organizations can overcome these challenges by using the right tools and following best practices. By improving their ability to detect and resolve production failures, organizations can deliver value to customers more effectively and improve the overall performance of their DevOps practices.</p><h4>Resources</h4><ul><li>See the original post here: <a href="https://oobeya.io/blog/dora-metrics-tracking-how-to-effectively-detect-production-failures/">https://oobeya.io/blog/dora-metrics-tracking-how-to-effectively-detect-production-failures/</a></li><li>Check out the DORA research <a href="https://www.devops-research.com/research.html">here</a>.</li><li>How to measure DORA metrics accurately: <a href="https://oobeya.io/blog/how-to-measure-dora-metrics-accurately/">https://oobeya.io/blog/how-to-measure-dora-metrics-accurately/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcf14042964a" width="1" height="1" alt=""><hr><p><a href="https://blog.devops.dev/dora-metrics-tracking-how-to-effectively-detect-production-failures-calculate-change-failure-dcf14042964a">DORA Metrics Tracking: How to Effectively Detect Production Failures &amp; Calculate Change Failure…</a> was originally published in <a href="https://blog.devops.dev/">DevOps.dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Reduce Lead Time for Changes (Optimizing DORA Metrics)]]></title>
            <link>https://medium.com/better-programming/how-to-reduce-lead-time-for-changes-optimizing-dora-metrics-e97d47e11701?source=rss-cf1aed6d40d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e97d47e11701</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Emre Dundar]]></dc:creator>
            <pubDate>Tue, 15 Nov 2022 18:23:29 GMT</pubDate>
            <atom:updated>2022-11-15T18:23:29.984Z</atom:updated>
            <content:encoded><![CDATA[<h4>A guide to help teams make changes faster</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S7oM30zQyCw5s5F_w7L2lQ.png" /><figcaption>Optimizing software engineering processes | image by author</figcaption></figure><p>This article will look closely at one of the <a href="https://oobeya.io/dora-metrics-four-key/?utm_source=medium&amp;utm_content=lead-time">DORA metrics</a>, Lead Time For Changes (Change Lead Time), and how it can be reduced to optimize software development and delivery processes.</p><p>Metrics are a way of measuring something. They are used to understand the current situation, identify trends, predict future outcomes and make better decisions.</p><p>DORA metrics are the best way to measure and improve the health of the software delivery process.</p><h3>What Are DORA Metrics?</h3><p><a href="https://oobeya.io/dora-metrics-four-key/?utm_source=medium&amp;utm_content=lead-time">DORA metrics</a> have been widely adopted by organizations across the world. They are now the standard for measuring software value delivery.</p><p>DORA metrics are the way to go if you want to measure overall software delivery performance. But what are they?</p><p>Read my article on ‘How To Measure DORA Metrics Accurately’ <a href="https://oobeya.io/blog/how-to-measure-dora-metrics-accurately/">here</a>:</p><p><a href="https://oobeya.io/blog/how-to-measure-dora-metrics-accurately/">How to Measure DORA Metrics Accurately? | Oobeya Software Engineering Intelligence</a></p><h4>DORA Metrics (aka accelerate metrics and four key metrics)</h4><ol><li>Lead Time For Changes: The amount of time it takes a commit to get into production.</li><li>Deployment Frequency: How often an organization successfully releases to production. High-performing software teams release often and in small batches.</li><li>Change Failure Rate: The percentage of deployments causing a failure in production.</li><li>Time to Restore Service: How long it takes an organization to recover from a failure in production.</li></ol><p>Learn more from Google Cloud’s DORA research page: <a href="https://www.devops-research.com/research.html">https://www.devops-research.com/research.html</a></p><p>Organizations should measure and track all these four key metrics together to make better decisions and accelerate their value delivery performance.</p><p>You will probably make poor decisions if you only focus on one or two of these metrics. Assume you focused on increasing deployment frequency and decided to reduce testing efforts to make more production deployments in a shorter period. Your organization/product will likely lose stability and reliability due to your decision.</p><p>Focusing on four DORA metrics is the best and only thing you can do to create a high-performing organization.</p><p>But now we will talk about reducing the Lead Time For Changes (while taking care of all DORA metrics as well).</p><h3>What is the Lead Time For Changes?</h3><p>The interval between a code change and its release to the end users is considered Lead Time For Changes.</p><pre>Lead Time For Changes = [Production Deployment Time] - [First Commit Time of all changes]</pre><h4>The anatomy of the lead time</h4><p>The image below represents the anatomy of the Lead Time metric.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7r-mZIZvJu4hzIx9LVfKMw.png" /><figcaption>Lead Time Breakdown</figcaption></figure><p>Let’s dive into this breakdown to understand how we can reduce Lead Time For Changes.</p><h3>The Stages of Lead Time For Changes</h3><p>Lead Time For Changes mostly measures friction in the coding, code review, and CI/CD processes.</p><ol><li>Coding Time: The time elapsed between the First commit and PR opened.</li><li>Code Review Time: The time elapsed between the PR opened, and PR merged.</li><li>Waiting For Deploy: The time elapsed between the PR merged and the Deployment pipeline started.</li><li>Deployment Time: The time elapsed between the Deployment started, and Deployment finished successfully.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vdAsf0iEGB9EHO2lal4Ytw.png" /><figcaption><a href="https://oobeya.io/">https://oobeya.io</a> — DORA metrics Tracking Tool</figcaption></figure><h3>How To Reduce the Lead Time For Changes</h3><p>The best thing you can do to reduce Change Lead Time is to identify software development waste and bottlenecks.</p><p>Identifying waste and working on reducing it will automatically reduce the lead time and <a href="https://oobeya.io/optimize-software-engineering/?utm_source=medium&amp;utm_content=lead-time">increase the development teams’ productivity</a>!</p><p>Let’s see how we can optimize the stages of Lead Time for changes:</p><h4>Optimize coding time</h4><ul><li>Reduce rework in the coding cycles (but first measure Rework)</li><li>Work with small batches</li><li>Avoid unnecessarily complex solutions (needs technical and domain knowledge)</li><li>Avoid multitasking and context switching</li><li>Write clear requirements</li><li>Fasten the feedback cycle (always the most critical one)</li></ul><h4>Optimize code review time</h4><ul><li>Keep it small. If reviewers decide to battle with your changes, it will take too much time to review the PR.</li><li>Code faster. Break large features into small pieces and keep the coding time short for each pull request. See the problems earlier.</li><li>Review faster. Don’t let your code changes stale to prevent potential merge conflicts.</li><li>Create a Code Review Checklist</li><li>Automate what can be automated in the code review process. Automation is the first gatekeeper of code reviews.</li><li>Be ready to be reviewed. Review yourself before submitting. Give it a clear and descriptive title and write the best description.</li></ul><p>Check out my article on code reviews <a href="https://oobeya.io/blog/why-code-reviews-should-be-your-favorite-activity/">here</a>:</p><p><a href="https://oobeya.io/blog/why-code-reviews-should-be-your-favorite-activity/">Why Code Reviews Should Be Your Favorite Activity | Oobeya Software Engineering Intelligence</a></p><h4>Optimize waiting for deploy time</h4><ul><li>Automate your CI/CD process.</li><li>Increase your test automation coverage.</li><li>Create a strong set of smoke tests, regression tests, etc.</li><li>Eliminate manual approval processes.</li><li>Reduce pipeline queue time. Improve your CI/CD tooling performance and capability.</li></ul><h4>Optimize deployment time</h4><ul><li>Identify friction in the CI/CD process.</li><li>Reduce CI/CD pipeline duration.</li><li>Cache build dependencies.</li><li>Optimize container image size.</li><li>Check the network latency.</li><li>Optimize resources.</li><li>Review pipeline architecture.</li></ul><h3>“Yes, I know where I need to improve!”</h3><p>These magic words open the doors for effective and sustainable improvement.</p><p>If you want to improve the health and performance of your team, you should start by measuring metrics first. Then you’ll gain insights into what’s going on in your development and delivery cycles (by utilizing trends, benchmarks, patterns, anti-patterns, friction, risks, symptoms, and so on).</p><p>You will have the keys to optimizing system performance, team health, developer happiness, productivity, and organizational success once you start saying, ‘yes, I know where I need to improve.’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P9Dip6Dc4Bg-yA3MU_av-g.png" /><figcaption>Yes, I know where I need to improve! — <a href="https://oobeya.io/">https://oobeya.io</a></figcaption></figure><h3>Resources</h3><ul><li>See the original post here: <a href="https://oobeya.io/blog/how-to-reduce-lead-time-for-changes-dora-metrics/">https://oobeya.io/blog/how-to-reduce-lead-time-for-changes-dora-metrics/</a></li><li>Check out the DORA research <a href="https://www.devops-research.com/research.html">here</a>.</li><li>How to measure DORA metrics accurately: <a href="https://oobeya.io/blog/how-to-measure-dora-metrics-accurately/">https://oobeya.io/blog/how-to-measure-dora-metrics-accurately/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e97d47e11701" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/how-to-reduce-lead-time-for-changes-optimizing-dora-metrics-e97d47e11701">How To Reduce Lead Time for Changes (Optimizing DORA Metrics)</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stack Overflow 2022 Developer Survey: Where Is the Industry Heading?]]></title>
            <link>https://medium.com/better-programming/stack-overflow-2022-developer-survey-where-is-the-industry-heading-3cd4a0cd41f3?source=rss-cf1aed6d40d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/3cd4a0cd41f3</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Emre Dundar]]></dc:creator>
            <pubDate>Mon, 27 Jun 2022 18:04:06 GMT</pubDate>
            <atom:updated>2022-06-27T18:04:06.705Z</atom:updated>
            <content:encoded><![CDATA[<h4>See the highlights to understand where the industry is heading</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*riVoLooAIrqAHiHM" /><figcaption>Photo by <a href="https://unsplash.com/es/@wocintechchat?utm_source=medium&amp;utm_medium=referral">Christina @ wocintechchat.com</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The results of <a href="https://stackoverflow.com/">Stack Overflow</a>’s 2022 Developer Survey were recently published. The survey gathered information from 70,000 developers from various countries, roles, and technologies.</p><blockquote>“This report is based on a survey of 73,268 software developers from 180 countries around the world.” — Stack Overflow Developer Survey 2022</blockquote><p>Let’s look at my highlights from these survey results to understand where the industry is heading.</p><h3>1. Git Is the King: The Use of Git Is Increasing Year by Year</h3><blockquote>“No other technology is as widely used as Git. Especially among professional developers.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*QQ5KWakXiNFGhk-j6PE4vg.png" /><figcaption>What are the primary version control systems you use?</figcaption></figure><h3>2. Version Control Universe: GitHub, GitLab, Bitbucket, Azure DevOps</h3><p>If you’re building a product that integrates with version control platforms — that is what I did at <a href="https://oobeya.io/">Oobeya</a> — this is your universe: GitHub, GitLab, Bitbucket, and Azure DevOps. You need to cover these immediately because the entire software development industry lives in this universe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*eJMPU12eV1ZpYUIJqdHg4A.png" /><figcaption>What version control hosting service are you using?</figcaption></figure><h3>3. Docker Usage Is Increasing Year by Year</h3><p>Every developer should now be familiar with <a href="https://www.docker.com/">Docker</a>. Developers must first learn the concept and the technology behind it. Then, they must gain hands-on experience with it.</p><blockquote>“Last year, we saw Git as a fundamental tool to being a developer. This year it appears that Docker is becoming a similar fundamental tool for professional developers, increasing from 55% to 69%.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*CgKTibqjAbIsJgnSyvbAxg.png" /><figcaption>Which developer tools have you done extensive development work in over the past year, and which do you want to work in over the next year?</figcaption></figure><h3>4. Docker and Kubernetes Are in Every Developer’s Toolbox</h3><blockquote>“Docker and Kubernetes are in first and second place as the most loved and wanted tools.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*BbNOq69AoNgqCEi-sVHMRg.png" /><figcaption>Which developer tools have you done extensive development work in over the past year, and which do you want to work in over the next year?</figcaption></figure><h3>5. Communication Matters: Developers Love Slack</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*RN8RavC2To1KrUX7tt5RFw.png" /><figcaption>Which communication tools did you use regularly over the past year, and which do you want to work with over the next year?</figcaption></figure><p>But where is Discord?</p><p>I guess those who don’t like <a href="https://slack.com/">Slack</a> have already gone to <a href="https://discord.com/">Discord</a>, but Discord was not included in this survey. We have Slack and Microsoft Teamstons on <a href="https://oobeya.io/">Oobeya</a> in order to communicate with developers and teams. We also plan to add the Discord integration for dev teams using Oobeya.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/837/1*A3OCnurG1vRm4U9L1zcpTQ.png" /><figcaption>Which communication tools did you use regularly over the past year, and which do you want to work with over the next year?</figcaption></figure><h3>6. You Probably Have Knowledge Silos As Productivity Killers</h3><blockquote>“68% of respondents say they encounter a knowledge silo at least once a week. For people managers, 73% report encountering a knowledge silo at least once a week.”</blockquote><p>Engineering leaders must first change the culture of one-time communication (communicating need-to-know information once and quickly) to break down existing knowledge silos.</p><p>See the following tips for breaking down knowledge silos and increasing overall productivity:</p><ol><li>Create a clear and accurate documentation system</li><li>Practice pair programming</li><li>Perform better code reviews (See <a href="https://oobeya.io/blog/why-code-reviews-should-be-your-favorite-activity/">the code review tips here</a>)</li><li>Use Git analytics to identify knowledge silos in the development team. (<a href="https://oobeya.io/">Oobeya</a> provides you insights into existing knowledge silos in your code base and teams.)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*Io_h1QGnq1ogantK9eFyUQ.png" /><figcaption>How frequently do you experience each of the following?</figcaption></figure><blockquote>“62% of all respondents spend more than 30 minutes a day searching for answers or solutions to problems.</blockquote><blockquote>25% spending more than an hour each day. Regardless of being an independent contributor or people manager, this is time that could be spent learning or building.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*DcJSA8cgCAmIuyv1Uiz4ig.png" /><figcaption>On an average day, how much time do you typically spend searching for answers or solutions to problems you encounter at work?</figcaption></figure><blockquote>“For a team of 50 developers, the amount of time spent searching for answers/solutions adds up to between 333–651 hours of <em>time lost per week</em> across the entire team.”</blockquote><h3>7. Smaller Organizations Often Tend to Be in the Office</h3><blockquote>“85% of developers say their organizations are at least partially remote. Smaller organizations are most likely to be in-person, with 20% of 2–19 employee organizations in-person.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*fzsQodUcWWbtJHLkuMlVPw.png" /><figcaption>Which best describes your current work situation?</figcaption></figure><h3>8. Developer Experience: Processes, Tools, and Programs Within an Organization</h3><p>I believe software organizations today should invest more in improving the overall developer experience. Development teams should gain more visibility into their software development and delivery pipelines and strive to build a transparent and accountable working environment to increase developer experience and productivity.</p><blockquote>“Only 16% of organizations have Innersource initiatives.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*s292CcxC8h0DvZY5CAu_3g.png" /><figcaption>Developer experience</figcaption></figure><h3>Resources</h3><ul><li>See the original post here: <a href="https://oobeya.io/blog/stack-overflow-2022-developer-survey-where-is-the-industry-heading/">https://oobeya.io/blog/stack-overflow-2022-developer-survey-where-is-the-industry-heading/</a></li><li>Check out the complete Stack Overflow <a href="https://survey.stackoverflow.co/2022/">Survey Results here</a>!</li><li>Keywords to learn more: knowledge silos, developer experience, git analytics, innersource initiatives</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3cd4a0cd41f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/stack-overflow-2022-developer-survey-where-is-the-industry-heading-3cd4a0cd41f3">Stack Overflow 2022 Developer Survey: Where Is the Industry Heading?</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Measure DORA Metrics Accurately]]></title>
            <link>https://emredundar.medium.com/how-to-measure-dora-metrics-accurately-490d3fa22eef?source=rss-cf1aed6d40d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/490d3fa22eef</guid>
            <category><![CDATA[dora]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[accelerate]]></category>
            <category><![CDATA[four-key-metrics]]></category>
            <dc:creator><![CDATA[Emre Dundar]]></dc:creator>
            <pubDate>Wed, 18 May 2022 11:42:17 GMT</pubDate>
            <atom:updated>2022-06-30T09:59:35.464Z</atom:updated>
            <content:encoded><![CDATA[<p>DORA metrics are quite popular in the industry. However, working with them is extremely difficult. Let’s take a look at how your company can calculate and track DORA Metrics to gain complete visibility into complex delivery cycles.</p><h3>Why are DORA Metrics so popular and important to track for the industry?</h3><p>As software engineering organizations scale, fundamental software development and delivery processes become more and more complex. The number of tools used in the software delivery life cycle (SDLC) increases as processes become more sophisticated. Different teams within the company set up and run various delivery pipelines. During this process, visibility into the software development and delivery cycles is significantly reduced.</p><p><a href="https://www.devops-research.com/research.html">DORA (DevOps Research and Assessment)</a> sought to find a solution to this complexity and invisibility problem:</p><ul><li>How do you identify your organization’s elite performers?</li><li>What should low-performing teams focus on?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DW6swNpjXGGn4CWi.png" /><figcaption><a href="https://oobeya.io/dora-metrics/">Oobeya DORA Metrics</a></figcaption></figure><p>Once you begin to define and measure the metrics of the software delivery process, you will be able to improve them. Based on significant scientific research, DORA metrics empower engineering teams and leaders to improve their software development and delivery processes.</p><p>The DORA study’s approach attracted the interest of all engineering teams, from large-scale enterprises to small teams. Many engineering teams have tried to measure their DORA metrics by developing in-house tools since the beginning of the study. Because they could not adjust quickly enough to the changing and diversifying tools and methodologies within the company, in-house tools developed for specific processes have usually gone into junk. Many companies trying to measure DORA metrics with a ready-to-use product, on the other hand, struggled to locate a product that could fit their delivery pipeline and easily track accurate DORA metrics.</p><p>DORA metrics are quite popular in the industry. However, working with them is extremely difficult. Let’s talk about what are DORA Metrics basically and how you can track them accurately.</p><h3>What are DORA Metrics basically?</h3><h4>DORA Metrics (a.k.a. Accelerate Metrics &amp; Four Key Metrics)</h4><ol><li><strong>Lead Time For Changes: </strong>The amount of time it takes a commit to get into production.</li><li><strong>Deployment Frequency: </strong>How often an organization successfully releases to production. High-performing software teams release often and in small batches.</li><li><strong>Change Failure Rate: </strong>The percentage of deployments causing a failure in production.</li><li><strong>Time to Restore Service:</strong> How long it takes an organization to recover from a failure in production.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g0p5FBB8XJzmg7g7nEgQ6A.png" /><figcaption>State of DevOps 2021 — <a href="https://services.google.com/fh/files/misc/state-of-devops-2021.pdf">https://services.google.com/fh/files/misc/state-of-devops-2021.pdf</a></figcaption></figure><h3>Tracking DORA Metrics</h3><p><a href="https://oobeya.io/dora-metrics-four-key/"><strong><em>Oobeya</em></strong></a><strong><em> Deployment Analytics</em></strong> is an easy-to-use tool delivers accurate DORA metric results for all software development and DevOps teams. It analyzes the entire software development and delivery pipeline and calculates DORA metrics by connecting to various tools within the organization. You can connect both <em>Source Control, CI/CD, APM, Incident Management, and Issue Tracking</em> tools to calculate and track accurate DORA metrics with <em>Oobeya Deployment Analytics</em>.</p><p>No matter how you built your delivery cycle. It is easy to set up. For example, you can effortlessly calculate:</p><ul><li>DORA Metrics for GitLab x GitLab CI</li><li>DORA Metrics for GitHub x Jenkins</li><li>DORA Metrics for GitHub x GitHub Actions</li><li>DORA Metrics for GitHub x AzureDevOps Releases</li><li>DORA Metrics for GitLab x Jenkins</li><li>DORA Metrics for Azure Repos x AzureDevOps Releases</li><li>DORA Metrics for Azure Repos x Jenkins</li><li>DORA Metrics for Bitbucket Server/Cloud x Jenkins</li></ul><p>Watch and see how it is effortless measuring DORA Metrics in Oobeya:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FEYE4e1gTs80%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DEYE4e1gTs80&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FEYE4e1gTs80%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/51d215e3eff3c9c22904cbbb50296374/href">https://medium.com/media/51d215e3eff3c9c22904cbbb50296374/href</a></iframe><blockquote>Oobeya Free Edition: <a href="https://oobeya.io/dora-metrics/">https://oobeya.io/dora-metrics/</a></blockquote><p>Oobeya analyzes all <strong>commits, pull requests, </strong>and<strong> deployment pipelines</strong> and generates detailed <em>historical</em> reports of DORA metrics. Oobeya Deployment Analytics (DORA) Report includes the following features and <em>more</em>:</p><ul><li><strong>Lead Time For Changes</strong> (average time &amp; breakdown &amp; DORA badge)</li><li><strong>Deployment Frequency </strong>(average &amp; chart &amp; DORA badge)</li><li><strong>Change Failure Rate </strong>(average &amp; DORA badge)</li><li><strong>Time to Restore Service</strong> / Mean Time to Recovery (MTTR) (average time &amp; DORA badge)</li><li><strong>List of deployments </strong>during the selected period (breakdown, lead time, contributors…)</li><li><strong>Deploy size </strong>for each deployment (small, medium, large, gigantic)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o-jAmdX6wD9Jjy4i" /><figcaption>Oobeya Deployment Analytics Report — DORA Metrics</figcaption></figure><p><strong>“Lead Time For Changes” breakdown</strong> includes four significant steps such as <em>coding time, code review time, waiting for deploy time, </em>and<em> deployment time</em>. <strong><em>Visualizing</em></strong> these steps <strong>helps you pinpoint bottlenecks</strong> in your software development and delivery cycle. 👇</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vfosqxyvkApiJjW6lIHXiQ.png" /><figcaption>Oobeya — Lead Time For Changes Breakdown</figcaption></figure><p>You can set your own <strong><em>goals</em></strong> for these steps👇</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*T34wtmJXEygOJrcV" /><figcaption>Set goals for Deployment Analytics (DORA)</figcaption></figure><h3>Additional Resources</h3><ul><li>Oobeya DORA Metrics: <a href="https://oobeya.io/dora-metrics/">https://oobeya.io/dora-metrics/</a></li><li>DORA research program: <a href="https://www.devops-research.com/research.html">https://www.devops-research.com/research.html</a></li><li>DORA DevOps Quick Check: <a href="https://www.devops-research.com/quickcheck.html">https://www.devops-research.com/quickcheck.html</a></li><li>State of DevOps: <a href="https://cloud.google.com/blog/products/devops-sre/announcing-dora-2021-accelerate-state-of-devops-report">https://cloud.google.com/blog/products/devops-sre/announcing-dora-2021-accelerate-state-of-devops-report</a></li><li>Accelerate. <strong>Authors:</strong> Nicole Forsgren, Jez Humble, and Gene Kim: <a href="https://itrevolution.com/book/accelerate/">https://itrevolution.com/book/accelerate/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=490d3fa22eef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mühendislikten Ürün Yöneticiliğine — Kişisel Deneyim Paylaşımı]]></title>
            <link>https://emredundar.medium.com/m%C3%BChendislikten-%C3%BCr%C3%BCn-y%C3%B6neticili%C4%9Fine-ki%C5%9Fisel-deneyim-payla%C5%9F%C4%B1m%C4%B1-dc1ab095db28?source=rss-cf1aed6d40d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc1ab095db28</guid>
            <category><![CDATA[urun-yonetimi]]></category>
            <category><![CDATA[ürün-geliştirme]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Emre Dundar]]></dc:creator>
            <pubDate>Fri, 11 Mar 2022 05:31:07 GMT</pubDate>
            <atom:updated>2022-03-11T05:54:49.952Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mühendislikten Ürün Yöneticiliğine — Kişisel Deneyim Paylaşımı</h3><p>2018 yılında verdiğim bir kararla Ericsson’daki işimden ayrılarak konfor alanımın dışına çıktım ve geleceğini öngöremediğim bir maceraya atıldım.</p><p>Bahsettiğim maceraya atılmadan önce plazadaki ofis masasında büyük yazılım sistemlerinin / organizasyonlarının bir parçasını doğru bir şekilde işletmekten sorumlu olan bir mühendistim. Kariyerimin başında büyük bir bankanın yazılım organizasyonunda (Softtech — 600+ yazılım geliştirici ile) yazılım geliştirme yaşam döngüsünde (SDLC) bulunan araç, platform ve süreçlerin bakım, yönetim ve iyileştirilmesinden sorumlu olarak çalıştım. Üç yılı aşkın bir süre büyük ölçekli ve farklı teknolojiler kullanan dinamik bir yazılım organizasyonun içerisinde önemli deneyimler edindim. Yeni süreçler tasarladık, yeni araçlar seçtik, konumlandırdık. Yazılım geliştirme ve teslimatının daha kaliteli ve hızlı değer üretebilmesini sağladık.</p><p>Üç yılın ardından global bir şirkette (Ericsson) global bir ürünün sürüm yönetim ekibine katıldım. Farklı paydaşlarla global bir ürünün geliştirme, test, sürüm yönetimi ve kurulum süreçleri üzerine çalıştım. Daha eski bir sistemle uğraşmak zorunda kalsam da bu yolculukta ilk kez kıtalararası çalışma ve bir ürünün tüm süreçlerini izleme deneyimi elde etmiş oldum. Yine büyük ölçekli kurumsal bir yazılım organizasyonunun tüm iç dinamiklerini yakından deneyimleme fırsatım oldu.</p><p>Ofis masasında büyük organizasyonların büyük sistemlerinin bir parçasını yönetirken geçen 4 yılın ardından artık farklı bir işe girişme zamanının geldiğini hissetmeye başlamıştım. Bu noktada Testinium’dan gelen teklif ile kendimi şu soruyu sorarken buldum:</p><blockquote>4 yıldır yazılım geliştiren organizasyonlarda SDLC sistemleri yönetirken kendi yaşadığım acıları (devops) ve arkadaşlarımın (yazılım geliştirici, takım lideri, proje lideri, mühendislik yöneticisi, vb.) yaşadığı acıları iyileştirebilecek bir ürün geliştirebilir miyiz?</blockquote><p>Buna yanıtım <em>evet </em>oldu ve kariyerimin dönüşümü bu noktada başladı. <a href="https://testinium.com/">Testinium</a>’dan çıkan tüm B2B ürünler şu benzer stratejiyi izlemişler: <em>Önce fikri servis olarak sağlayalım, pazardan geri bildirim toplayalım, deneyim kazanalım, ihtiyacı analiz edelim ve pazarda bir boşluk tespit edersek bu açığı ürün ile kapatalım.</em> Bu strateji benim yürüdüğüm yolu şekillendiren esas yaklaşım oldu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pa7mgBiJG5JnSHBI0d5OZg.png" /><figcaption>Mühendislikten Ürün Yöneticiliğine</figcaption></figure><h3>Yeni deneyim ve rol: Teknik Danışmanlık</h3><p>Testinium’a gelmemle birlikte daha önce düşünmediğim bir role sert bir geçiş yapmış oldum. Burada önce teknik danışman olarak görev aldım. Farklı sektörlerde (havacılık, otomotiv, sigortacılık, e-ticaret, finans…) yazılım geliştiren organizasyonlara SDLC pratikleri, kod kalitesi ve DevOps alanında teknik danışmanlık sağladım. Hedeflediğimiz ürün için farklı yapıdaki organizasyonları analiz etme, ihtiyaçlarını anlama ve buna çözüm üretme fırsatı buldum ve bu bakışla geçen iki ayın sonunda ürünümüzün ilk <strong>prototipini </strong>geliştirmiş oldum. Yazılım geliştirici olmamama rağmen, kendimi kurumsal organizasyonlarda çalışan basit bir web uygulaması geliştirmiş ve ürün entegrasyonlarını müşterilerin ihtiyacına göre sürekli artırırken bulmuştum. Takip eden üç ayın sonunda prototip görevini tamamladı ve biz Testinium içerisinde yeni ürün geliştirme takımımızı kurmaya karar verdik.</p><h3>Yeni başlangıç ve rol: Product Owner</h3><p>İlk kez bir yazılım ekibi ile ürün geliştirmek için çalışmaya başlamıştım. Bu sefer kendimi bir anda mockup araçlarında ekranlar tasarlarken, pazar araştırması yaparken ve kullanıcı hikayeleri yazarken buldum.</p><p>Bir ürün ekibini yönetmek ve sıfırdan bir ürün geliştirmek benim için edinmem gereken pek çok yetkinlik ve çözmem gereken pek çok sorun barındırıyordu. Okudum, topluluklara katıldım, denedim, yaptım, başarsız oldum, bir daha denedim… Bu süreçte kendimi önce “Product Owner” olarak konumlandırıp yeni yetkinlikler edinmeye başladım. Paralelde ürün pazarlamak, ürün satmak, ürün kurmak, müşteri ile ilişki kurmak, destek sağlamak gibi pek çok işi de yürütüyordum.</p><p>Baştan sona bir ürünle yolculuk etmek ve her adımı deneyimlemek o zamanlar çok yorucu olsa da bugün dönüp bakınca bunun bana çok şey kattığını görebiliyorum.</p><h3>Bir adım daha ileri: Ürün Yöneticiliği</h3><p>Ürün artık belirli bir olgunluğa ulaştıktan ve ben de ürün yönetiminin kitabını açtıktan sonra işler biraz daha profesyonel hale gelmeye başladı. Hali hazırda yaptığım işleri ürün yönetimi çerçevesi altında yeniden konumlandırdık ve artık ekibi genişletip işleri doğru kaynaklara adreslemeye başladık. Burada edinilen yeni deneyimler <em>ekip yönetimi, delegasyon, paydaş yönetimi ve daha fazlası</em>… Gerçek bir ürün ekibi olarak çalışmaya başladık. Ürün vizyonunu ve stratejisini güncelledik, global pazarda konumlandık, yeniden <a href="https://medium.com/testinium/announcement-qa-dashboard-is-now-oobeya-6fdc83ff140d">markalaştık</a> (<a href="https://oobeya.io/">Oobeya</a>). Y<em>azılım geliştirme, kalite güvence, kurulum, destek, müşteri başarımı, satış, pazarlama, iş geliştirme ve ürün yönetimi</em>… günün sonunda herkes kendi alanında, paydaşları ile birlikte, tek bir amaç için çalışır hale geldi.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ig53HRzKfBN87BEu19dOtQ.jpeg" /><figcaption>Oobeya Ekibi</figcaption></figure><h3>Geleceğe hazırlık</h3><p>Kendi yolumda öğrendiğim en önemli derslerden biri şu oldu: B2B <em>(Business-to-business)</em> bir ürün geliştirmek sabır ister, başarmak ve başarının meyvelerini toplamak da. Biz sabır gerektiren kısımları başarılı bir şekilde aştık ve sabırsızlıkla ilerlememiz gereken güzel ama zorlu bir zamana geldik.</p><p>Geldiğimiz noktada -yaklaşık 1000 kişilik bir teknoloji organizasyonunun çatısı altında- kendi kararlarını alabilen, kendi ekibini oluşturup yöneten dinamik bir yapıya dönüşme kararını aldık. Şimdi <a href="https://oobeya.io/">Oobeya</a> ekibi ile atacağımız büyük adımlara hazırlanıyoruz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t_rY43tPYuLBB9V6YfkyZg.png" /><figcaption><em>Oobeya:</em> <a href="https://oobeya.io/">https://oobeya.io</a></figcaption></figure><h4>Hikayenin parçası olmak</h4><p>Bir konuşmada şunu söylemiştim, yazılı olarak da kalsın isterim:</p><p>İnsan atomlardan değil hikayelerden oluşur. Bizim ürünümüz de 1&#39;ler ve 0&#39;lardan değil hikayelerden oluşuyor. İçinde başarı hikayeleri kadar başarısızlıklar da var. İşte bu yazıda anlatılanlar hikayelerin sadece dağınık parçaları. Gelecek hikayelere dahil olmak isteyenler için de yerimiz var: <a href="https://www.linkedin.com/company/oobeya/jobs">https://www.linkedin.com/company/oobeya/jobs</a></p><p>Bu yazıda kariyer yolumun nasıl şekillendiğini yüzeysel bir şekilde aktardım. Süreç içerisinde her bir adımda karşılaştığım zorluklara, bunlara nasıl çözüm bulduğuma, verilen stratejik kararlara ve sonuçlarına hiç değinmedim, çünkü bu adımlarda yaşananlar ayrı yazılar olur, belki bir gün yazılır.</p><p><em>Linkedin:</em> <a href="https://www.linkedin.com/in/emredundar/">https://www.linkedin.com/in/emredundar</a><br><em>Twitter:</em> <a href="https://twitter.com/emredundar_e">https://twitter.com/emredundar_e</a><br><em>Oobeya: </em><a href="https://www.linkedin.com/company/oobeya/">https://www.linkedin.com/company/oobeya/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc1ab095db28" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>