Details

    • Feature
    • Resolution: Obsolete
    • Critical
    • None
    • None
    • GRC
    • None
    • False
    • None
    • False
    • Not Selected
    • 83
    • 83% 83%

    Description

      h1. Feature Overview

      • This feature covers all aspects of ACM and OLM integration.

      h2. Goals

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

      h2. 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

      h2. (Optional) Use Cases

      This Section:

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

      h2. Questions to answer

      • ...

      h2. Out of Scope

      h2. 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?

      h2. Assumptions

      • ...

      h2. Customer Considerations

      • ...

      h2. 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 a 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)?

      Attachments

        Activity

          People

            rhn-support-cstark Christian Stark
            rhn-support-cstark Christian Stark
            Derek Ho Derek Ho
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: