Discussions
-
Atlassian Event: What Changes When AI Becomes Part of the Entire SDLC?
Atlassian Event: State of AI SDLC AI in software development is moving pretty quickly. It started with code suggestions. Now we're talking about AI agents helping with planning, development, testing, and production workflows. That shift raises a different set of questions: Are we measuring the right things?Can agents work…
-
Atlassian Event: When AI Agents Write the Code, Who Owns the Outage?
Atlassian Event: State of AI SDLC AI is no longer just helping developers write code. It’s starting to influence how software gets planned, built, and run. That raises some bigger questions for engineering and DevOps teams: Are we measuring the right impact?Do AI agents have enough context to work reliably?And when an…
-
Where should an SAP implementation solution live?
I've been wondering how Jira administrators view large SAP S/4HANA implementation projects. Imagine a solution that could manage everything from requirements and Fit/Gap analysis to WRICEF tracking, sprint planning, testing, dashboards, and project governance. Would you expect something like that to work natively within…
-
Does anyone else feel Jira gets harder to manage as more teams get involved?
I've noticed this on a couple of large delivery programs recently. Everything works fine until you have several teams working in parallel, dependencies everywhere, approvals, testing, and different stakeholders trying to stay aligned. That's usually the point where things start getting messy. Curious if others have…
-
How are you managing SAP S/4HANA projects in Jira?
We've been having a few internal discussions around this recently, and I'm curious how other teams are approaching it. Jira does a great job for agile project management, but SAP S/4HANA implementations bring a different level of complexity. Beyond sprint planning and issue tracking, there are requirements, Fit/Gap…
-
Should every SAP team use the same Jira configuration?
As organizations scale their SAP delivery, Jira often becomes the central platform for managing requirements, development, testing, and project tracking. One question that frequently comes up is: How much should be standardized across projects? On one hand, standardized workflows, issue types, and configurations make…
-
Why do business and IT teams often see SAP projects differently?
One of the most interesting challenges in SAP implementations isn't technical. It's alignment. Business teams focus on business processes, priorities, and outcomes. Delivery teams focus on requirements, development, testing, and timelines. Both are working toward the same objective, yet they often view project progress…
-
Is your Jira configuration scaling as well as your projects?
One thing I've noticed in growing Jira environments is that complexity doesn't usually arrive all at once. It builds gradually. A new workflow is added for one project. A custom issue type is created for another. Additional fields, automations, and permission schemes are introduced as business requirements evolve. Each…
-
Is your Jira instance becoming harder to manage as your organization grows?
Most Jira environments start simple. A few projects. A handful of workflows. Some custom fields and automation rules. As more teams adopt Jira, new requests naturally follow. Different workflows are created, additional custom fields are introduced, Marketplace apps are installed, and new automations are added to support…
-
Are cross-team dependencies the biggest risk in large SAP programs?
One of the biggest challenges in enterprise SAP implementations isn't delivering individual work items. It's managing the dependencies between them. A single business requirement can involve multiple teams, development objects, testing activities, approvals, and business stakeholders. When one dependency slips, it can…
-
When was the last time your Atlassian environment had a health check?
As organizations evolve, so do their Atlassian environments. New teams are onboarded, workflows are refined, Marketplace apps are introduced, and automations are added to support changing business needs. These changes happen gradually, often over months or even years. The question is: Is your Atlassian environment evolving…
-
Why do SAP project decisions become harder as implementations grow?
Every SAP implementation starts with a clear plan! Requirements are gathered, timelines are defined, and responsibilities are assigned. But as projects progress, making timely decisions often becomes more difficult. Why? * Because the information needed to make those decisions is rarely in one place. * Project managers…
-
Are your Jira workflows helping your SAP project, or slowing it down?
One of the biggest strengths of Jira is its flexibility. Teams can build workflows that reflect how they actually work, automate repetitive tasks, and adapt processes as projects evolve. But in large SAP implementations, flexibility can sometimes become complexity. As projects progress, new statuses are added, approval…
-
Does every SAP implementation really need a separate project management tool?
This is something I've been thinking about lately. Many SAP implementation teams use one platform for project planning, another for requirements, another for testing, and spreadsheets for reporting. It raises an interesting question: Is using multiple tools actually making projects easier to manage, or just adding more…
-
Consistency vs. flexibility: How standardized should SAP project delivery be?
No two SAP implementations are exactly the same. Business processes differ. Teams work differently. Every organization has its own priorities. But one thing I've noticed is that many projects also differ in how they're managed. Workflows, issue types, reporting, and even project structures often vary from one…
-
Why does project visibility become harder as transformation programs grow?
Most enterprise transformation initiatives start with a clear goal: improve collaboration, increase visibility, and deliver outcomes faster. Yet as programs scale, many teams experience the opposite. More stakeholders become involved. More systems are introduced. More reports are created. Yet getting a clear answer to a…
-
Is end-to-end traceability still a challenge in your SAP projects?
One question that came up during a recent discussion with SAP project teams was: How easy is it to trace a business requirement from day one through to deployment? In many SAP implementations, requirements, Fit/Gap analysis, development, testing, and defect resolution are managed across multiple tools. As the project…
-
Why do SAP projects still rely on spreadsheets for visibility?
I've been speaking with teams involved in SAP implementations recently, and one challenge keeps coming up. Despite having powerful tools for project management, many SAP programs still depend on spreadsheets for status updates, reporting, and stakeholder communication. As projects grow, teams are often juggling: * Business…
