Close
Diese Seite in deiner Sprache anzeigen?
Alle Sprachen
Sprache auswählen
Erste Schritte
Einführung in Jira Product Discovery
Benutzerrollen und Berechtigungen
Kurzanleitung
Projekte
Overview
Resources
Ideen
Überblick
Resources
Einblicke
Überblick
Resources
Felder
Überblick
Resources
Ansichten
Überblick
Resources
Delivery
Überblick
Resources
Automatisierung
Overview
Resourcen
Integrationen
Überblick
Resources

Überblick über die Jira Product Discovery-Umsetzung

Wie gelangen Ideen von der Ideenfindung zur Umsetzung?

Das Hauptziel des Software Development Lifecycle (SDLC) ist es, effizient und effektiv hochwertige Software zu produzieren, die die Kundenerwartungen innerhalb eines Zeitrahmens und Budgets erfüllt oder übertrifft. Zwar hat jedes Team seine eigene Arbeitsweise, aber der grundlegende Workflow umfasst diese Phasen:

  1. Parkplatz: Wir beginnen mit "unsicheren" Ideen in einem Backlog, das zur Prüfung bereit ist. Diese Ideen wurden nicht recherchiert oder priorisiert und wurden wahrscheinlich von Kunden, Teams mit Kundenkontakt oder Führungskräften vorgeschlagen.
  2. Ideenfindung: Ideen werden mithilfe von Recherchen, Kundengesprächen und einer Validierung des Problems und der Lösung untersucht, um sicherzustellen, dass es sich lohnt, sie weiterzuverfolgen. Möglicherweise ist nur ein minimaler Entwicklungsaufwand erforderlich, z. B. ein technischer Spike, um die Machbarkeit einer Idee zu beurteilen. Am Ende wird eine Idee priorisiert (oder nicht).
  3. Ready for delivery: These are “certain” ideas that have been validated, assessed for impact, prioritized, and are now committed to by the team. This is the transition point from discovery to delivery where we prepare for development.
  4. Delivery: Ideas are in progress! They are being designed, built, tested, and deployed.
  5. Impact: We’ve shipped! Ideas have been delivered to customers, and now we monitor the impact and feedback. Any insights will be fed into the next round of improvements, and the cycle repeats itself.

It’s important to remember that while it’s easiest to explain discovery and delivery as phases in a cycle, they are often not concrete moments in time, or perfectly linear. They are continuous and require constant listening and iterating.

How do Jira Product Discovery and Jira Software work together?

Jira Product Discovery gives you a separate space for prioritization and roadmapping and figuring out what ideas to commit to on the roadmap. Once ideas have commitment, connect them to your delivery tickets in Jira Software. Ideally you shouldn’t have any tasks in your Jira Software backlog that are not 100% committed to. By having both discovery and delivery in Jira, business and tech teams are more connected with a unified workflow, less context switching, and more visibility.

The table below highlights the best way to think about Jira Product Discovery and Jira Software together.

 

Jira Product Discovery

Jira Software

Zweck

Discovery

Delivery

Was

Helps you decide what to work on now, next, and later

Helps you plan and track how committed-to work will be done

Jobs it accomplishes

  • Gathering ideas and insights
  • Priorisierung
  • Roadmapping

  • Planning execution
  • Zuordnung von Abhängigkeiten
  • Delivery tracking

How do I connect ideas to delivery tickets in Jira Software

You can connect Jira Product Discovery ideas to any issue type in Jira Software (or Jira Work Management). As long as your software project is on the same site as your discovery project, you can connect an idea to an epic with multiple child issues, or have a one:many relationship and connect one idea to multiple epics across multiple software projects.

To link an idea to a delivery ticket in Jira Software:

  1. Click on any idea and click the Delivery tab in the top right
  2. Select Create a delivery ticket if you want to create and connect to a new epic or issue, or select Add a delivery ticket to connect to existing issues
Screenshot einer Projektübersicht

How to customize delivery progress

Once your delivery tickets are connected, a progress bar will appear that reflects the statuses of your connected issues. You can choose to estimate progress based on issue count or story points that have been set in Jira Software.

To customize delivery progress and statuses:

1. Click into any idea and click the Delivery tab in the idea panel

2. Click the progress bar and select Configure delivery progress

3. Choose the estimation type (default or simple) and the estimation value (issue count or story points). Note that your Jira Software project must be company-managed to estimate progress based on story points.

View our documentation for details on estimation types and estimation values.

How to visualize delivery progress in views

With your delivery tickets connected, you can also create views specific to delivery progress by adding certain fields that are calculated based on the Jira Software epics and issues linked to the idea:

  • Delivery status - displays the delivery status for the idea, which is calculated based on the number of issues per status or the number of story points per status
  • Delivery progress - displays the delivery progress bar for the idea, which is calculated based on the number of issues per status or the number of story points per status

You can also add extra information like Due date, Assignee or Team.