<?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 Release Management Apps on Medium]]></title>
        <description><![CDATA[Stories by Release Management Apps on Medium]]></description>
        <link>https://medium.com/@releasemanagement?source=rss-66f5f60b52d9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WTjamq0zAhXUyCGLXks5KA.png</url>
            <title>Stories by Release Management Apps on Medium</title>
            <link>https://medium.com/@releasemanagement?source=rss-66f5f60b52d9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 16:28:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@releasemanagement/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[Release Management in Jira: A Practitioner’s Guide]]></title>
            <link>https://medium.com/@releasemanagement/release-management-in-jira-c00e146697f3?source=rss-66f5f60b52d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/c00e146697f3</guid>
            <category><![CDATA[atlassian]]></category>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[release-management]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Release Management Apps]]></dc:creator>
            <pubDate>Wed, 26 Aug 2026 15:32:31 GMT</pubDate>
            <atom:updated>2026-08-26T15:40:19.025Z</atom:updated>
            <content:encoded><![CDATA[<p>Release management in Jira is available almost from the very beginning, and the hard parts have changed little over the past decade. The tooling has grown; the underlying problem, getting the right work tested and approved into production on a date other people are counting on, has not. At Release Management Apps we build the release management app this guide keeps circling back to, so read the product mentions as disclosed and focus on the platform underneath them.</p><p><strong>TL;DR</strong></p><ul><li>Jira manages releases natively through versions: a version is a release, the Fix version field sets its scope, and the Release Hub, Release Burndown, and development integrations track progress within a single project.</li><li>At scale it runs out where releases cross projects, where dependencies hide at the release level, and where “Done” has to mean tested, documented, and approved rather than merely coded.</li><li>Release management under audit is the part Jira leaves thinnest: enforced approval gates, a reproducible audit trail, change control, and evidence-grade release documentation are not built in.</li><li>The practical path is to keep Jira as the system of record and add a release layer over it for cross-project scope, gates, and evidence.</li></ul><h3>What release management in Jira actually is</h3><p>Strip away the tooling and release management is a coordination job. Someone has to decide which work goes into a given release, confirm it is ready, and get it in front of users on a date other people are counting on. Jira models the release itself as a <strong>version</strong>. In practice the two words are used interchangeably: a version is a release. A version carries a name, a description, optional start and release dates, and can name a <strong>Driver</strong>, which is Jira’s term for the person who owns the release.</p><p>The scope of that release is defined by work. The <strong>Fix version</strong> field assigns a work item to a version, and the set of work items carrying that Fix version is the release scope. Change what is in scope and you change the Fix version assignments; that is the whole mechanism. Around it sits the cycle every release manager knows: agree the scope, hold it steady long enough to build and test against it, then ship. The dates give the cycle its shape, the scope gives it its content, and the Fix version field ties the two together inside Jira.</p><p>Fix version has a counterpart, and the two are easy to confuse.<strong> Affects version</strong> points the other way: it records the version in which a bug was found, not the one it will be fixed in. Only the Fix version field defines release scope. Confusing the two is one of the more common reasons a release’s scope looks wrong on the Release Hub.</p><p>It is worth separating two jobs that often blur together. A developer’s job ends when the work item is coded and merged. The release manager’s job begins there and runs until the release is out, verified, and documented. Those are different responsibilities with different definitions of done, and most late releases live in the gap between them: a developer can be finished while the release is nowhere near ready. Jira gives you the raw objects to manage this. What it does not give you, out of the box, is a way to make “ready” mean the same thing to everyone who has to sign off on it.</p><h3>What Jira gives you out of the box</h3><p>Jira ships with more release tooling than it usually gets credit for, and any honest guide should say so before selling anything on top of it. Most single-team release work can be done with the native objects alone, and for a while that is the right call.</p><p>The <strong>Release Hub</strong>, reached through the Releases tab of a project, is the working surface. It lists each version with a status of Unreleased, Released, or Archived, a progress bar against the work in scope, and filters. When you mark a version as released, Jira checks the work under it and raises <strong>warnings</strong> for anything marked Done that is not actually shippable: an open pull request, unreviewed code, a failed build. On Jira Cloud, you can also name <strong>approvers</strong> who approve or decline the release on that page, which is the first native hint of a governance layer.</p><p>The reporting is real, too. The <strong>Release Burndown</strong> shows completed against remaining work for a version, provided your items carry estimates. The <strong>development integrations</strong> pull more than code state onto the work item: commit, branch, pull-request, build, and deployment status, and — depending on what you connect — feature-flag state and security vulnerabilities as well. All of it surfaces on the work item and in the Release Hub, so the state of the code sits next to the state of the plan. And <strong>release notes</strong> can be generated automatically from the work items in a version, grouped by type and regenerated from current state each time, with Rovo able to assist on the writing.</p><figure><img alt="How to create automated release notes? Choose space, work types and included fields." src="https://cdn-images-1.medium.com/max/405/1*00jHBLYEGMI1kEO9GH45HQ.png" /></figure><figure><img alt="Automated release notes." src="https://cdn-images-1.medium.com/max/648/1*imLVLYqX8bc9Cpnlaz-7nw.png" /></figure><p>The table below is the fair version of what you get, and where each piece stops.</p><figure><img alt="Native Jira release management: what each capability covers, and where it stops. Cross-project releases need Jira Plans on Cloud Premium or Enterprise; Jira Align is a separately licensed product." src="https://cdn-images-1.medium.com/max/1024/1*NMBwiRXBKH0KPtg1xVGj2Q.png" /></figure><h3>The release lifecycle, stage by stage</h3><p>A release moves through four stages, and the release manager’s attention shifts at each one. The stages are familiar. What is less obvious is where the risk sits, and it is rarely where the activity is loudest.</p><p><strong>Plan.</strong> Scope is agreed here, and the agreement is the one thing Jira does not keep. Assigning a Fix version records what is in scope right now; it records nothing about what was agreed at the outset, by whom, or when. Without that baseline there is nothing to compare against, so the current scope always looks like the intended scope. Items get added and dropped over the following weeks and the board stays green throughout — scope creep is noticed by its effects, a missed date or a surprise in testing, rather than at the moment it happens. It is also why the first question an incident review or an auditor asks, was this in the approved scope, has no native answer.</p><p><strong>Build.</strong> The work is done, merged, and moved toward Done. Native Jira is at its strongest here: CI/CD integrations show build and pull-request state against each work item, and the Release Hub’s progress bar moves as items close. The risk in this stage is quiet. A dependency on another team’s work item can be blocking your release without anyone watching that item, because Jira does not surface dependencies at the release level. Everything looks green until the one red item that was never in your view slips the date. The same blind spot exists one level up. A release can be waiting on another release — a shared platform version, an API upgrade, a hardware milestone — and Jira has no way to express a dependency between two releases at all.</p><p><strong>Test.</strong> This is where “Done” and “ready” separate. A work item marked Done has been tested by the team that built it, in isolation. What has not been tested is the release: how the changed components behave together, and whether the non-functional requirements — performance, security, compatibility, upgrade path — still hold at the solution level. That verification only exists above the work-item level, and Jira has no object at that level to hold it. Native warnings catch the obvious code-level cases, an open pull request or a failed build, but they check whether code is shippable, not whether the release has been verified as a whole. Someone has to make that judgment and record it, and native Jira has no field that means “verified and approved for release.”</p><p><strong>Release and deploy.</strong> The version is marked released, notes are generated, and the work goes to users. On Cloud you can require an approver to approve or decline at this point, which is a real gate, if a single one. The risk here is the rollout: putting software into an environment, in the right order, with a way back if it fails. Jira tracks the release object well. It does not track the procedure that puts the release into production, and it holds no inventory of the environments that procedure touches. And deploying is not the same as releasing. An artifact can sit in production with its functionality dark behind a feature flag, so a release is only complete once the right flags are enabled for the right audiences. Jira tracks neither the rollout procedure nor the flag state that decides whether users actually got the release.</p><p>Read across the four stages and the pattern is clear. Jira is excellent at the state of the work and thin on the governance around it: who decided, who approved, what was verified, and where it was deployed. That thinness is manageable for one team and one project. It compounds at scale.</p><h3>Where native Jira runs out</h3><p>Everything above holds for one team shipping within a single project. Add projects, teams, and the obligation to prove what happened, and the native model strains in five specific places. The right frame is not any single feature you are missing; it is <strong>release orchestration</strong>: coordinating one release across the projects, dependencies, environments, and approvals a real release spans.</p><p><strong>One release across many projects.</strong> Versions are project-scoped by design. There is no native global release object that several projects share. Jira Plans offers cross-project releases, but only on Cloud Premium and Enterprise, and it stops short of a single release you can govern as one thing. Outside that, a release spanning many projects becomes many separate versions kept in sync by hand, which drift the moment someone forgets to update one. This is the gap we built our Release Management app around first: a single Jira-native release view across teams and projects that is one real release object, not a set of synced duplicates.</p><p><strong>Dependencies at the release level.</strong> Jira models dependencies between individual work items. It does not roll them up to the release, so the question that matters most to a release manager, is anything my release depends on at risk, has no native view. One blocked item can slip a release with little warning, and the surprise usually arrives late. Dependency tracking at the release level is the difference between managing a release and reacting to one.</p><p><strong>Environment inventory and rollout tracking.</strong> Jira knows the release exists. It does not know which environments it has to reach, in what order, or whether the rollout procedure ran. There is no native inventory of test and production environments, and no native record of the steps that put a release into each. For anyone whose releases move through more than a couple of environments, that record lives in a spreadsheet or a runbook no one fully trusts by the third release.</p><p><strong>Release-readiness and approval gates.</strong> Native warnings check code shippability, and Cloud approvers give you one approval step. Neither gives you configurable gates: a release cannot proceed until testing is signed off, documentation is attached, and the named approver has cleared it. “Done” work items do not prove tested, documented, or approved. We handle that with approval workflows and release gates that sit on the release itself.</p><p><strong>Audit trail and release documentation.</strong> Jira records changes on individual work items. It does not assemble, at the release level, a durable record of who approved what and when, alongside the documentation that release produced. That record is optional right up until the moment it is not, and by then it often cannot be reconstructed. If your releases ship under any kind of external scrutiny, the next section is the one to read.</p><p>None of this means native Jira is wrong. It means Jira is a system of record for work, and release orchestration is a layer that sits over it. For the specifics, our <a href="https://marketplace.atlassian.com/apps/1221946/release-management-workflows-calendar-roadmaps-for-jira?hosting=cloud&amp;tab=overview&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=rm-jira-guide&amp;utm_content=body-marketplace">Release Management for Jira product page</a> goes deeper than a guide should.</p><h3>Release management when you are under audit</h3><p>Here is the part most Jira release guides skip, and it is the part that decides whether a release process survives contact with a regulator, an external auditor, or a serious incident review. If your releases ship under audit, the interesting question is not whether you shipped but whether you can prove how you shipped, months later, without anyone’s memory involved. Native Jira leaves this thinnest of all, and the reason is structural: Jira records the state of work, not the governance around a release as evidence.</p><p>Start with approval gates, because they are the most misunderstood. In an audited process an approval is a <strong>control</strong>, not a courtesy. The point is not that someone clicked approve; the point is that the release could not have proceeded until the right person did — that the person had the authority, and that the click is tied to the exact scope they were approving. A single approve-or-decline step, which is what Cloud offers natively, records an outcome. It does not enforce a sequence, and it does not bind the approval to a frozen scope. To an auditor, an outcome without a sequence is a weak answer; gates that block progress until each condition is met are the strong one, and they are worth building deliberately rather than approximating with statuses and hope.</p><p>Then the audit trail, which is where reproducibility lives. The test is simple. Pick a release from a year ago and ask: who approved it, against what scope, on what date, with what testing evidence attached, and what changed between the approved scope and what actually shipped. If answering that means archaeology across work-item histories, chat threads, and someone’s inbox, the trail is not audit-ready. A real audit trail assembles those facts at the release level and holds them, so the answer is a record you retrieve rather than a story you reconstruct. Trust is not earned by demos here; it is earned by being able to point to specific evidence when someone asks.</p><p>Change control is the same idea worn as process. Many regulated organizations run a change-advisory step before a release reaches production. The instinct is to run it outside Jira, in a separate tool or a meeting whose output lives in minutes no one reads. It works far better as a workflow inside Jira, where the change request, its review, and its outcome are tracked against the same release the team already works in. The CAB does not need its own island. It needs to be a stage in the release’s own workflow, with the decision recorded where the release lives.</p><p>Documentation is the quiet one, and often the most valuable. A release produces evidence whether or not anyone captures it: what was in scope, what was tested, what was approved, and what shipped. Release notes generated from the work items in a version are the visible slice. The larger prize is release documentation assembled as an evidence base a regulator or auditor can actually read: the scope, the approvals, the test results, and the deployment record, gathered per release rather than scattered across systems. Information radiators, not refrigerators. Evidence no one can find is evidence that does not exist when it matters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*91Rrt8rE-b3IajZTXYoLJQ.png" /></figure><p>The shape of this problem changes with the situation, though the substance does not. When you are scaling across many autonomous teams, the hard part is keeping one release’s evidence coherent while everyone works in their own project. When you are delivering under a formal audit regime, the hard part is reproducibility on demand, long after the fact. When a single release rolls out across dozens of client environments, the hard part is proving the same controlled procedure ran in each one. And when hardware and software timelines have to line up, the hard part is a release record that stays honest across two different delivery cadences. Different situations, one requirement underneath: the release has to account for itself.</p><p>This governance layer is the point of the product for us, not a feature bolted to the side. Approval workflows and release gates, a release-level audit trail of who approved what and when, change control <a href="https://releasemanagement.app/case-study-how-an-iot-manufacturer-coordinates-platform-sprints-device-firmware-and-multi-year-product-generations-all-inside-jira/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=rm-jira-guide&amp;utm_content=body-change-control">inside the Jira workflow</a>, and auto-generated release documentation are what turn a release from an event into a record.</p><p>One factual note belongs here rather than in a boast: our own operation carries SOC 2 Type II, the same evidence-driven discipline described above applied to ourselves. If audited delivery is your reality, our <a href="https://marketplace.atlassian.com/apps/1221946/release-management-workflows-calendar-roadmaps-for-jira?hosting=cloud&amp;tab=overview&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=rm-jira-guide&amp;utm_content=body-marketplace">solutions page for regulated and audited delivery</a> is the next stop.</p><h3>Best practices that hold up</h3><p>None of the following is exotic. These are the habits that separate release processes that scale from ones that quietly depend on one person remembering everything.</p><p><strong>Make “done” mean done.</strong> Agree a definition of done for a release, not just for a work item, and write it down. A release is done when it is coded, tested, documented, approved, and deployed, with each step recorded. The most common dysfunction we see is a team treating a work item’s Done status as release readiness. They are not the same thing, and the gap is where late failures live.</p><p><strong>Set a scope cutoff and defend it.</strong> Pick a date after which the release scope is frozen, and treat later changes as exceptions that require explicit approval rather than as normal traffic. Call it a change cutoff, a code freeze, or a feature freeze; the label matters less than the discipline. Scope that stays open until the last day cannot be tested as a whole, because the whole keeps moving. A cutoff is not bureaucracy. It is what makes a release testable.</p><p><strong>Standardize the repeatable parts, then automate them.</strong> Most releases run the same set of tasks: cut the version, notify stakeholders, generate notes, run the rollout steps, and close the release. Native Jira has no template for the release-related task set that repeats every cycle. Automation can create work items on a schedule, but there is no reusable release checklist that comes with each version, so these tasks are cloned or recreated by hand each time, which is slow and error-prone. Define the standard set once, and automate what can be automated. Time savings in the assembly of a release are real, but the larger gain is that a standardized release runs the same way every time, which is what makes it auditable.</p><p><strong>Use workflow statuses that tell you something.</strong> To-do, In-progress, and Done describe a task. They say almost nothing about a release. Granular statuses that reflect the stages a work item actually passes through, such as in review, in test, ready for release, and released, turn a status field into information a release manager can act on. A status that only ever reads Done is not telling you anything you can steer by.</p><p><strong>Name a release owner.</strong> Every release needs one person accountable for it reaching production in good order, and Jira’s Driver field exists for exactly this. Diffuse ownership is how releases fall between teams. A named owner is not about blame; it is about someone whose job it is to see the whole release, not just their team’s slice of it.</p><p>Adopt these and much of what native Jira leaves thin becomes manageable through discipline alone. The rest, the cross-project scope and the audit-grade evidence, is where a dedicated release layer earns its place.</p><h3>FAQ</h3><p><strong>Is Jira a release management tool?</strong></p><p>Jira has native release management built in through versions, the Fix version field, the Release Hub, Release Burndown, CI/CD integrations, and auto-generated release notes. For a single team releasing within a single project, that is often enough. On its own it is not a release orchestration tool: it does not manage one release across many projects, track dependencies at the release level, or assemble an audit-ready record of approvals and evidence. Whether native Jira is enough depends entirely on the scale and the scrutiny your releases run under.</p><p><strong>What is the difference between Fix version and Affects version?</strong> Fix version is forward-looking: it marks the version a work item is being delivered in, and the set of items sharing a Fix version defines a release’s scope. Affects version is backward-looking: it records the version in which a bug was found. You scope and plan releases with Fix version, and you use Affects version to describe where a problem appeared.</p><p><strong>Do I need Jira Premium for release management?</strong> For most of it, no. Versions, the Fix version field, the Release Hub, CI/CD integrations, Release Burndown, and release notes (including Rovo-assisted notes) all work on Jira Standard. The main capability gated behind Premium and Enterprise is cross-project releases, which live within Jira Plans. If your releases stay within one project, Standard covers the release basics.</p><p><strong>How do I track release progress in Jira?</strong> Open the Releases tab to reach the Release Hub, select the version, and read the progress bar against the work items in scope. Add the Release Burndown for completed against remaining work, provided your items carry estimates, and use CI/CD integrations so build and deployment status sits alongside the work. Warnings on the release page flag Done items that are not actually shippable.</p><p><strong>How do I make release management in Jira audit-ready?</strong> Native Jira records the state of work but not the governance around a release, so audit-readiness has to be added deliberately. In practice that means enforced approval gates rather than a single approve step, a release-level audit trail of who approved what and when, change control run as a stage in the Jira workflow, and release documentation assembled as evidence a regulator can read. The test is whether you can reconstruct a year-old release, its scope, and its approvals from a record rather than from memory. If you cannot, that is the gap to close.</p><h3>Where this leaves you</h3><p>Native Jira is a genuinely good system of record for release work, and for a single team within a single project it may be all you need. The strain shows up predictably: when releases cross projects, when dependencies hide at the release level, and above all when someone has to prove, later and from a record, how a release was approved and shipped. That last case is the one native Jira serves worst, and the one where the cost of getting it wrong is highest.</p><p>So the question worth sitting with is not whether Jira can manage your releases, but whether it can account for them under the scrutiny yours actually face. If the honest answer is “not yet,” that is where a release layer over Jira stops being optional. That is the layer we build; our <a href="https://releasemanagement.app/solutions/release-portfolio-management/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=rm-jira-guide&amp;utm_content=closing-cta">Release Management for Jira product page</a> and <a href="https://releasemanagement.app/solutions/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=rm-jira-guide&amp;utm_content=body-solutions">solutions page for regulated and audited delivery</a> are where to look next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c00e146697f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Agents in Release Management: From Automation to Autonomy]]></title>
            <link>https://medium.com/@releasemanagement/ai-agents-in-release-management-from-automation-to-autonomy-ea8e6a799a76?source=rss-66f5f60b52d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea8e6a799a76</guid>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[release-management]]></category>
            <dc:creator><![CDATA[Release Management Apps]]></dc:creator>
            <pubDate>Wed, 08 Jul 2026 14:46:51 GMT</pubDate>
            <atom:updated>2026-07-08T14:46:51.262Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By Yuri Kudyn, Co-founder, Release Management Apps</em></p><p><strong><em>Disclosure: </em></strong><em>I am a co-founder at Release Management Apps, an Atlassian Gold Marketplace Partner. We have been building Jira-native release tooling since 2018. This article reflects our findings so far and where the industry is moving, taking into account modern trends.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rpja8ukRd42eRi4gjhUyHA.png" /></figure><p>The release management market is projected to reach $3.51 billion in 2026 and $5.72 billion by 2030. The core challenges enterprise teams face have changed little over the past decade. Dependencies are often missed. Compliance evidence is still assembled by hand. Release managers still spend hours answering questions that repeat every week.</p><p>AI agents are starting to change that equation. The path from an interesting demo to trusted in production runs through a discipline where a single mistake can break production, delay an entire release train, or trigger a regulatory finding. Caution is warranted for good reasons.</p><p>What follows is a walkthrough of four things. What enterprise release management actually demands. Why the standard tooling, including most DevOps release management workflows, keeps falling short. Where AI can move the needle. And the adoption sequence we think makes that help safe enough to lean on.</p><h3>What is release management?</h3><p>Release management is the planning, scheduling, and control of the software delivery lifecycle, from development and testing through deployment and beyond. It is the layer between what engineering builds and what end users see.</p><p>When a single team ships a single service, it stays simple. In an enterprise, the scope expands. Multiple teams contribute to a single increment. Multiple components consolidate into a single solution. Multiple environments must be tested in the correct sequence. Multiple approval gates must be cleared before anything reaches production.</p><p>When it works, release management disappears. Software reaches users on schedule, without surprises. When it fails, it shows up in audit findings, customer escalations, and weekend incident reviews.</p><p>It is not the same as deployment, though the two are often conflated. Deployment is the technical act of putting software into an environment. Release management is the orchestration around it: what goes where, when, in what order, and with whose approval.</p><h3>Where Jira alone runs out of road</h3><p>A working release in a large organization rarely lives within a single Jira project. It draws fix versions from many projects, each with its own. The release itself is a coordination layer that spans them: code from several repositories, environments shared across teams, change requests in Jira Service Management that govern what can be deployed, and approvals that must be cleared in a defined sequence.</p><p>Jira provides the building blocks. The structural work of release management in Jira, turning those blocks into something a release manager can actually answer questions about, is where teams reach for spreadsheets, Confluence pages, or a release manager whose calendar fills up with status updates.</p><p>That is the structural gap our app exists to fill. It is also where AI starts to earn its keep, because most of the questions release managers field every week are answerable from data that already exists across connected systems. Just not in any single one.</p><h3>The six places it hurts</h3><p>Pain in release management is not evenly distributed. Across the customer conversations we have had, it concentrates in six areas.</p><p><strong>Dependencies and a complex landscape. </strong>Large releases involve dozens, sometimes hundreds, of moving parts. Visibility into the full release scope is often patchy. Dependencies between components are missing or unclear. Excessive changes cause disorder, and the release plan is rarely communicated clearly to all the teams that need it. Pulling multiple teams toward the same window adds a coordination cost that compounds with each additional team. A single overlooked dependency can hold up an entire release train.</p><p><strong>Compliance. </strong>Regulated industries like banking, healthcare, defense, and gaming add an extra layer to every release. Approval flows must be followed and documented, audit logs must be complete and tamper-resistant, and collaboration with regulators requires evidence spanning from code change through the deployment artifact. None of this is optional under DORA, IEC 62304, CMMC 2.0, or PCI DSS 4.0. The work itself is mostly manual, which makes it slow, error-prone, and a frequent bottleneck.</p><p><strong>Testing orchestration. </strong>Getting the right code tested in the right environment at the right time is harder than it sounds. Configuration drift between test and production environments remains one of the most reliable sources of post-release incidents. When teams share environments, scheduling becomes a daily problem rather than an occasional one.</p><p><strong>Environment management. </strong>Knowing which version is deployed where, which environments are healthy, and which are misconfigured is a prerequisite for reliable releases. Many organizations still rely on spreadsheets and tribal knowledge. The cost shows up later, as production incidents traced back to assumptions.</p><p><strong>Orchestration core. </strong>Every enterprise release management process needs a single source of truth. A place where release statuses from all connected systems are tracked on a roadmap and calendar. A place where state and approvals are controlled. A place where the connected toolchain remains internally consistent. Without it, information scatters across Jira, CI/CD systems, test platforms, and chat. Decisions are made on stale data.</p><p><strong>Automation gaps. </strong>Even teams with mature CI/CD pipelines spend significant time on routine work: assembling release notes, updating statuses across tools, compiling approval evidence, and reconciling information between systems. The patterns are predictable. This work is exactly what eats into the time that release managers should be spending on judgment calls.</p><h3>Where AI agents can help</h3><p>AI’s advantage in release management is context. An agent with access to work items, code changes, deployments, test results, approvals, and timelines can reason across that graph in ways that would take a human analyst hours. General-purpose AI assistants do not get this kind of grounding; release management agents that do are a different category of useful.</p><p>The mapping to each of the six areas above is reasonably clean.</p><p><strong>For dependencies, </strong>an agent can analyze them at every level: across releases, between tasks, within code, across components, through pipelines, and between environments. The interesting cases are the implicit ones — a shared library version, a database migration affecting several services, and a pipeline configuration that creates an ordering constraint. These are the dependencies humans miss until a deployment fails.</p><p><strong>For compliance, </strong>an agent can trace the chain from release to tasks to code changes to pull requests to artifacts, pulling in metadata from vulnerability scans and static analysis tools along the way. It can also produce the documents regulators expect, from change impact assessments to traceability matrices, in a fraction of the time a person would need. The cost-of-error problem is real here. The time savings in assembly are not in dispute.</p><p><strong>For testing, </strong>an agent can monitor whether the environment setup actually meets the release’s testing needs, track results across test cycles, and surface common dysfunctions along with possible remediation paths.</p><p><strong>For environment management, </strong>an agent can analyze health and usage, identify configuration drift, and help plan dependencies across environments for upcoming releases. The shift is from reactive (discovering a problem when a deployment fails) to proactive.</p><p><strong>For the orchestration core, </strong>this is where the impact is highest. An agent can generate a real-time summary of the current release state, identify risks based on patterns across the toolchain, suggest specific actions to address them, and validate consistency across connected systems. The release dashboard moves from a passive display to an active advisor.</p><p><strong>For automation, </strong>an agent can do more than execute existing rules. It can suggest new ones based on observed patterns, identify places where manual handoffs can be removed, and propose optimization paths a human can evaluate and implement.</p><h3>The cost-of-error problem</h3><p>Now, the uncomfortable part.</p><p>Release management follows strict processes because the cost of getting it wrong is high. A missed dependency breaks production. An incorrect compliance artifact triggers regulatory action. A false positive in risk detection delays a release that did not need to be delayed; a false negative lets a defect reach customers. Trust in the tooling, once lost, takes a long time to rebuild. In some industries, it does not fully recover within the same audit cycle.</p><p>AI agents, by nature, occasionally produce incorrect outputs. The industry numbers tell a sobering story: only 12% of enterprise AI agent initiatives reach production at scale, and Gartner forecasts that over 40% of agentic AI projects will be scrapped by 2027. In low-cost domains, the occasional miss is tolerable. In release management, where the cost of a single bad call can cascade across systems, customers, and regulatory relationships, organizations are justifiably cautious about handing over control.</p><p>This caution is not resistance to innovation. It is the same engineering discipline that makes release management valuable in the first place.</p><h3>An adoption sequence that respects the risk profile</h3><p>The way to handle this is not to avoid AI or to deploy it everywhere at once. It is to bring it in gradually, with the scope of agent authority widening only as the evidence justifies it.</p><p>The sequence we use and recommend has five phases.</p><p><strong>Phase 1. AI-assisted data collection. </strong>Start where risk is lowest. Information gathering, validation checks, and evidence collection. The agent brings the right data to the right person at the right time. The release manager reviews and decides. This saves time with effectively no downside: the agent is not making decisions or taking actions. It removes the manual data-gathering that consumes release managers’ time.</p><p><strong>Phase 2. Proactive agents with human approval. </strong>The agent autonomously collects what is needed and goes a step further: it proposes actions. A compliance agent drafts the approval evidence package and flags gaps. A dependency agent recommends reordering the release sequence. A risk agent suggests pulling a component out of scope based on test patterns. Every proposed action undergoes human approval before execution. The agent recommends; the human decides.</p><p><strong>Phase 3. Validated automation with cross-checking. </strong>This is where the architecture has to be right. Agent outputs that inform a decision need to be checked against an independent data source. When the agent says a release is ready, the system has to point to specific evidence, and a separate mechanism has to be able to spot-check that evidence for plausibility. That mechanism is increasingly a second agent, with the single job of reviewing the first agent’s decision before any action is taken. This is not a model-quality problem. It is a system-design problem. It also determines whether the tooling is trustworthy when the stakes are high.</p><p><strong>Phase 4. Autonomous agents in lower environments. </strong>Development and staging environments only. The blast radius of a mistake is contained: failed test runs, not customer incidents. Run the agent autonomously to orchestrate test deployments, validate environment configurations, and execute routine release steps. Build a track record. Surface the edge cases that need to be handled before anything moves closer to production.</p><p><strong>Phase 5. Production autonomy with embedded safeguards. </strong>Only after earlier phases produce evidence of reliability. This is the point where fully automated release management with AI agents becomes real. Multiple layers of safety apply: automated pre-deployment validation, rollback triggers, anomaly detection of the agent’s behavior, and clear escalation paths when confidence drops. The goal is not to remove humans from the loop. It is to reduce the routine load so consequential decisions receive the scrutiny they deserve.</p><p>Each phase exists because of what the previous phase produces: evidence that the agent works, evidence that cross-checking catches errors, and evidence that the process improves rather than merely changes. Skip a phase, and you are back to deploying interesting demos.</p><h3>Trust is the bottleneck, not capability</h3><p>It is worth saying out loud: the limit on how far agents go in release management is not model capability. It is trust. Trust is not earned by demos. It is earned by track records that are visible, auditable, and reproducible.</p><p>An organization with messy fix versions, ambiguous approval workflows, and components that do not reflect the actual service topology will not get useful agent behavior, regardless of which model sits behind it. The pre-work is unglamorous: labeling things accurately, structuring releases as actual release packages with a clear cross-project scope, and ensuring the underlying data reflects how work actually flows. The agent capability is the easy part by comparison.</p><p>The teams that will get the most out of AI in release management are the ones doing that pre-work now.</p><h3>Where we are</h3><p>We are in the early stages of using AI for data collection and building agents that support data processing within our release management workflows. We are also developing release management skills and the domain logic agents can compose against, to make more autonomous operation viable in later phases.</p><p>This is deliberate. Rushing past the early phases without building a foundation of trust, validation, and cross-checking would be irresponsible in a domain where reliability is the whole point. Each phase generates the evidence the next depends on. There is no shortcut to that.</p><p>How we approach the structural side of this, including release packages, cross-project scope, and change request integration, is visible in <a href="https://marketplace.atlassian.com/apps/1221946/release-management">Release Management for Jira</a>. The agent work sits on top of that structure, not beside it.</p><h3>An open question</h3><p>A question for anyone running releases in earnest.</p><p>If you were going to put an agent on the smallest task on your plate next quarter, what would that task be? What would have to be true about your data, your validation, and your ability to spot-check the result for you to extend that trust further?</p><p>The future of AI in release management will not be shaped by one vendor or one team. It will come from practitioners testing these ideas in real environments and sharing what worked and what did not. I would be curious to hear yours.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea8e6a799a76" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a One Flow: How to Balance Engineering Velocity and Customer Support Load]]></title>
            <link>https://medium.com/@releasemanagement/building-a-one-flow-how-to-balance-engineering-velocity-and-customer-support-load-3b8ba9380146?source=rss-66f5f60b52d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b8ba9380146</guid>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Release Management Apps]]></dc:creator>
            <pubDate>Thu, 08 Jan 2026 16:37:01 GMT</pubDate>
            <atom:updated>2026-01-08T16:37:01.635Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>In the early stages of building software products, engineering is mostly about speed — shipping features, iterating rapidly, and finding product-market fit. Engineering management at this stage focuses on optimizing delivery time, team efficiency, and technical execution.</p><p>But as the customer base grows, so does the volume of inquiries, incidents, production issues, and change requests. What once felt manageable begins to challenge team stability, delivery predictability, and engineer motivation. A common first instinct is to funnel everything into engineering backlogs like any other development task but this quickly reveals deeper systemic problems.</p><p>This article explores why that happens, what patterns leaders adopt to cope, and how an integrated “<strong>one flow</strong>” approach can help maintain both product momentum and customer satisfaction.</p><h3>The Challenge: Balancing Product Development and Production Support</h3><p>As customer-facing responsibilities increase, engineering organizations face a set of recurring tensions:</p><ul><li>Balancing new product development and customer support workload</li><li>Maintaining predictable delivery velocity while reducing MTTI and MTTR</li><li>Providing reliable delivery forecasts for internal and external stakeholders</li><li>Keeping engineers motivated across both feature work and operational tasks</li></ul><p>Left unaddressed, these competing demands might erode team morale, stretch timelines, and can ultimately slow both innovation and customer responsiveness.</p><h3>Common Approaches: From Shared Responsibility to Dedicated Support</h3><p>Many engineering leaders start by handling support within the same team. This is a workable approach for small teams with limited volume. As complexity grows, organizations often transition through recognizable stages:</p><h3>1. Ring-Fencing Engineers Through Rotations</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nmz8oul0fvZ7Hh9wWKKa9w.png" /></figure><p>Engineers rotate into a support role for a sprint for Scrum teams or a week or two for Kanban teams.</p><p><strong>Pros:</strong></p><ul><li>Maintains empathy for customers</li><li>Ensures engineers stay close to production realities</li></ul><p><strong>Cons:</strong></p><ul><li>Disrupts flow</li><li>Creates unpredictable team velocity</li></ul><h3>2. Dedicated Support Teams</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U3GFAXWwOfepmrLdrogAiQ.png" /></figure><p>A team fully focused on customer cases and incidents.</p><p><strong>Pros:</strong></p><ul><li>Faster response times</li><li>Shield product development teams from operational noise</li></ul><p><strong>Cons:</strong></p><ul><li>Risks of creating silos</li><li>Can weaken shared ownership of quality and stability</li><li>Product teams do not always get enough feedback from production issues and, therefore, are not motivated to eliminate production issues.</li></ul><p>The question becomes: <strong>How can we maintain the benefits of specialization without losing the “one flow” culture?</strong></p><h3>The Hidden Culprit: Tools That Separate Instead of Connect</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E0xj4R7J0VPtuszDgtPTPQ.png" /></figure><p>In many organizations, tooling unintentionally reinforces silos. Each team maintains its own board, workflow, and methodology:</p><ul><li>Engineering teams often select to operate in <strong>SCRUM</strong>, optimizing iteration planning and commitment.</li><li>Support teams prefer to operate in <strong>KANBAN</strong>, optimizing flow and throughput.</li></ul><p>This divergence is natural but it makes cross-team visibility difficult.</p><p>Ask yourself:</p><ul><li><em>How often do you view another team’s board?</em></li><li><em>How easily can you visualize cross-team dependencies?</em></li></ul><p>Jira offers strong capabilities for each team individually, but integrating multiple teams into a shared operational view remains challenging. This is where Marketplace Apps help bridge the gap.</p><h3>One Unified Board: Integrating Teams Without Sacrificing Autonomy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0knre485hkL8BJCC4eTVdQ.png" /></figure><p>To promote true “one flow” collaboration, we need a shared place where engineering and support can see each other’s work while still maintaining their individual policies.</p><h3>1. Combine Scrum and Kanban on the same board</h3><p>Bring multiple SCRUM sprints and KANBAN lanes into one board as dedicated swimlanes. This instantly unlocks:</p><ul><li>Shared visibility</li><li>Dependency mapping</li><li>Real-time understanding of workload distribution</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nx5ILaaDzSL3MPBUZpD09Q.png" /></figure><h3>2. Custom Views for Zoom-In / Zoom-Out Collaboration</h3><p>Teams should be able to toggle between:</p><ul><li>Their own focused view</li><li>A broader organizational view</li></ul><p>This maintains independence while fostering collaboration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wYpJNckqsSTppZqnkBaWew.png" /></figure><h3>3. Empowering Scrum Teams: Manage Sprints Directly From Swimlanes</h3><p>Scrum teams should be able to:</p><ul><li>Create and start new sprints</li><li>Move remaining scope</li><li>Estimate work</li><li>Plan upcoming cycles</li></ul><p>— all within their dedicated swimlane.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*haQRQqva7f3PaR0VriPVpw.png" /></figure><h3>4. Supercharge Scrum with Kanban techniques</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U_8D7s2gL_Pc-Brq9U1EIQ.png" /></figure><p>Mature Scrum teams can extract additional value by adopting selected Kanban techniques, including:</p><ul><li><strong>A “doing–done” model</strong> to optimize queues and improve flow</li><li><strong>Personal WIP limits</strong> to reduce context switching</li><li><strong>Explicit exit criteria and policies</strong> to increase predictability and quality</li></ul><p>These practices not only enhance Scrum performance, but also <strong>smooth the transition toward a Kanban-style flow</strong> when that becomes a more effective approach for engineering teams focused on delivering outcomes.</p><h3>5. Empowering Kanban Teams: Optimize Flow Without Interference</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K5mvstszrQxoFPxmn_hajA.png" /></figure><p>Kanban teams usually require:</p><ul><li>A combined set of WIP limits</li><li>Cycle time insights</li><li>Throughput analytics</li><li>Return limits and efficiency metrics</li></ul><p>— and they should manage it from their own swimlane without affecting Scrum processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tn7D46cKkXhtqEworXhDeA.png" /></figure><p>This integrated structure enables teams to learn from one another and adopt best practices across methodologies.</p><h3>About Us</h3><p>At <a href="https://marketplace.atlassian.com/vendors/1216961/release-management"><strong>Release Management Apps</strong></a>, we build elegant solutions that enhance cross-team collaboration and unlock true end-to-end visibility. The screenshots above showcase features from our app <a href="https://marketplace.atlassian.com/apps/1223877/advanced-kanban-agile-boards?hosting=cloud&amp;tab=overview&amp;utm_campaign=content-strategy&amp;utm_source=blog&amp;utm_medium=articles&amp;utm_content=aab-oneteam"><strong>Advanced Kanban &amp; Agile Boards</strong></a>, which among other capabilities enables organizations to create a unified board for multiple teams — supporting autonomy while reinforcing a strong “<strong>one flow</strong>” culture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b8ba9380146" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AppTime: A Comprehensive Time-Tracking & Resource Management Solution for Jira]]></title>
            <link>https://medium.com/@releasemanagement/apptime-a-comprehensive-time-tracking-resource-management-solution-for-jira-17b7c174025c?source=rss-66f5f60b52d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/17b7c174025c</guid>
            <dc:creator><![CDATA[Release Management Apps]]></dc:creator>
            <pubDate>Wed, 17 Dec 2025 10:57:44 GMT</pubDate>
            <atom:updated>2025-12-17T11:52:56.878Z</atom:updated>
            <content:encoded><![CDATA[<p>As teams expand and projects increase in complexity, many organizations look beyond basic task tracking in Jira. They seek a platform that enables full-fledged time tracking, resource planning and organizational visibility. That’s precisely where <a href="https://almarise.com/en/apptime/?utm_source=partner_website&amp;utm_medium=partner_blog_+post&amp;utm_campaign=releasemanagement_blog"><em>AppTime</em></a> from <a href="https://almarise.com/en?utm_source=partner_website&amp;utm_medium=partner_blog_+post&amp;utm_campaign=releasemanagement_blog">Almarise</a> enters the picture.</p><p>With AppTime, managers gain the oversight, control and insight they need, whether it’s agile sprint work, service operations or cross-departmental initiatives, all directly within Jira.</p><p><strong>Flexible Time Tracking Made Easy</strong> <br>Logging work is simple: users can enter time right within the Jira issue view. Every worklog is captured and turned into meaningful data via customizable fields and attributes tailored to your specific workflow.</p><p>The platform offers multiple views: a detailed grid for deep analysis, a compact list view for summary insights, and a visual time chart to instantly reveal how your team spends its hours. Using AppTime’s Timesheets module, you can generate detailed reports, group and filter data, save custom configurations for recurring analysis and export to XLSX or CSV. Unlimited number of custom attributes (e.g., billable, internal) are supported. For Jira Service Management users, AppTime extends time-tracking and timesheet capabilities to the customer portal* (*currently supported only on Jira Data Center).</p><p>Built-in approval workflows let you define single or multistage review processes, ensuring that logged hours are accurate, approved and compliant, adding an extra layer of accountability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*vxIb0KSAGCrriBVijwet5w.png" /></figure><p><strong>From Planning to Delivery</strong> <br>Time tracking is just the foundation. AppTime bridges the gap between planning and execution. Its Work Plans module supports planning and monitoring of tasks across issues, projects, sprints, versions and even JSM organizations. You can assign multiple users or entire teams, estimate remaining effort and follow progress in real time.</p><p>With capacity-management features, the platform helps you identify overloads early, balance workloads intelligently and manage availabilities proactively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/1*hiJ_eIO5hjVvCjpOnZg_Nw.png" /></figure><p><strong>Team &amp; Organization Structure at a Glance</strong> <br>Modern teams perform best when structure and visibility are clear. AppTime allows you to build your company structure within Jira: define teams, assign roles and availability, create hierarchies and dashboards that show workload trends and performance over time. This transparent view empowers planning and better decision-making by clearly highlighting who’s available, who’s overloaded and how capacity aligns with goals.</p><p><strong>Enterprise-Grade Controls: Approvals, Permissions &amp; Accountability</strong> <br>Visibility alone isn’t enough — you also need control. AppTime comes with an advanced permissions engine and approval system designed for enterprise contexts. You set exactly who can view, edit, approve or manage each piece of data. The Approval Center brings together things like missing hours, excessive work time, late logging or empty days in a single overview, enabling proactive issue detection. Multi-level approval workflows, including partial approvals, give growing teams the adaptability they require while keeping accountability high.</p><p><strong>“Engagements” — Upscaling to Strategic Work</strong> <br>The new Engagements module gives structure and meaning to logged effort. It allows you to group related projects, service operations, R&amp;D initiatives or routine “business-as-usual” activities into clearly defined initiatives, phases and deliverables. This means you can always trace how every hour contributes to larger business objectives.</p><p><strong>Unified Filtering &amp; Seamless Navigation</strong> <br>In a sea of worklogs, issues and plans, finding the right data quickly is essential. AppTime features a unified filter system applicable across all modules: Timesheets, Work Plans, Teams, Engagements. You define your scope (projects, sprints, epics or JSM organizations), add filters (time-ranges, keywords, users, teams, engagements) and get consistent logic throughout. Filtering is fast, intuitive and real-time — giving you full control over even complex datasets.</p><p><strong>What’s New in AppTime</strong> <br> AppTime is evolving rapidly. Recent major enhancements include:</p><ul><li>Multi-level approval workflows with support for partial acceptance</li><li>The Engagements module for centralized initiative tracking</li><li>A rebuilt permissions engine for enterprise-grade governance</li><li>Team dashboards offering workload insights and trend analysis</li><li>Enhanced planning &amp; capacity management capabilities</li><li>Full support for both Atlassian Cloud and Data Center environments</li></ul><p>With monthly feature updates, AppTime is fast becoming one of the most comprehensive native-Jira time-tracking and team-management solutions available. It has also earned the Atlassian Cloud Fortified badge, meeting Atlassian’s high standards for security, reliability and enterprise support.</p><p><strong>Why Teams Choose AppTime</strong> <br>Because it balances ease of use for team members with depth and control for managers and executives. Developers log time effortlessly and stay focused on their work. Managers gain clear visibility into project progress, team capacity and organizational efficiency. Executives see how people, plans and performance come together — all inside Jira. AppTime delivers clarity, accountability and growth.</p><p><strong>Get Started with AppTime — Free for All Jira Hosting Options</strong> <br>AppTime is available at no cost for all Jira editions: Cloud, Server and Data Center. Installation takes just a few clicks via the Atlassian Marketplace.</p><p>Discover how your team can track smarter, plan better and manage more effectively — starting today with <a href="https://almarise.com/en/apptime/?utm_source=partner_website&amp;utm_medium=partner_blog_+post&amp;utm_campaign=releasemanagement_blog">AppTime</a> by <a href="https://almarise.com/en?utm_source=partner_website&amp;utm_medium=partner_blog_+post&amp;utm_campaign=releasemanagement_blog">Almarise</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17b7c174025c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Releasing Tasks: Does not work for Enterprise?]]></title>
            <link>https://medium.com/@releasemanagement/releasing-tasks-does-not-work-for-enterprise-68982d6c45d0?source=rss-66f5f60b52d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/68982d6c45d0</guid>
            <category><![CDATA[release-management]]></category>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Release Management Apps]]></dc:creator>
            <pubDate>Thu, 19 Jun 2025 08:50:51 GMT</pubDate>
            <atom:updated>2025-06-19T09:33:49.206Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, we explore recent trends in accelerating software development and how they apply to organizations of various sizes. We also examine the specific requirements enterprises place on the release management process, and how Continuous Delivery can be adapted to meet these demands. Additionally, we outline a practical solution tailored to the realities of enterprise environments, along with the benefits it offers to development teams and organizations. Finally, we briefly touch on how this approach can be implemented using Atlassian Jira.</p><h3>Acceleration, acceleration, acceleration ..</h3><p>Through our engagements, we speak with global engineering leaders almost daily, and we’re seeing a growing emphasis on acceleration and achieving faster time-to-market goals. This shift is driving an increase in both the number and frequency of releases. Fortunately, modern software architectures — truly decoupled and distributed — are well-suited to meet this demand, providing engineering teams with a solid foundation for rapid delivery.</p><p>Agile and DevOps practices are becoming the de facto standard, empowering teams and organizations to deliver more effectively. While the maturity of these practices varies across organizations, the foundational capabilities are generally robust enough to support consistent execution.</p><h3>Why is Enterprise a different beast?</h3><p>Continuous Delivery is a promising approach for reducing time to market and responding more quickly to changing market needs, without compromising product quality. It works well in less complex architectural landscapes, which are more common among small and medium-sized businesses. However, it poses certain challenges for enterprises, where value is typically delivered at the solution level and involves multiple interconnected products. These implicit or explicit dependencies require careful management, often necessitating additional layers of integration and testing of non-functional requirements such as performance and security.</p><p>In addition, enterprises are more frequently subject to regulatory requirements, which call for compliance checks and a more formal change management process.</p><p>As a result, while Continuous Delivery is highly effective for enabling early integration and faster deployments to lower environments, a more gated approach — with clearly defined quality gates — is often necessary when promoting changes to higher environments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*iL49VeCZecHRaDrV" /></figure><h3>Solution: Level up!</h3><p>Executing quality gates at the level of each individual work item (such as a task, story, or bug), as is common in the Continuous Delivery philosophy, is becoming increasingly impractical and overwhelming. A more effective approach is to elevate the process and perform quality checks at the artifact level — that is, on specific versions of software components or products that make up a solution. By establishing a standardized, company-wide approach, organizations can streamline the promotion of these artifacts to higher environments.</p><p>As a result, the definition of a “solution” evolves into a collection of interconnected artifacts (product releases) — each aggregating multiple work items — with quality gates applied at the artifact or solution level. This shift reflects how business value is typically delivered: not through individual work items, but through coordinated releases of multiple components working together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*7PoCm9CU9jzSr1RS" /></figure><h3>Important benefits</h3><p>Artifact-based release management offers several additional benefits. Notably, it enables a clear separation between tactical and strategic levels within the enterprise. This approach provides software development teams with the freedom and flexibility to use various techniques and methodologies for building components or products, while establishing a common framework at both the product release and solution levels. In turn, this allows for a unified and orchestrated release process that aligns with the goals and objectives defined at the solution level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*PHtlGtYg0uUzfIix" /></figure><h3>How Release Management Apps for Jira can help?</h3><p>In Atlassian Jira, Releases (also known as Versions) are tied to specific Jira projects, which limits visibility and orchestration in enterprise use cases, especially those that span multiple projects. The simplistic status model and limited taxonomy further hinder efforts to structure enterprise-level release management processes effectively.</p><p><a href="https://marketplace.atlassian.com/apps/1221946/release-management-workflows-calendar-roadmaps-cloud?tab=overview&amp;hosting=cloud&amp;utm_campaign=content-strategy&amp;utm_source=medium&amp;utm_medium=articles&amp;utm_content=rm-releasingtasks"><strong>Release Management for Jira</strong></a> addresses these challenges by offering cross-project release management capabilities, robust workflows, automation, and a more comprehensive taxonomy. This enables organizations to establish a unified release management process at the artifact level and to package these artifacts into business solutions with their own dedicated workflows.</p><p>Enterprises can also benefit from complementary features such as structured release roadmaps with intermediate milestones, externally shareable release calendars, multiple automated release note templates, and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*Un_kxn9lrSTMDHr8" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*ZWcbkytBDQVD1WRQ" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*af1zZMDfis-zD_cw" /></figure><h3>Take out</h3><p>As global engineering leaders aim for faster time-to-market, modern decoupled architectures and Agile/DevOps practices are helping teams accelerate delivery. However, large enterprises face unique challenges due to complex solution-level dependencies, regulatory requirements, and the need for rigorous integration and non-functional testing.</p><p>While out-of-the-box Continuous Delivery techniques work well for smaller, simpler systems, enterprises often need a more structured and gated release process, particularly in higher environments.</p><p>To address this, organizations can adopt <strong>artifact-based release management</strong>, shifting quality gates from individual work items to artifacts (i.e., versions of components/products). This enables better orchestration, scalability, and alignment with business value, as solutions are formed by multiple interconnected artifacts.</p><p>Artifact-based release management also balances team autonomy and strategic governance, allowing flexibility in development practices while unifying release processes across the organization.</p><p><a href="https://marketplace.atlassian.com/apps/1221946/release-management-workflows-calendar-roadmaps-cloud?tab=overview&amp;hosting=cloud&amp;utm_campaign=content-strategy&amp;utm_source=medium&amp;utm_medium=articles&amp;utm_content=rm-releasingtasks"><strong>Release Management for Jira</strong></a> supports this approach by overcoming native Jira limitations through cross-project capabilities, release-centric roadmaps and calendars, advanced</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68982d6c45d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Launching Advanced Edition for our Apps: Release Management for Jira, Advanced Kanban & Agile…]]></title>
            <link>https://medium.com/@releasemanagement/launching-advanced-edition-for-our-apps-release-management-for-jira-advanced-kanban-agile-de89b06b37da?source=rss-66f5f60b52d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/de89b06b37da</guid>
            <category><![CDATA[atlassian]]></category>
            <category><![CDATA[atlassian-marketplace]]></category>
            <category><![CDATA[release-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Release Management Apps]]></dc:creator>
            <pubDate>Mon, 23 Dec 2024 12:10:09 GMT</pubDate>
            <atom:updated>2024-12-23T12:10:09.856Z</atom:updated>
            <content:encoded><![CDATA[<h3>Launching Advanced Edition for our Apps: Release Management for Jira, Advanced Kanban &amp; Agile Boards</h3><h3>Article Content</h3><p>In this article, we will share why we decided to join the <strong>Early Access Program (EAP) for Apps Editions with Atlassian,</strong> how we launched the first versions of our Apps’ Advanced Editions, and what the journey ahead looks like.</p><h3>Why consider it?</h3><p>As with any other app on the Atlassian Marketplace, we grow mostly organically, with a backlog that consistently includes a mix of our own ideas and client requests. As more enterprise clients join the Cloud, we increasingly see enterprise-grade features appearing on our team’s board.</p><p>We often face a dilemma between implementing certain features and the potential audience size for these features. Advanced functionality may not suit every client, leading them to question the rationale for paying for it. However, for more mature clients, these features are becoming crucial for purchasing the app, and they can clearly articulate the value.</p><p>Thus, there is no ‘one size fits all’ solution; your ‘Apps Editions’ need to be flexible to meet market demand.</p><h3>Excellence in execution</h3><p>We need to acknowledge that Atlassian has done a great job providing us with the technical capabilities to enhance our ‘Apps Editions’ with seemingly no additional overhead.</p><p>In particular, we are pleased with the ability to show a differentiated list of features for Standard and Advanced Editions, complete with short descriptions. Additionally, the flexibility of having segregated pricing plans for Standard and Advanced Editions makes it easy to develop pricing strategies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/776/0*9COiIKSMs3nuwXik" /></figure><p>Regarding technical implementation, we were pleased with the range of options available to segment functionality and feature visibility through configuration.</p><p>For instance, in our <a href="https://help.releasemanagement.app/space/GFJR/3004956696/Advanced+Features">Release Gadgets Apps</a>, we were able to easily hide or show complete gadgets (e.g. Release Frequency Gadget) thus segregating gadgets between the Standard and Advanced Editions. We also successfully implemented extra advanced features in existing Gadgets, providing enhanced options to outline selected Sprints and Epics on Release Calendars and Roadmaps together with Releases itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*SLAUHmVFP1SRwCpb" /></figure><p>For another <a href="https://help.releasemanagement.app/space/ASPT/3007053826/Advanced+Features">Advanced Kanban &amp; Agile Board</a>, we successfully implemented a number of enterprise-grade features (namely Flow Efficiency Calculation &amp; Alerts, Multiple Board Views) that we had delayed for some time due to value and cost considerations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/0*72_7K1V971fu6yse" /></figure><p>We took the same approach with <a href="https://help.releasemanagement.app/space/RMC/3009118209/Advanced+Features">Release Management for Jira</a> to include client requests that are more applicable for enterprise-grade setups in our Advanced Edition. Thus, we are shortly delivering Global Milestones, Global Properties for our Release Boards, and Access Token Management to use our Rest of APIs seamlessly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/0*CVdUQd_U8LmZ34wN" /></figure><p>Of course, we need to wait for the official launch of ‘Apps Editions’ for the complete marketplace. But as it stands, we are confident that we now have the right tools in place to inform our product and business decisions.</p><h3>The new interesting challenge?</h3><p>While it might seem easy to add all new enterprise-grade requests into the Advanced Edition, the real challenge lies in effectively promoting Advanced Features within the app, better segmenting features between the Standard and Advanced Editions, and determining whether to split existing functionality.</p><p>To answer these questions, it is essential to understand your customers’ journey with your app and have sufficient product analytics data. This knowledge helps you identify which features are utilized, how deeply, and how broadly, enabling informed decisions about feature segmentation and timing for promoting advanced capabilities, including usage-based limits.</p><p>We believe we are well-equipped with tools like <a href="http://journy.io/"><strong>journy.io</strong></a><strong> and </strong><a href="http://amplitude.com/"><strong>amplitude.com</strong></a>. Only time will tell how effective these will be.</p><h3>Take out</h3><p><strong>If you are a Marketplace Partner</strong>, we encourage you to consider the differentiated value propositions of Apps Editions that you will be able to offer to customers and partners. Apps Editions is right now in EAP and will soon be available for all partners.</p><p><strong>If you are a Solution Partner</strong>, although it might appear as an additional moving part, your customers will gain more flexibility to receive the right solutions at the right price, supported by Marketplace Partner capabilities.</p><p><strong>If you are a Customer</strong>, there’s a great opportunity for your requests to be addressed more quickly, giving you the flexibility to choose the specific features you need, much like selecting from a menu. During EAP Apps Editions are available for customers on the new billing system only and during the EAP, customers can raise a request to get upgraded.</p><p>If you want to try out our <strong>Apps Editions please submit a request </strong><a href="https://releasemanagement.atlassian.net/servicedesk/customer/portal/11/group/16/create/53"><strong>here</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de89b06b37da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Atlassian Marketplace Growth Strategy: Stop Clients Leaving]]></title>
            <link>https://medium.com/@releasemanagement/atlassian-marketplace-growth-strategy-stop-clients-leaving-29c628a73ccd?source=rss-66f5f60b52d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/29c628a73ccd</guid>
            <category><![CDATA[churn-prediction]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[success]]></category>
            <category><![CDATA[growth-strategy]]></category>
            <dc:creator><![CDATA[Release Management Apps]]></dc:creator>
            <pubDate>Thu, 26 Sep 2024 11:26:42 GMT</pubDate>
            <atom:updated>2024-09-27T12:25:27.434Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>In this article, we share our experience in controlling churn for our Atlassian Apps, which has fueled organic growth and established a stronger foundation for increased marketing spend. While the problem statement and suggestions may apply to any SaaS business, we focus on specifics relevant to the Atlassian Marketplace, which is our area of expertise and success.</p><h3>Addressing Churn Challenges for Enhanced Growth in the Atlassian Marketplace</h3><p>The Atlassian Marketplace is an excellent platform for bootstrapping SaaS businesses, offering a large customer base and an active community. If you have ideas for Atlassian Apps, you’ll find the tools and capabilities needed to assess market fit and stimulate organic growth. However, you may soon realize that your growth isn’t happening as quickly as you’d like. While there are known strategies to increase traffic, it’s crucial to build a strong foundation to effectively control churn.</p><p>Consider the following questions:</p><ul><li>Why aren’t people converting after a trial?</li><li>Why do they leave after only a few months?</li><li>Why don’t they renew annual licenses?</li></ul><p>Promptly addressing these issues involves:</p><ul><li>Determining if they’re your target customers</li><li>Identifying problems early</li><li>Engaging with clients early to attempt to manage churn These are the challenges we encountered while developing our own growth strategy.</li></ul><h3>Solutions that did not work out</h3><p>Our initial strategy was to leverage existing resources, like Amplitude (or alternatives like MixPanel), to manage churn. While these tools excel in product development, they fall short in identifying and handling churn effectively. The challenge was akin to ‘seeing a forest but missing the trees’ — we couldn’t automate segment identification or detect early churn indicators. Initially, we attempted a manual approach, conducting daily reviews of segmented accounts to spot issues and engage clients. This quickly proved unsustainable due to unrealistic pace expectations, competing business focuses, and frustration over a lack of direct client feedback. On the Atlassian Marketplace, engaging the right contacts is challenging:</p><ul><li>Technical Contacts (often DevOps) are typically tasked only with installation, not engagement.</li><li>Billing Contacts (procurement professionals) are mostly interested in procurement activities</li><li>Partner Contacts usually consist of generic emails, rarely yielding responses to engagement invitations.</li></ul><p>Fortunately, we maintained contact with individuals from demo sessions and could export additional contacts from Service Desk records. This approach had some success, but it wasn’t scalable.</p><h3>Exploring PLG/SLG Solutions for Effective Churn Management and Enhanced Engagement</h3><p>Based on advice from another Marketplace Partner, we explored the growing segment of Product-Led Growth (PLG) and Sales-Led Growth (SLG) solutions. We trialed <a href="https://www.journy.io/">journy.io</a> and were impressed with its capabilities to manage churn effectively. Key features included:</p><ul><li>Defining custom scores and health profiles using our existing product analytics from Amplitude</li><li>Automating churn signals for specific segments and configuring playbooks</li><li>Properly segmenting clients based on usage tiers and monthly recurring revenue (MRR) scores</li><li>Visualizing our client portfolio according to engagement stages and usage patterns</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5MXwK2ZALRoFLv_NGYcm9g.png" /></figure><p>Currently, we’re implementing an engagement solution to interact directly with our app users via Jira. If readers show interest in the comments, we’re happy to share our implementation process, current status, and key results. We’re also eager to learn about other churn reduction and conversion increase solutions and their outcomes. Additionally, we’ve discovered Segment.com, which opened new possibilities for us. This exploration led us to adopt an appropriate CRM — we transitioned from Mailchimp to a more robust solution quite quickly.</p><h3>Was it difficult to start?</h3><p>It wasn’t super easy to achieve, but we managed it relatively quickly. Since we were already collecting product analytics, we redirected the data flow into <a href="https://segment.com/">Segment.com</a> before sending it to Amplitude and journy.io, replacing the direct integration with Amplitude. We also used the no-code platform <a href="https://make.com/">Make.com</a> to extract data from the Atlassian Marketplace via Open API and upload it to journy.io through Segment.com. The entire setup took us about two weeks. If you’re interested in trying this approach, we have created a step-by-step guide with reusable templates for no-code solutions, which we’ve published on Confluence: <a href="https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2774433793/Atlassian+Marketplace+Connector">Atlassian Marketplace Connector</a> Feel free to reach out if you need any assistance!</p><h3>About us</h3><p>We are Release Management Apps, a Platinum Atlassian Marketplace Partner. We proudly advanced from Silver to Gold to Platinum over three consecutive years, thanks largely to our award-winning apps — Best New App in 2020, Finalist for Agile-at-Scale in 2022, and Winner for Agile &amp; DevOps in 2023. Despite these achievements, we continue to search for the most effective growth strategy, as our current growth rate doesn’t meet our expectations. Our connection with journy.io began as clients, and we were so impressed that we seized the opportunity to take it over when it arose. We’re excited to share this journey with the rest of the Atlassian Marketplace community.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29c628a73ccd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking the Power of Advanced Kanban Boards with Nave Integration]]></title>
            <link>https://medium.com/@releasemanagement/unlocking-the-power-of-advanced-kanban-boards-with-nave-integration-8333621cd10b?source=rss-66f5f60b52d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/8333621cd10b</guid>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[nave]]></category>
            <category><![CDATA[reporting]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[kanban]]></category>
            <dc:creator><![CDATA[Release Management Apps]]></dc:creator>
            <pubDate>Fri, 15 Mar 2024 08:58:16 GMT</pubDate>
            <atom:updated>2024-03-15T11:11:08.773Z</atom:updated>
            <content:encoded><![CDATA[<p>In the fast-paced world of project or product management, the efficiency of execution is key. Every minute saved and every bottleneck avoided can mean the difference between success and stagnation. For those who have embraced <a href="https://marketplace.atlassian.com/apps/1223877/advanced-kanban-agile-boards?hosting=cloud&amp;tab=overview&amp;campain=Nave">Advanced Kanban boards</a>, the journey has been one of streamlined workflows and enhanced visibility on the flow bottlenecks. However, for all its benefits, there has been a crucial aspect missing: comprehensive reporting on key Kanban process measurements. Recognizing this gap, many have been asking for a solution to provide insightful metrics to drive continuous improvement.</p><p>Enter <a href="https://marketplace.atlassian.com/apps/1220667/kanban-analytics?tab=overview&amp;hosting=cloud">Nave</a> — probably, the best solution for Kanban metrics on the market.</p><p>Nave seamlessly integrates with Advanced Kanban boards, offering users an intuitive Analytics tab where a measurements dashboard is just a click away. With Nave, teams can effortlessly measure crucial metrics that underpin their Kanban processes:</p><p>1. <strong>Cycle Time:</strong> This metric measures the time a task spends moving through your process, starting from when your team begins working on it, unlike lead time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KaK9jBwqlei-_iUh" /></figure><p>2. <strong>Throughput</strong>: Throughput measures the total amount of work delivered within a specific period. It provides teams with a clear view of their productivity and helps them make informed decisions about flow optimization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jouGB4h1RIdA6JCw" /></figure><p><strong>3. Work In Progress (WIP):</strong> WIP limits are crucial in Kanban, as they help teams maintain a steady flow of work. Nave allows teams to visualize their WIP limits and monitor them in real time, preventing overburdening and bottlenecks. This functionality greatly extends all types of work-in-progress limits configured in Advanced Kanban Boards.</p><p>4. <strong>Team Performance</strong>: Measuring team performance is essential for ensuring that work is delivered efficiently. Metrics such as Cycle Time and Throughput are key indicators of team performance and should be closely monitored to ensure that teams are delivering results to customers effectively. Cycle Time, Throughput, and WIP are interconnected by Little’s Law, a fundamental principle in queuing theory. Understanding this relationship allows teams to optimize their workflows and improve their overall efficiency.</p><p>5. <strong>Bottlenecks</strong>. By leveraging Nave Kanban metrics, teams can spot bottlenecks as they occur. Signs such as increasing Cycle Time, decreasing Throughput, and sharp gradients in cumulative flow diagrams are indicators that teams should watch out for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dAG4Pcc2qMcpqt43" /></figure><p><strong>Forecasting with Nave</strong></p><p>One of the standout features of Nave is its ability to forecast the time needed to complete work based on past execution times and Monte Carlo simulation. This feature allows teams to answer critical questions such as when tasks will be completed, why so slow, and how many tasks can be finished within a specified timeframe. A significant advantage of this method is the ability to define multiple scenarios and correctly estimate the probability of each of them:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*to1KXcv4WdUzT06E" /></figure><p><strong>Executive Dashboards for Organizational Insights</strong></p><p>For organizations operating at scale, Executive Dashboards provide insightful metrics across all teams. These dashboards enable organizations to proactively spot bottlenecks and make data-driven decisions to improve team efficiency.</p><p>These dashboards can also immediately spot what teams require help right now and what the most critical areas to be focused on to do the right things.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b85ilS3oAeFkZ9ux" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kQTrPqI9KqbiPyY2" /></figure><p><strong>Try it now!</strong></p><p>Don’t miss out on this opportunity to enhance your Kanban processes. <a href="https://marketplace.atlassian.com/apps/1220667/kanban-analytics?tab=overview&amp;hosting=cloud">Try Nave</a> in integration with <a href="https://marketplace.atlassian.com/apps/1223877/advanced-kanban-agile-boards?hosting=cloud&amp;tab=overview&amp;campain=Nave">Advanced Kanban Boards</a> today. <strong>Get 10% off all yearly plans using code AAKBNAVEANNUALLY and all monthly plans with code AAKBNAVEMONTHLY for the first year!</strong> Seize the chance to unlock the full potential of your Kanban workflows with Nave — where efficiency meets innovation</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8333621cd10b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Atlassian Partner of the Year 2022 Finalist: Agile at Scale App]]></title>
            <link>https://medium.com/@releasemanagement/atlassian-partner-of-the-year-2022-finalist-agile-at-scale-app-e28e53e261f7?source=rss-66f5f60b52d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e28e53e261f7</guid>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[wip]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[jira]]></category>
            <dc:creator><![CDATA[Release Management Apps]]></dc:creator>
            <pubDate>Thu, 20 Apr 2023 19:08:16 GMT</pubDate>
            <atom:updated>2023-04-20T19:08:16.878Z</atom:updated>
            <content:encoded><![CDATA[<p>Atlassian announced today that <strong>Release Management </strong>is a finalist for the <strong>Atlassian Partner of the Year 2022 Award: Agile at Scale App </strong>for their outstanding contribution and achievements during the calendar year 2022. This includes exceptional efforts in developing new business, thought leadership, and products and services that complement Atlassian.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*iRQSGHQnFgzUCRRQjp4AlA.png" /></figure><p><em>“Every year, Atlassian partners submit so many incredible nominations,” said Allyce Mardesich, Atlassian’s Head of Marketplace Partnerships, “being recognized as a finalist in an award category is a huge accomplishment given all of our partners’ depth of expertise and commitment to innovation on behalf of Atlassian customers. We are excited to spotlight some of our top partners in these categories across the Atlassian Marketplace.”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e28e53e261f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Roadmaps — When Good Enough Just Isn’t Good Enough]]></title>
            <link>https://medium.com/@releasemanagement/product-roadmaps-when-good-enough-just-isnt-good-enough-ab3657902de0?source=rss-66f5f60b52d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab3657902de0</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[sprint]]></category>
            <category><![CDATA[release-management]]></category>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[roadmaps]]></category>
            <dc:creator><![CDATA[Release Management Apps]]></dc:creator>
            <pubDate>Tue, 27 Sep 2022 20:10:17 GMT</pubDate>
            <atom:updated>2023-04-30T19:04:25.402Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product Roadmaps — When Good Enough Just Isn’t Good Enough</h3><p>Product Roadmaps — When Good Enough Just Isn’t Good Enough</p><p>In this article we will discuss how microservices and micro-frontends architecture empowers teams to deliver more frequently and independently to production. And when established product-centric roadmaps aren’t good enough to answer the question “When will it be delivered?“ We will also outline why delivery-centric roadmaps are a better fit and what are the ways to define your release scope in Jira in order to plan, orchestrate and deliver a release cross-team, cross-project or cross-company.</p><h3>The world has changed</h3><p>The world of ‘software development’ has changed. Most backends nowadays are based on services and microservices (m/s). They are also owned and delivered by different teams independently. Some of them are single-tenant serving specific clients or segments. Others are multi-tenant serving all the clients in a specific region or Datacenter (DC).<a href="https://martinfowler.com/articles/micro-frontends.html"> Micro Frontends</a> is also picking up to do the same for client-facing Apps what m/s did for backend.</p><p>With all this new eco-system in place almost any feature you develop presumes changes in multiple m/s, widgets that need to be delivered to finally toggle ON your feature flag. To make things easier you can always package those changes somehow in a single delivery or orchestrate multiple deliveries in a coordinated fashion.</p><p>But you ‘do not want to’, mainly because:</p><ul><li>technology is built for — and empowers — independent, incremental and iterative delivery</li><li>you don’t deliver one feature at a time; you deliver dozens on a regular basis</li><li>“time to market matters” and you want to deliver something as soon as you have it working and just turn it on when all the dependencies are ready and in place.</li></ul><h3>Product-centric roadmaps don’t answer</h3><p>Product-centric roadmaps are usually built around the structure of software requirements (e.g. Initiatives split into Epics that are split into Stories and/or Technical Tasks). Stories and Tasks are usually Team level and sit with teams and their deliveries. But Epics in most cases span across different teams/departments (some call it Program level), and the notion of delivery and ownership is becoming blurred.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hQYnAqrIwnxjCdbE" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dVSdPKrRPMW6TbJY" /></figure><p>It’s very difficult to answer the question when a small Feature will be delivered, because usually it includes changes in multiple services and frontends owned and delivered by different teams with their own delivery technique and cadence.</p><p>Things get worse if this feature requires configuration per client (b2b) or customer segment (b2c)… or you have a distributed production environment with a private cloud in the US and another one in EMEA. This is when questions like “When will Feature X be delivered?” become really tough to answer.</p><h3>Delivery-centric roadmaps can help</h3><p>One of ‘<a href="https://resources.scrumalliance.org/Article/key-values-principles-agile-manifesto">The Key Values and Principles of Agile Manifesto</a>’ says</p><p>Working software is the primary measure of progress.</p><p>What is working software? Software deployed to the production environment and configured for the end customers to use. There’s no credit given to anything partial.</p><p>If you look at it from this perspective, your ‘working’ Feature X is becoming a set of deployments of a set of services and Apps with appropriate configurations applied. We will be calling these deployments ‘releases’, comprised of the changes engineering teams performed to implement the requirements given for Feature X..</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TnCK-_DYlHIGcs6C" /></figure><h3>Helping how?</h3><p>Planning, visualizing, orchestrating and deploying your releases across multiple services and Apps will give you the ultimate solution to answer the question “When will it be delivered?“. But also help in a way to manage the flow of different deliveries happening, spot impediments, clearly understand the impact, and manage the expectations on a) “Why so slow?” and b) “What’s the new date?“</p><h3>Release Management beyond ‘Affects version and Fix version’ in Jira</h3><p>In Atlassian Jira, release management is all about ‘Affects versions and Fix versions’ standard fields that are tied to any issue type you create. They are referencing a unified lookup that is configured on Project level and can’t be shared cross-project.</p><p>So, in order for you to define your release scope, you need to add a new version in Releases lookup and assign issues to it via the Fix Version field.</p><p>This might be good enough if you track your different components in separate projects and have a good culture of using the Fix Version field. It would also be okay to have a plain list of versions of different Apps and services if you track it all in a single project (just difficult sometimes not to get lost in this list).</p><p>Once you track releases of individual components as Fix Versions you need a tool to aggregate them into something bigger to track your Epics/Features or more complex releases’ cross components/projects. There are a number of Apps on Atlassian Marketplace to help with that.</p><p>Sometimes it is useful to ‘simulate’ a single version across projects (not supported by Jira out of the box). Again, most of these tools from the Marketplace have a versions-sync functionality cross-project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*waVb9YW-cFqEls1w" /></figure><h3>Jira Epic as deliverable?</h3><p>Some companies do not use fix versions and use Jira Epics instead to define scope of releases. And for a good reason:- in the former Classic and now<a href="https://support.atlassian.com/jira-software-cloud/docs/learn-the-basics-of-team-managed-projects/"> Company-managed projects</a> (CMP) you can share your Epic across projects to aggregate work from different services and Apps to deliver Features. If you link here tasks from DevOps and Change Management (CM) projects (if tracked separately). Epics could easily become deliverables. For better tracking you can use Due Date or any other custom date field as Release Date and build all the reporting accordingly.</p><p>In former NextGen and new<a href="https://support.atlassian.com/jira-software-cloud/docs/learn-the-basics-of-team-managed-projects/"> Team-managed projects</a> (TPM) Epics are tied to the project and you get a deja vu with Fix Versions. They may be still good enough to treat these individual Epics as deliverables but most probably you would need similar tooling to aggregate them into something bigger to orchestrate end-to-end delivery and/or sync those Epics across all projects to ‘simulate’ single delivery (from a business perspective).</p><h3>Sprints in Jira as deliverable?</h3><p>Some of the Scrum adepts would be puzzling reading up to here:- “What are they talking about? We deliver at the end of each sprint (!)“. If this is true we really admire it. Same time Sprint in most cases is a team level delivery, and if you want to release something across teams you need to find ways to aggregate and orchestrate sprints as deliverables. So, the problem statement seems similar to Fix Versions for individual projects or Epics from different TPMs. Probably with a difference of ‘talking and talking’ Sprints from different boards to aggregate in single end-to-end deliveries and orchestrate accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Fb0bACor0JPNYYVE" /></figure><h3>Custom JQL as deliverable?</h3><p>What is ‘Release’ in Jira?:- it’s all the issues where the fixVersion field equals the Release name.</p><p>What is ‘Epic’?: — all the issues with Epic link equals to Epic key.</p><p>What is ‘Sprint’? — all the issues with Sprint being in the Sprint name.</p><p>So, it’s just a JQL (!)</p><p>Why can’t we define even more Custom JQL then as deliverable? We can. Just define how you want to differentiate deliverables and what attributes and values are to be used (Jira labels seem an obvious choice but not limited to) for tracking your release.</p><p>Probably a good tool that will allow you to package such custom JQL and bring Release notion to it with necessary attributes will be very beneficial.</p><h3>Mixing all the above</h3><p>The above options give you flexibility as there is no one size fits all. The reality is you most probably would need to combine them, as organizations are varied, and internally might use different approaches towards release management.</p><p>E.g. Imagine a bank with some legacy backend solutions being delivered on a fixed cadence, and let’s say Fix Versions are used. Same time you have a new innovative department (or a third-party) responsible for online or mobile banking with established CI/CD practices and deliverables by Epics or Sprints. Now you want to develop and deliver a feature that goes across those 2 departments and orchestrates such deliverables.</p><p>Ideally to have options to aggregate Fix Versions from one project and Epics or Sprints as deliverables from others to orchestrate and delivery cross-project release. There are Apps on Atlassian Marketplace to help you with that.</p><h3>A few take away notes</h3><p>The new world of software development presumes microservices and micro-frontends architecture empowers multiple teams to continuously deliver to production completely independently from each other. Disregard the fact that Product-centric roadmaps are good for planning work, they can’t help with questions like “When will it be delivered?“ Delivery-centric roadmaps can, and there are tools to plan, orchestrate, and deliver release giving you ultimate flexibility to define the scope of your deliveries in Jira</p><ul><li>either via Fix Version field and Releases in Jira</li><li>or Epics</li><li>or Sprints</li><li>or Custom JQL</li></ul><p>as well as a mix of those approaches to make cross-Jira projects ensuring end-to-end delivery.</p><h3>Who ‘we’ are?</h3><p>We are one of the <a href="https://marketplace.atlassian.com/vendors/1216961/release-management">partners</a> on Atlassian Marketplace who focus on Release Management and Delivery-centric Roadmaps solutions for Jira, both <a href="https://marketplace.atlassian.com/apps/1221946/release-management-workflows-calendar-roadmaps-cloud?hosting=cloud&amp;tab=overview&amp;utm_campaign=content-strategy&amp;utm_source=medium&amp;utm_medium=articles&amp;utm_content=rm-productroadmaps">Cloud </a>and <a href="https://marketplace.atlassian.com/apps/1218705/release-management-workflows-calendar-roadmaps?hosting=datacenter&amp;tab=overview&amp;utm_campaign=content-strategy&amp;utm_source=medium&amp;utm_medium=articles&amp;utm_content=rm-productroadmaps">Datacenter</a>. Our mantra is “Working software is the primary measure of progress“ and we truly believe in the statements we wrote in this article. We would be happy to have a constructive discussion in comments to this article or you can always reach out to us via our<a href="https://docs.google.com/forms/d/e/1FAIpQLSdvVBm5KK5wTNosLqyP9iKUI8GOoqZn8kQEyV-1yAOJZEwKxQ/viewform"> Service Desk</a>.</p><p>Stay tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab3657902de0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>