The objectives for the user backlog requirements analysis task are listed below.
· Categorize and prioritize current request backlog as to size, scope and type
· Uncover hidden or inappropriately assigned requests
· Assess qualitative functional attributes of current application
· Determine current maintenance support requirements
The entrance criteria for the user backlog requirements analysis task are listed below.
· Completion of objective setting/proposal development task
· List of current system request backlogs
· Access to system logs indicating system performance attributes, system failures and change requests
· Access to IS project (or other) management to provide personnel and related support information for system
Optional:
· Populated LTM model as completed in entrance criteria task - requires system and sub-system object instance population
The personnel and skill requirements necessary to meet the user backlog requirements analysis task objectives are identified below.
· Redevelopment Expert
- Ability to plan and execute requirements backlog analysis
- Ability to perform user/system SME interviews and assimilate results
- Basic repository update skills
· Current Systems Expert
- Knowledge of current technical backlog and estimates
- Knowledge of current functional backlog and estimates
· Target System Functional Expert
- Knowledge of strategic application requirements
· User Requirements Analyst
- Knowledge of short and long-term system requirements
· Metric Analyst
- Ability to assess & record architectural metrics
The system components and related inputs required to initiate and complete the user backlog requirements analysis task are listed below.
· Blank copy of Functional Assessment Form 005-1
· All existing system backlog request lists or related logs
· Historical log of change requests completed over the past two years (or whatever period is available)
· System logs indicating performance statistics, system failures and related information
· Personnel information regarding the systems support team for the system(s) being assessed
Technologies supporting the user backlog requirements analysis task include open systems repository, project management, spreadsheet, and word processing tools. These tools are used to represent information as required by this task.
Open systems repository
A repository provides an important, yet optional, capability to link business areas, systems and components using the legacy transition meta-model (LTM). In this task, the repository is used to establish relationships between system components and a backlog request If change requests are loaded into LTM during this analysis, a process should be established to maintain those requests post-project.
Project management tool
Tool support for this analysis task includes change request project planning and management capabilities. This includes the ability to depict hours, roles, deliverables and dependencies.
Project planning tools are not an absolute necessity for this task.
Spreadsheet
This tool is used to record metric results for this task and, optionally, as a way to track, categorize and summarize backlog requests.
Word processor
This is required to record analysis results.
The user backlog requirements analysis task is comprised of the following task steps:
