NOVUS Fit Assessment Tool Concept Wireframe Challenge

Welcome to the NOVUS Feature Identification Tool (FIT) Assessment Tool Wireframe Challenge! For this challenge, we are looking for your help to come up with a wireframe concept that will support an assessment and design phases of the Feature Identification Tool.

We need to see intuitive, elegant and easy to use wireframe concepts that will let us design and build the final web-based user interfaces on the next stage of this project. Think about what are the best UI/UX practices when creating this wireframe.

Round 1

Submit your initial wireframes for checkpoint review. Feel free to add any screens which are necessary to explain your concept.

1. Login
2. Dashboard
3. Assessment Management (all screens under this item)

Round 2

Submit your final wireframes plus checkpoint feedback implemented. Feel free to add any screens which are necessary to explain your concept.

Background

The Business Architecture (BA) Practice plays a pivotal role in continuing to fuel the momentum by developing new and innovative ways for business and IT teams to work and communicate with one another.

One of the team's key focus areas has been to reduce the amount of friction and inefficiencies associated with translating and scoping the business vision for a project into discrete people, process and technology impacts.

By giving teams a common language to communicate with, this allows the company to rapidly and efficiently take any business idea and understand the required changes to the company's people process & technology to make it a reality.

The goal of this project is to build an app to be accessed over the web using a desktop browser. This FIT tool app will provide the delivery teams a consistent methodology to aid with the upfront assessment and scoping of a project.

Existing App
The existing application of the client is made of an Excel file with several sheets in it. The creation of an assessment will go through several process/sheets. The following screen shots are from the existing Excel solution, and should only serve as a guide for how data is collected today. As you work through your design, explore ways to interact with the data that goes beyond Excel and uses the assortment of interactions available on the Web.

1. Cover Page
   - This holds the basic information of the assessment concept
   - The Document Owner will be the name of the user who creates the assessment. For the new app, this should be automatic based on logged in user and the field will not necessarily show in the form.
   - The Concept Name will list available options based on third-party service (AgileCraft)
   - Concept Description will be populated from AgileCraft based on the selected Concept Name
   - Product Objectives are also coming from AgileCraft based on the selected Concept Name

2. Scope Impacts
   - This will be identifying project scope impacts
   - Users will select Actors, Products, and Channels
   - For each Actor, Product and Channel, the available impacts to choose will include “None”, “Change”, “Test-Only”, with “None” being the default value
   - Each Actor, Product and Channel should have a description available for a user to view. The current version of the Excel app displays this information when you double-click, however in the new app we would like to display this information by either mouse hover or other intuitive way of showing information

3. Experience and Back Office Impacts
   - This will be identifying the (1) Life Cycle Stage, (2) Scenarios, and (3) Scenario Elements
   - A User will be able to select one or more lifecycle stages with thedefault state being not selected
   - When a User selects a Lifecycle Stage, its corresponding Journey Scenarios will appear
   - When a User selects a Journey Scenario, its corresponding Scenario Elements will appear
   - Each scenario element displayed should indicate which selected journey scenario(s) caused that scenario element to appear.
   - The user will then be able to select each of the scenario elements, with the default state being not selected
   - Once the scenario element is selected the user should be able to select Change, or test only impact
   - Note that there are more life cycle stages than what’s currently showing in the screenshot
   - Each Lifecycle Stage, Journey Scenario, and Scenario Element should have a description available for a user to view. The current version of the Excel app displays this information when you double-click, however in the new app we would like to display this information by either mouse hover or other intuitive way of showing information

4. Feature
   - Based on the selected options in Experience and Back Office Impacts, this sheet will display all possible Scenario Element to Capability pairs
   - From here, users can include or exclude certain Scenario Elementto Capability pairs
   - Exclude means they are not doing anything with that Scenario Element to Capability pair
   - After including and excluding Scenario Element to Capability pairs, users will now select different selected Scope Impacts fromthe previous sheets for each Included Scenario Element to Capability pair. For each included Scenario Element to Capability pair, users should be able to select one or more of the previously identified “Actors”, “Products” and “Channels”
   - The Product Objective options will be based on what entered the Cover Page sheet
   - For each Scenario Element to Capability Pair, users should be able to select one or more Product Objectives
   - User will then enter or define the Feature Name and Feature Description
   - User shall be able to create, update and delete named Product Bundles (which are “containers” that hold one or more Features)���User shall be able to view a list of bundles, features associated with those bundles, and unassociated features
   - User shall be able to manage association of bundles and features

5. Feature Summary
   - This sheet displays the summary of all the “included” features organized by Lifecycle Stage and Journey Scenario based data collected from the previous sheets

6. App Impacts and LOE
   - Here, it will also display the previously selected features (ProductObjective, Product Bundle, Feature Name, and Feature Description)
   - This sheet helps to identify Level of Effort (LOE) impacts for each feature
   - App field will be dropdown options driven by the capability to application relationship. In the new app, we want this to be able to select multiple applications, and then each application would have its own associated Delivery Group and LOE.
   - Impact Type options are None, Test-Only, Config, and Dev
   - User then needs to enter the value for Impact Descriptions, LOE (Hours), LOE ($), and LOE Notes
   - Other fields are initially populated from the Features screen

7. Control Impacts
   - Controls are displayed based on included Scenario Elements and Capability pairs from (4)
   - Other fields are displayed based on the previous screens
   - The user should be able to include/exclude which controls apply

8. Impact Summary
   - This will display the summary of impacts based on the selected options from the previous screens

9. LOE Summary
   - This will display the summary of Level of Efforts based on the selected options from the previous screens (by Bundle and by Feature)

Assessment Flow Notes

• Administrators and Owners should be able to create an assessment
• ���Once an assessment is created, the administrator or the owner should be able to manage the users of the assessment
• There should be settings to mark the assessment as “Dark”
• If the assessment is marked as Dark, it means that it will be viewable/accessible only by the admin, assigned owner, assigned contributors, and assigned LOE-Only contributors
• Different users assigned to this assessment can manage/update the assessment depending on their role
• Submit to AgileCraft. Only Admin or the Owner can submit to AgileCraft

User Roles

1. Administrator
   - this will be the creator/edit of an assessment and all model meta-data
   - this role has all the capabilities

2. Owner 
   - this will be the creator/edit of an assessment

3. Contributor
   -  this will be the view /edit of an assessment

4. LOE-Only Contributor
   - this will be the view /edit of an LOE 

5. Read Only
   - this will be a user role that can only view an assessment.

Note: see the provided diagram for the complete details of different user roles. All users (except the Administrator) share or can assume a particular role.

Required Screens

The following are the required screens, make sure to consult the Role’s UI flow diagram for different user roles in each screen below.

1. Login
   - This screen will be a unified login page for all the users

2. Dashboard
   - The Dashboard displays will depend on the user’s role mentioned above

3. Assessment Management

   1. Create Assessment

   2. View Assessment

   3. View History

   4. View Assessment - Historic

   5. Edit Assessment

   6. Edit Level of Effort (LOE)

   7. View LOE Summary

   8. View Feature Summary

   9. Edit Notifications

   10. Submit to AgileCraft

4. Assessment User Management

   1. Search for users

   2. Assign user and roles

   3. Remove users

   4. Edit role

5. Assessment Model Management

   1. Select Model

   2. Manage Models

   3. Load Bulk Data

   4. Publish Changes to new Assessments

   5. Notify users

Note: You are not limited to these screens, you are allowed to create new ones or merge several screens where it makes sense. We are open to your suggestions. Also, do not replicate/copy the attached screenshots. We need better flow and user experience.

Target Device

• Desktop (all OS)
  Browsers: Chrome and MS Edge

Target Users

• Client’s teams and staffs

Tools :

- We are asking to work with Axure: http://www.axure.com/support

- You can also work with static images but you must include a fully navigable prototype in HTML.

- If you are designing in the sketch or Adobe XD then it is mandatory that you create the flow using MarvelApp as we are expecting to see a clickable wireframe in this challenge.

- You are also allowed to submit pure HTML wireframes

 

Judging Criteria

- User Experience of the application

- Completeness and accuracy of your wireframes

- How well your wireframes provide a consistent user flow

Submission & Source Files

Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission File
Wireframes should be built in HTML or Axure

Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.
 

Final Fixes

As part of the final fixes phase, you may be asked to modify content or user click paths