Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-37

Console: Customer Happiness (RFEs) for 4.13

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Critical Critical
    • openshift-4.13
    • None
    • UX
    • BU Product Work
    • False
    • 0% To Do, 0% In Progress, 100% Done
    • 0

      Feature Overview

      Console enhancements based on customer RFEs that improve customer user experience.

       

      Goals

      • This Section:* Provide high-level goal statement, providing user context and expected user outcome(s) for this feature

       

      Requirements

      • This Section:* A list of specific needs or objectives that a Feature must deliver to satisfy the Feature.. Some requirements will be flagged as MVP. If an MVP gets shifted, the feature shifts. If a non MVP requirement slips, it does not shift the feature.

       

      Requirement Notes isMvp?
      CI - MUST be running successfully with test automation This is a requirement for ALL features. YES
      Release Technical Enablement Provide necessary release enablement details and documents. YES

       

      (Optional) Use Cases

      This Section: 

      • Main success scenarios - high-level user stories
      • Alternate flow/scenarios - high-level user stories
      • ...

       

      Questions to answer…

      • ...

       

      Out of Scope

       

      Background, and strategic fit

      This Section: What does the person writing code, testing, documenting need to know? What context can be provided to frame this feature.

       

      Assumptions

      • ...

       

      Customer Considerations

      • ...

       

      Documentation Considerations

      Questions to be addressed:

      • What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
      • Does this feature have doc impact?  
      • New Content, Updates to existing content,  Release Note, or No Doc Impact
      • If unsure and no Technical Writer is available, please contact Content Strategy.
      • What concepts do customers need to understand to be successful in [action]?
      • How do we expect customers will use the feature? For what purpose(s)?
      • What reference material might a customer want/need to complete [action]?
      • Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available.
      • What is the doc impact (New Content, Updates to existing content, or Release Note)?

            Unassigned Unassigned
            amobrem Ali Mobrem
            Yufen Chang Yufen Chang
            Olivia Payne Olivia Payne
            Rick Wagner Rick Wagner
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: