Gap Analysis and Feature Ranking 2019
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Gap Analysis/Feature Ranking 2019 Instructions
2
Please watch this video recording of the Gap Analysis/Feature Ranking instructions
3
4
Overview
5
The purpose of the Gap Analysis/Feature Ranking is described in the FOLIO wiki.
6
Before starting the process, following the steps below, please familarize yourself with the worksheets that make up this spreadsheet (see "Spreadsheet Contents" section.)
7
Please note that this one spreadsheet will be updated by all participants of the Gap Analysis/Feature Ranking.
8
Because of this, you should not delete columns/rows/worksheets. Do not use filters to change your view of the spreadsheet as this will change the view for everyone.
9
Please make your own copy if you want to make a personalized version:
10
* Download this Google sheet as a Excel spreadsheet by selecting "File", then "Download as", then "Microsoft Excel (.xlsx)"
11
* You will notice that the .xlsx file has a cell wrapping issue--fix this by selecting the entire spreadsheet (clicking in the upper left hand corner) and then double clicking on the line between two row numbers that are bad
12
* Instructions with pictures are available at https://docs.google.com/presentation/d/1qKQkDG5XoiiXctZBKZsZsze259fv7UQc1KmksvGY35g/edit?usp=sharing
13
* Do not delete the "Ranking Options" tab as this is how the RANK drop-down options are populated--you will also want to leave the INSTRUCTIONS tab
14
* Someone at your institution will need to enter the Excel spreadsheet values into the Google spreadsheet
15
16
Spreadsheet contents
17
WORKSHEETPURPOSECRITERA FOR INCLUSIONSORT ORDER
18
Open FeaturesThis worksheet contains all features that have notJIRA Project=UXPRODBy JIRA Issue Key within Fix Version within Epic
19
(provided for you to update with you institution's
yet been completed--in most cases they are notIssue Type=New Feature
20
priorities)started beyond screen mock-ups. These are theStatus not = Closed or In-Review
21
features you need to rank for your institution.Fix Version not = Q4 2018 or Q1 2019
22
Label does not contain NFR (Non-Functional Requirement)
23
24
Planned for Bellis Release
This worksheet contains features planned for the
JIRA Project=UXPRODBy JIRA Issue Key within Fix Version within Epic
25
(provided for informational purposes)
Bellis (aka Q1 2019) release that we are working on
Issue Type=New Feature
26
right now. Some of the features are completed and
Fix Version = Q1 2019
27
can be demoed in the test system. These features
Label does not contain NFR (Non-Functional Requirement)
28
do not need to be ranked because they are
29
already being worked on and will not benefit from
30
ranking at this late date.
31
32
Available in Aster ReleaseThis worksheet contains features that have beenJIRA Project=UXPRODBy JIRA Issue Key within Fix Version within Epic
33
(provided for informational purposes)completed in releases Q1 2018 through Q4 2018Issue Type=New Feature
34
(aka Aster Release). These features are available for
Status = Closed
35
demoing in the Q4 2018 instance set up by Indexdata.
Fix Version = Q4 2018
36
These features do not need to be ranked because
Label does not contain NFR (Non-Functional Requirement)
37
they have been completed.
38
39
Non-Functional RequirementsThis worksheet contains features that have beenJIRA Project=UXPRODBy JIRA Issue Key within Fix Version within Epic
40
(provided for informational purposes)
labeled as "non-functional requirements" (aka NFRs).
Issue Type=New Feature
41
These are features that don't need to be rankedLabel contains NFR (Non-Functional Requirement)
42
because they will be completed when needed,
43
regardless of rank.
44
45
Missing Features
This worksheet is where you should record any missing
Blankn/a
46
(provided for you to document missing features
features you discover during the Gap Analysis that your
47
needed for your institution to go-live)institution needs to go-live.
48
49
Bugs FoundThis worksheet is where you should reportBlankn/a
50
(provided for you to report bugs if you come
any bugs you may discover when you are using
51
across some)one of the FOLIO demo sites.
52
53
Video QuestionsThis worksheet is where you should ask anyBlankn/a
54
(provided for you to ask questions about the
questions you may have after watching the
55
product owner videos clips)product owner videos clips.
56
57
Ranking OptionsThis worksheet contains the values used for the n/aRandom
58
(used internally by this spreadsheet)
ranking drop-down menu. Please do not touch this
59
spreadsheet.
60
61
Recommended Steps
62
1. Prepare the "Open Features" worksheet for your institution
63
* If you completed the 2018 Gap Analysis you will have a column containing your institution's rankings from that exercise, which you may elect to update now.
64
* If you are new to the Gap Analysis process, scroll to the right of the worksheet to see if a new column has been inserted for your institution--if not, rename one of the "Rank: <institution> - <install type>" columns.
65
* If your institution is considering an ERM-only installation, label the column as such--feel free to have two columns, one for a full install and one for an ERM-only install (see Leipzig as an example, they have both a "Rank: Leipzig - Full" column and a "Rank: Leipzig - ERM-only" column.
66
2. Set up a team at your institution for a particular functional area.
67
3. Determine which features each "team" at your institution will be responsible for--the best approach may be to divide up the work by Epic.
68
4. Watch the video clip(s) provided by the appropriate product owner(s) for your team's area of responsibility.
Note: Video clips may not exist for everything!
69
(Ask any questions your team may have in the worksheet tab titled "Video Questions")
70
5. Start with the Feature Ranking portion of the exercise, following the "Feature Ranking Details" provided below.
71
6. Then move on to the Gap Analysis component, , following the "Gap Analysis Details" provided below, recording missing features as you discover them.
72
7. When you are done, let the Product Council member from your institution know that your team has finished the assignment.
73
74
Feature Ranking Details
75
1. Review the features in the "Open Features" tab that have been assigned to your "team."
76
2. In the column for your institution, indicate if the feature is needed by your institution to go-live, or can wait up to a quarter or year after going live, can wait until fiscal year rollover, or is not needed by your institution.
77
(we purposely have not included an option before go-live--we know that you need time to test. If you need a feature before go-live for a reason other than testing, please right click in the ranking cell and select "Insert comment.")
78
3. If you need more information about the feature than what is provided in the "Summary" column, click on the UXPROD link in the "JIRA Issue" column to open the JIRA issue.
79
4. If the JIRA issue does not provide enough information, click on the "Comment" button while viewing the JIRA issue to ask the feature's Product Owner a question.
80
(your FOLIO JIRA login is the same as your FOLIO wiki login--if you don't have a JIRA/Wiki account go to issues.folio.org and click on the "Sign up" link)
81
5. In your institution's column, select the appropriate RANK (aka "feature needed by") value from the drop-down menu.
82
* We recognize that your institution needs time to test each feature/function and the appropriate amount of time will be provided.
83
* Please do not provide a blanket "go-live" response if there is a feature/function that can wait a bit or you don't need.
84
* If you need to provide additional information related to your RANK response, right click in the cell and select "Insert comment."
85
* Please do not ask questions via Google's "Insert comment" feature--instead use JIRA's "Comment" button.
86
87
Gap Analysis Details
88
1. Compare the requirements that your institution has defined to what has been developed for FOLIO so far by testing features in the Q4 2018 Release.
89
Use this demo site:http://folio-q4.aws.indexdata.com/
(The features in this release are also listed in the "Available in Aster Release" worksheet)
90
2. For institution requirements not found in Q4 2018, look at the features in-progress or completed for the Q1 2019 (aka Bellis) Release--scheduled for April 8--as presented in the "Planned for Bellis Release" worksheet.
91
Some of the features are completed, or partially completed, and can be checked out at a demo site right now. Please follow these directions:
92
a. Click on the UXPROD link in the "JIRA Issue" column to open the JIRA issue for the feature.
93
b. If the JIRA "Status" field is "Closed" and the "Resolution" is "Done" you should be able to check out the feature on one of the demo sites.
94
Try this demo site first:http://folio-snapshot-stable.aws.indexdata.com/
95
If feature not there, try this demo site:http://folio-testing.aws.indexdata.com/
96
If not at either site:Try again in a day or two
97
c. If the JIRA "Status" field is NOT "Closed", there may still be parts of the feature that are completed--if not code then perhaps a user story with a screen mock-up.
98
Look at the non-UXPROD issues that are linked to this issue (see the "Linked Issues" section of JIRA issue)--the linked issues that have a square green icon are user stories.
99
* Completed stories will result in code be available to demo at one of the two demo sites listed above (folio-snapshot & folio-testing).
100
* Stories that are not completed are still useful in that they provide screen mock-ups and details about the feature.
Loading...