Documentation
SolutionDeveloperComplianceProjects
  • Introduction
  • Gitbook Guidelines
  • PRELIMINARY ANALYSIS
    • Project Initiation
    • Business Goals
    • Information Analysis
    • Solutions Evaluation
    • Risk Assessment
  • APPLICATION DEVELOPMENT
    • Scrum Framework
      • Scrum Values
      • Scrum Roles
      • Scrum Compliance
    • User Requirements
    • Product Backlog
      • User Story
      • Story Mapping
      • Grooming
      • Roadmap
      • Best Practice
    • Sprint Planning
      • Planning Inputs
      • Task Definition
      • Task Sizing
      • Sprint Backlog
      • Best Practice
    • Sprint Execution
    • Sprint Review
    • Sprint Retrospective
    • Process Control
      • Sprint Burn-Up
      • Sprint Burn-Down
      • Sprint Velocity
      • Source Control
    • Risk Assessment
      • Data Privacy & Security
      • Postpone the release
      • Lack of participation or engagement
      • Incomplete backlog items
      • Project Scope Creep
      • Third-Party Dependency
      • Integration Issue
      • Outdated Technology
      • Budget & Time Constraints
      • Inadequate Testing
    • User Acceptance
    • Release and delivery plan
    • Literature
  • SERVICE MANAGEMENT
    • Service Lifecycle
    • Receiving Ticket
    • Ticket Management
      • Maintain Attributes
      • Ticket Assignment
    • Troubleshooting
    • Escalation
    • Monitoring
    • Evaluation
    • Risk Assessment
      • Support and Maintenance
      • Insufficient information
      • Misinterpretation of attributes
      • Insufficient Testing
      • Delayed deadline
      • Lack of continuous improvement
      • Lack of Stakeholder involvement
  • REVIEW & IMPROVEMENT
    • Dashboard Analysis
Powered by GitBook
On this page
  1. SERVICE MANAGEMENT

Evaluation

PreviousMonitoringNextRisk Assessment

Last updated 1 year ago

  1. Goals

The last step of the Application Maintenance process is evaluation. A corporate technique known as "improvement evaluation" involves reviewing and updating your organization's procedures, methods, and practices. Increasing the precision and efficiency of company processes is the aim of this process. EA team and the manager are responsible for this step of the process. They are gathered together to decide how to improve the overall process after the monitoring step.

(comparative agility,n.d.)

2. Scope

Working instruction covers enterprise application employees in Europe.

  1. Responsibility

  • EA team: It participates in the evaluation of the process.

  • Manager: He can analyze and monitor the ticketing process. Together with the team decide what changes they will make in order to improve their work.

  • User: He uses the knowledge base to solve his tickets.

  1. Process

In this step, the team will gather the information from the monitoring process, and it will store the improvement ideas in the knowledge base. The scrum team will use this to improve themselves and the process behind it. Also, the client can use this knowledge base to solve their tickets with the information available.