User Story: As Portal user, I need to understand whether I file a Security Incident or an IT Issue so I can submit the correct form and have my problem addressed.

User Story: As a Portal user, I need to be able to select my preferred date format, so that I can view dates in the format I am accustomed to.

User Story: As a Portal user, I need a visual way to understand when I'm about to select something.

As a Portal user, I need to understand what my options are for specific services and solutions so that I can choose the right tool and solution for me.

User Story: As a Product Manager, I want the ability to cycle through different homepage backgrounds to provide surprise and delight for users.

Assessment: 40 points
User Story: As a Product Manager, I need to know all pages being viewed in Portal so that I can build a report to understand which pages are being frequented and which are not.

User Story: As a Product Manager, I need to know which record producer items (incidents, change requests, and ideas) are being submitted in Portal so that I can build a report based on the data to determine usage.

Assessment: 58 Points
User Story: As a Product Manager, I need to know which catalog items are being viewed in Portal so that I can build a report based on the data to determine engagement.

User Story: As a Product Manager, I need create a better user experience for the front-end Portal user by configuring the backend of the Add New Delegate Form.

User Story: As a Portal user with correct permissions, I need to be able to add a new Delegate so I can ensure that user can approve requests on behalf.

User Story: As a Portal user with correct permissions, I need to see who I am a Delegate for and if there are any outstanding Approvals that require my action.

User Story: As a Portal user with correct permissions, I need to see all my active Delegates so that I can review and perform actions as needed.

User Story: As a Portal user with correct permissions, I need to see all my non-active (expired) Delegates so that I can review and reactivate as needed.

Assessment: 29 points
User Story: As a Product Manager, I need to know what knowledge content is being viewed in Portal so that I can build a report based on the data and add or remove content based on usage.

PM - 2 High 
Sprint - 12/15-01/09: Pending Release
STRY0022359

User Story: As a Portal user, I need to be able to change my preferred language to Latin American Spanish in My Account, so that the entire site is changed to Latin American Spanish.

User Story: As a Portal user, I need  to understand when I'm about to select a single link for content.

User Story: As a Portal user, I need a visual way to understand when I'm about to select an icon.

User Story: As a Portal user, I need a visual way to understand that an object is selectable so I can click on it. 

User Story: As a Portal user, I need a visual way to understand my options for removing items from my shopping cart.

As a Portal user, I need icons and text that have hover states to be selectable so that I understand I can click on them.

User Story: As a Portal user, I need to understand which item I am selecting in the header by having a hover state appear when I hover over specific text. 

User Story: As a Portal user, I need the interactions on the Portal to be consistent so I understand how to interact with all the elements on each page. 

User Story: As a Portal user, when I hover over the home icon, then I need to icon to change it's hover state so I understand that I'm about to select it. 

User Story: As a Portal user, when I hover over an object I expect to be able to click on it and if it is not clickable then it should not have a hover state to avoid confusion. 

2 - High will be placed in the next sprint as a priority over other stories. If there are multiple 2-High stories we will use the first in, first out model where points allow.

3 – Moderate will be placed in the next available sprint, after the 2 – High stories are scheduled.

4 – Low these stories will be in the backlog and placed in a sprint as points allow.

Goal: Currently, when a new knowledge article is created, there are two columns created by default. One column for the actual article and one column for the "Published/Helpful," widget. We want to remove the second column, expand the first column and move that widget to below the knowledge article itself so we have more horizontal space for articles. 

Questions to be answered as a result of this SPIKE:
- Do we get more horizontal real-estate space for articles if we remove the second column?
- Can we move the "Published/Helpful," widget beneath the article? 
- Does reducing two columns to one larger column meet our needs for future articles and for building Solutions & Services pages?