IBM - Cloud, PowerVS and Ceph aaS - Structured Ideas

This portal is to open public enhancement requests. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

Add a new idea Subscribe
Status Not under consideration
Workspace * IBM Cloud Ideas
Categories DevOps
Created by Guest
Created on Sep 8, 2025

RELATED IDEAS

Implement an approach to define and manage Requirements record Acceptance Criteria for IBM DevOps Plan

An Agile requirement comprises (or SHOULD comprise!) a high-level statement of what the system needs to do, plus one or more related, detailed scenarios that define system Acceptance Criteria for the high-level statement.  The AC's provide the requirements details.  Most Agile requirement tools, including the default implementation for DevOps Plan, manage only the high-level statement "well".  I've previously defined an approach using IBM ELM for managing both aspects of Agile requirements.  This is described in the accompanying file.  Motivating narrative can be found in my Blog entry: https://elmwatsoniot.wordpress.com/2019/07/03/how-to-effectively-author-manage-and-reuse-work-item-acceptance-criteria-using-elm/. A similar capability can be implemented for DevOps Plan using a Package that provides a new record type for Acceptance Criteria and a custom link type to associate Epic, Feature, or Requirements records with Acceptance Criteria.

doors-next-as-a...
doors-next-as-a...
doors-next-as-acceptance-criteria-manager_2021.pdf
 doors-next-as-acceptance-criteria-manager_2021.pdf
Open full size
doors-next-as-acceptance-criteria-manager_2021.docx
 doors-next-as-acceptance-criteria-manager_2021.docx
Open full size
doors-next-as-acceptance-criteria-manager_2021.pdf doors-next-as-acceptance-criteria-manager_2021.docx
Idea priority Medium
Needed By Not sure -- Just thought it was cool
  • Admin
    Manish Tiwari
    Sep 15, 2025

    Hi @Todd Dunnavant, as discussed over slack, kindly submit this idea in the workspace for IBM DevOps plan. Thanks!

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.