If you’ve got ideas about how we can make our products work better for you, don’t keep them to yourself. Novell’s product teams are always looking for ways to enhance our products, and many good ideas come from product users like you.

There’s a place you can go enter these suggestions. Just go to the Novell Requirements Portal (http://www.novell.com/rms) and follow the instructions.

Don’t be shy! This is a great way to make your wishes known.

What to Expect
Novell sincerely appreciates product feedback and ideas. Please note that most Novell product development lifecycles often last 6 – 18 months. Features and functions are often locked down well in advance. At the same time, Novell uses an iterative approach to development in many product areas. For these reasons, the timeframe for status updates to requests submitted to Novell will vary.

Use the New button to submit items. Use My Product Requests to see a list and high level status of submitted items. Use My Requirement Subscriptions to manage e-mail subscriptions for updates.

Please refer to content guidelines for examples on creating effective request submissions.

Content Guidelines
Please use ENGLISH when entering requests.

Capturing adequate detail in a requirement request is very important for Novell’s product management teams. The typical content of a good request would include the description of functionality in the context of a particular role for the purpose of achieving a benefit.

Often, the best way to write that requirement is to define it the form of a user story. Here is an example framework that is simple but yet effective.

As a {describe the role} I would like {describe the feature/enhancement} so that I can {describe the business or technical goal}…

Another approach might be to create a service-oriented problem statement. Here is an example:

Our enterprise environment consists of 1500 servers deployed throughout our organization worldwide. Our IT staff is centrally located at our corporate headquarters and must be able to securely monitor and manage all corporate servers without direct access to the server console.

Business considerations used in our decision include but are not limited to interoperability with our existing system management solution, workstation platforms used by administrators, access control and role enablement, and latency for remote locations in emerging markets.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Categories: Uncategorized

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

Leave a Comment

  • jlodom says:

    I currently have several enhancement requests in the queue to different teams, and I imagine that various product teams do have different workflows and therefore different ways of managing enhancement requests. However, it would be valuable if you could comment on the various status messages we might get once Novell has an opportunity to look over our requests.

    Specifically, what precisely do the following mean organizationally, and what steps in the product cycle do they correspond to:

    “Queued for Development”
    “Awaiting Release Prioritization”
    “Product Management Review”

    Thank You!

  • ssalgy says:

    Status Definitions

    Awaiting Release Prioritization: Identifies a requirement that has been pushed to a target system for work or is simply under review by product management trying to decide next steps.

    Duplicate: Identifies a request that has been determined to be a duplicate of an existing request.

    Implemented: Identifies a request that is now available in a product release.

    Need Info: Requirement needs a clarification or more information from the submitter.

    Product Management Review: Identifies a request that has received some level of review but is waiting for Novell product management to make the next decision on its status.

    Queued for Development: Identifies a request that has been accepted and is either pending assignment or assigned to a current development project. DISCLAIMER: This status is subject to change at any time during the development lifecycle as scope, schedule, and resources decisions are made by Novell.

    Rejected: Identifies a request that has been turned down for further review by Novell.

    Unconfirmed: Identifies a request that has been submitted but not yet reviewed by Novell. This is the default status for all newly created requirements.

By: ssalgy
Mar 7, 2011
11:05 am
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management IT Security Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Supported Troubleshooting Workflow