Module 2 KOSIN Advanced 1 English Version

KOSIN - 更新
Module 2: KOSIN Advanced 1

Plan:
1. KOSIN training & implementation Plan

2. Introduction JIRA / KOSIN
3. Productive / Non Productive tasks
4. Type of tasks / subtasks
5. Create tasks in JIRA
6. JIRA Workflow
7. Assign a task & Work log-ETC
8. JIRA Plugins & integration
9. DEMO
10. Materials & documentation
Plan:

6. JIRA Workflow
9. DEMO
1
These are the modules dedicated to the CSD and CLD category, and it covers the following points:
Module 2: Module 3: Module 4: Module 5:

KOSIN – Risk KOSIN – Dashboard
KOSIN Advanced-1 KOSIN Advanced-2 Management
•Introduction JIRA / •Defects; •Risk / Problem •Dashboard and
KOSIN •Doubts; management; filters;
•Productive / Non • Change request; •Create / close risk / •Dashboard creation
Productive tasks Issue in Jira; and management;
•Type of tasks / •Track the Risk / •Search for Tasks /
subtasks Problem; Subtasks;
•Create tasks in JIRA •Query / filter
•JIRA Workflow management;
•Assign a task & Work
log-ETC
•JIRA Plugins &
integration
2
Plan:

6. JIRA Workflow
9. DEMO
3
Principal characteristics of JIRA
JIRA allows the management of issues or tasks (Development, corrective, supports, changes, risks, etc.),
having defined workflows for this.
In addition, it is integrated with other UMANE and development tools.
Traceability and
Workflow Control of estimated effort
centralization of activity
Tailor-made searches Agile Dashboards Dashboards for monitoring
4
2. Introduction JIRA / KOZIN
Alarmas
Producción
Modules
KOSIN Auditorias
Gestión de
Servicios
KOSINDM KOSINCT CTS OneSight

Centers Tools
Model Jira KOSIN Services People Quality Tools Suite model Reporting PowerBI
KOSIN
Definition of
Services and
characteristics Center Specific tools
of personnel People Dashboards
Waterfall / collaboration management PPB: Statistical PPM: Predictive Centers & Production
Agile analysis of MTT/MTO Services /
Híbrido between and indicator tool Indicators
indicators
Billing Centers Projects
offices assignments
to Services (Invoicing)
through
Groupings
5
Plan:

6. JIRA Workflow
9. DEMO
6
Work model in JIRA-KOSIN
Work model 1 Planning Tool 7
NON-operational work 2 Operational work 3 Management items 4
Imputable to the project Development Risks
Management incidents
NO imputable to the project Corrective
Problems
Inoperativity Support
Management changes
Breakdown Incident Scope Doubt
by activity registration changes management
Dashboards, Filters and Panels 5

7 CMDB 6
Plan:

6. JIRA Workflow
9. DEMO
8
NON- operational tasks :
Non-operational tasks will be divided into 3 types of requests which cover all the real needs for non-operational work.
Tasks
Imputable to the project NO imputable to the project Inoperativity
Client management
Vacations
Financial management
Legal absence
Subtasks
Team management
Holidays Unavailability
Infrastructure management
Illness
Strategy management
Training not billable to the project Availability
People
Collaborations
Internal Training
Internal compensations
Interns
(más información en las siguientes slides)
(more information in the following slides)
Some characteristics of these tasks are:

▪ They are automatically generated when the project is registered in the tool. No actions need be taken on them.
▪ They are global and so involve all team members.
▪ Requests must be kept alive throughout the life of the project/service.
▪ If the volume becomes very high, they can be closed and new identical requests opened (for example, annually). Opening new requests is
automatic, so the user does not have to spend time on this task.
9
Subtasks billable to the project
There will be a ‘Project-billable’ work request: Non-operational activities but which would be charged to my project's
charge account.
Subtasks Description
Relationship with the client, according to the established relationship
Client management model, and which cannot be charged to any request (for example,
committees with client...).
Financial management Economic monitoring of the project.
Team management, capacity, global planning, internal meetings,
Team management
resizing,...
Infrastructure Infrastructure management for proper project management: UMANE,
management IT, posts.
Project quality assurance: Management standards, audits,
Strategy management
improvement plan...
Activities related to team members’ career management: Annuals,
People
Reviews, Mentoring, Supervisor Evaluation, ...
Collaborations with other projects outside our own without charge
External collaborations
account.
Internal Training Knowledge management and transfer within the team.
Interns Time spent by trainees or interns.
10
Subtasks not billable to the project
There must be a request for 'NON project-billable' work: Non-operational activities for which the charge account is
different from our project.
Vacations Holidays and days off.
Legal absence Legal absences.
Holidays Holidays.
Illness Illness, sick leave and medical visits.
Training not billable to the Training with a different charge account from the project’s. For example, training
project at the everis University.
Collaborations Hours spent on collaborations with other projects with charge account
Hours that do not represent actual work, but are used to complete a day when
the person in charge compensates these hours for extra work done on another
Internal compensations
day.
Also, time for recoverable absences.
11
Inoperativity :
There must be an 'Inoperativity' work request: Activities in which, for one reason or another, I cannot work, regardless of
whether my project is the cause or not.
Tasks to book the hours of downtime due to external problems such as power
cuts, network failures, equipment problems, and the like, that prevent work
Unavailability
from being carried out. Provided it is not caused by the client's infrastructure
and cannot be billed to them.
Availability Tasks to book the hours for lack of work caused by having no assigned tasks.
12
Within each type of task, there

are more detailed sub-tasks to be
achieve like
13
Operative tasks :
➢ All operational requests of the project/service must be registered.

➢ The different types of requests are:
Development / Evolutive Corrective Support
Adaptation actions needed to keep the

applications operational by providing the new
functionalities required by the evolution of
A set of activities to diagnose and correct
the business they support and to prevent
errors in the software, found by the users of
their obsolescence
the applications or by the maintenance team.
Errors can range from functionality failures
A distinction will be made between MINOR Advice and support activities for queries from
and performance problems, to problems that
DEVELOPMENTS, MAJOR DEVELOPMENTS business users and other IT areas
hinder the operability of applications.
and PROJECT DEVELOPMENTS. This
This concept should not be confused with
distinction lies in the number of estimated
defects, which are associated with errors or
hours. Minor developments usually take
defects in the product generated by us.
under 50 hours; projects are those
developments which, due to their volume or
impact, need to be managed independently.
14
Subtasks according to the Request type:
➢ All requests and activities will have a bulk upload option.
➢ Within each type of request, a category of activities will be defined; it will indicate the product development stage at any
time.
➢ Activities within requests (subtasks) are created automatically and can be parametrised for each project/service on request
to UMANE. Therefore, the activities that will be automatically loaded for each type of request if nothing is specified are as
follows:
Development Corrective Support
Management
Functional analysis Support
Functional analysis
Construction
Technical design
Construction
Integrated Tests
Deployment
15
Subtasks according to the Evolutive Request :
16
Concept not to be confused from now on :
The notion of petition / OT does not exist :
In FENIX IN JIRA
Petition / OT Parent task
The ACC, in JIRA is mean: Subtask
In FENIX IN JIRA
ACC Subtask
17
Plan:

6. JIRA Workflow
9. DEMO
18
2
Your projet
Evolutive, Corrective, support
Short description of the task

Minor, major, project
Detailed description of the request
19
Fields that identify the technology in which

the request is developed and the% of use.
Phase field, to determine in more detail the moment

in which the request is found ( under study, in analisis
or in construction …)
Task priority: Critical, Hight, Low
The subtask is billable to customer (Yes)

It's not mandatory: Component field, to categorize
the task. Manageable by the project administrator.
(Module or application to which the issue belongs )
It's not mandatory; The grouping field allows the
issues to be grouped according to a series of values
requested from UMANE at the time of creating the
project. This field does not take into account the
type of request (it is a general grouping).
It's not mandatory; Labels field, to add labels to the

task and categorize the requests.
Your Service / Project (It's not mandatory )
Mark this check to choose the person in charge

of manage it
20
Sales Estimate (hs) and Internal

Estimate (hs) fields, which is the
estimate of the real effort that we
believe a request will cost, which may
not coincide with the previous one.
Once the request is In Execution, this
field should only be edited before a
Scope Change.
Version or date in which the request

will be delivered (it's not mandatory )
21
Number of client requests related to this

request.
Request ID in the client tool
Finally : create it
22
There are 10 customizable combo-type

fields (field name and possible
values (V1, V2…).
23
There are 10 customizable text type

fields (field name and free text).
24
There are 10 customizable date type

fields (field name and date).
25
Plan:

6. JIRA Workflow
9. DEMO
26
6. JIRA Workflow
Workflow of NON operational work :
The request flow only supports two states: running and closed.
IN PROGRESS Execution status of all subtasks associated with the request .
The request is fully finalized and cannot be reopened for any reason. If it is
CLOSED
necessary to reopen it, please contact the administrator.
27
6. JIRA Workflow
Workflow of operational work : Workflow - Evolutive
The request flow is open, with no restrictions on passing between statuses, so we can move from any status to any other.
The only status that does not allow this is the final state (Closed), which will not allow further progress in the flow (except
by the administrator user)
Open Request registration
Under study The task to be carried out is reviewed, if we can accept the request, first steps...
In progress Execution status of all subtasks associated with the request.
WORK Pending
The request is stalled for several reasons: lack of information.
FLOW Information
Blocked The request is blocked and the reason for the block must be identified.
Delivered The request has been submitted, pending the revisions needed before it is closed. The request can be reopened if necessary.
The request has been fully closed and cannot be reopened for any reason. If it needs to be reopened, please contact the
Closed
administrator.
This is a transition that we will press every time the scope of the development changes, but it will keep the request in the same status it
Scope Change
was in when the change was generated.
28
6. JIRA Workflow
Workflow - corrective and support
The request flow is open, with no restrictions on passing between statuses, so we can move from any status to any other.
The only status that does not allow this is the final state (Closed), which will not allow further progress in the flow (except
by the administrator user)
Open Request registration.
Under study The task to be carried out is reviewed, if we can accept the request, first steps...
In progress Execution status of all subtasks associated with the request.
WORK Pending
The request is stalled for several reasons: lack of information.
FLOW Information
Blocked The request is blocked and the reason for the block must be identified.
Delivered The request has been submitted, pending the revisions needed before it is closed. The request can be reopened if necessary.
The request has been fully closed and cannot be reopened for any reason. If it needs to be reopened, please contact the
Closed
administrator.
29
6. JIRA Workflow
Workflow of Subtasks :
➢ The Subtasks flows will be open. This means that we can move from one status to any other as we need.
➢ The Subtasks statuses are:
Status Description
Open Activity registration
In progress Status of implementation of specific activities
Pending information The activity is at a standstill for several reasons: blockages, lack of information.
Delivered The activity has been delivered and is awaiting the necessary revisions before its closure. The activity can be
reopened if necessary.
Closed The subtask is fully completed and cannot be reopened for any reason (by an administrator user only).
30
6. JIRA Workflow
31
Plan:

6. JIRA Workflow
9. DEMO
32
How to assign a Task ?
33
34
7. Assign a task & Work log-ETC : Search a task
35
7. Assign a task & Work log-ETC : Search a task
36
7. Assign a task & Work log-ETC: Search a task
37
7. Assign a task & Work log-ETC: Search a task
38
The first way to do the Log Work :
39
The amount of time

1
logged working on the
issue
the date when you 2
started this unit of
work.
3
Adjust automatically the
ETC
3
Adjust manually the ETC
** The work log is done

usually within the
subtask and not within
the parent task
4
40
The second way to do the Log Work :
Go inside the
subtask to do the
log work
41
The amount of time

1
issue
the date when you 2
work.
3
ETC
3
** The work log is done

usually within the
subtask and not within
the parent task
4
42
The third way to do the Log Work : in Jira - Timesheet
Allows you to view the incurred (it only shows the tasks that have been incurred in the configured period) and allows
you to incur from the gadget:
43
The amount of time

1
issue
the date when you 2
work.
3
ETC
3
4
44
Plan:

6. JIRA Workflow
9. DEMO
45
Jira – Teams
It is possible to have Access to JIRA from Teams.
We add the URL of JIRA
We add the URL of the JIRA board(It is

possible to directly access the board)
Example: https://umane.emeal.nttdata.com/jiraproy/secure/RapidBoard.jspa?rapidView=4546
46
Jira – Teams
The integration will provide us with a concrete vision of JIRA in the Microsoft Teams application. This can add value to us to be
able to detect requests created in JIRA and that are automatically notified in different channels.
Displays the information on the issue in information boxes and we have a link to JIRA.
Note: Part of the integration configuration must be done by the UMANE team.
Integración JIRA - Teams

47
Jira - Outlook
Outlook Integration for JIRA is a plugin that we can install in Outlook and that speeds up the transfer of information from Outlook
to JIRA in the form of: Create requests in JIRA from an Outlook email. Incorporate an email as a comment to a JIRA request.
This plugin is available to all users with access to JIRA from UMANE.
Integración JIRA - Outlook

48
Plan:

6. JIRA Workflow
9. DEMO
49
DEMO
50
Plan:

6. JIRA Workflow
9. DEMO
49
✓ All documentation related to JIRA-KOSIN can be found it at:

https://everisgroup.sharepoint.com/sites/DMFTetuan-
Calidad2/Documentos%20compartidos/Forms/AllItems.aspx?id=%2Fsites%2FDMFTetuan%2DCalidad2%2FDocumen
tos%20compartidos%2FGeneral%2F03%2E%20Formaciones%2F01%2DJIRA%2D%20KOSIN&viewid=02c33c22%2
D8cd4%2D4077%2Da645%2Dd63d7f31b33b
✓ The formations about JIRA-KOSIN are available at:

https://ulearndx.everis.com/auth/ldap/ntlmsso_attempt.php
✓ JIRA Pre-Prod link:

https://umane.everis.com/jiraito/projects/SDF/
https://umane.emeal.nttdata.com/jiraito/projects/KST/summary
✓ For any questions or suggestions about JIRA - KOSIN, you can contact the Level 1 Support team: Production Local Team.
26
Thank you

Module 2 KOSIN Advanced 1 English Version

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Module 2 KOSIN Advanced 1 English Version

Uploaded by

Copyright:

Available Formats

KOSIN - 更新

Module 2: KOSIN Advanced 1

1. KOSIN training & implementation Plan

1. KOSIN training & implementation Plan

Module 2: Module 3: Module 4: Module 5:

1. KOSIN training & implementation Plan

Tailor-made searches Agile Dashboards Dashboards for monitoring

KOSINDM KOSINCT CTS OneSight

1. KOSIN training & implementation Plan

Work model 1 Planning Tool 7

NON-operational work 2 Operational work 3 Management items 4

Imputable to the project Development Risks

Dashboards, Filters and Panels 5

1. KOSIN training & implementation Plan

(more information in the following slides)

Some characteristics of these tasks are:

Subtasks not billable to the project

Within each type of task, there

➢ All operational requests of the project/service must be registered.

Development / Evolutive Corrective Support

Adaptation actions needed to keep the

Subtasks according to the Request type:

➢ All requests and activities will have a bulk upload option.

Concept not to be confused from now on :

The notion of petition / OT does not exist :

The ACC, in JIRA is mean: Subtask

1. KOSIN training & implementation Plan

Evolutive, Corrective, support

Short description of the task

Detailed description of the request

Fields that identify the technology in which

Phase field, to determine in more detail the moment

The subtask is billable to customer (Yes)

It's not mandatory; Labels field, to add labels to the

Your Service / Project (It's not mandatory )

Mark this check to choose the person in charge

Sales Estimate (hs) and Internal

Version or date in which the request

Number of client requests related to this

Request ID in the client tool

There are 10 customizable combo-type

There are 10 customizable text type

There are 10 customizable date type

1. KOSIN training & implementation Plan

Workflow of NON operational work :

IN PROGRESS Execution status of all subtasks associated with the request .

Open Request registration

In progress Execution status of all subtasks associated with the request.

Workflow - corrective and support

Open Request registration.

In progress Execution status of all subtasks associated with the request.

Open Activity registration

In progress Status of implementation of specific activities

1. KOSIN training & implementation Plan

The amount of time

** The work log is done

The amount of time

** The work log is done

The amount of time

1. KOSIN training & implementation Plan

We add the URL of JIRA

We add the URL of the JIRA board(It is

Integración JIRA - Teams