Syensqo IS - Customer Support

Page tree

Versions Compared

Old Version 2

changes.mady.by.user TAN, Li-Lian

Saved on

compared with

New Version Current

changes.mady.by.user TAN, Li-Lian

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
borderColor#DBDBDB
bgColor#F2f2f2
borderWidth1
Panel
borderColor#DBDBDB
bgColor#ffffff
borderWidth1
Column
width10

Column
width90

Why Jira?

Change is always difficult at the beginning. Time permits us to better accept changes. Migrating to JIRA is our first chance to be opened to the world of agility.

Shorter release cycle. Simplication on ticketing tools. Reknown and standards of the market. Standardisation of major platforms like Core CRM and iCARe. Continuous integration tools among developers. Structured way of doing tests. Better visibility of tests performed and the results.

This move is one step ahead for transformation. To better prepare us to take new challenges!

YES WE CAN! (smile)

How to adopt JIRA in 5-minutes!

Create an issue in jira:

Panel
borderColor#DBDBDB
bgColor#F2f2f2
borderWidth1
Panel
borderColor#DBDBDB
bgColor#ffffff
borderWidth1
Table of contents

Table of Contents

Panel
borderColor#DBDBDB
bgColor#ffffff
borderWidth1

Useful links:

1.Lost in JIRA as I used to work thay way...tell me more!

.Terms in JIRA

Expand
titlesee definitionsthe changes
Used to be in PMO......Going to be in Jira
RequirementsStory (issue type)
DefectsBug (issue type)
Test scriptsTest (issue type)
SFDC processEpic (issue type). Remember to assign issue
with
to an Epic!
ReleaseFix version (field). In order to assign issue to a release, first needs to create a release record by Change Manager
Urgent change - quick and small hot fixes that are pushed to production quicklyCreate as either Story or Bug. Each move-to-production has to be a release. Urgent change is tied to a minor release
  
  
  

 

Expand
titlejira for dummies
Expand
titleBacklog

A Backlog is a list of issues in the pipeline, waiting to be qualified and assigned to a sprint.

Image Added

Expand
titleSprint

A Sprint can be planned ahead and issues can be assigned to planned sprints.

At any time, you cannot have 2 sprints running at the same time.

You need to complete a sprint before to start another one.

 Image Added 

Expand
titleActive sprint

 An active sprint is the current running sprint.

Image Added 

Expand
titleWorkload estimation and time logged

Image Added 

Expand
titleTest (issue type)

A Test is an issue type. When you create a Test, it has other properties of a Test Case.

It lists down the Test Step, Test Data required to execute that Test Step, Expected result of the Test Step.

You can only include an attachment to a step should it require graphical verification.

Image Added 

 

Expand
titleTest cycle view

Test cycle contains a list of all the Test issues that need to be executed.

Test cycle can be easily created and then clone, for example, the same test cycle cloned for Devpro and UAT.

For a given Test cycle, we have a good visibility of all tests executed and it's percentage of passes/fails.

Image Added 

 

Expand
titleTest execution

Image Added 

 

Expand
titleTransition vs Status

 

Image Added 

 


2.0 Workflow

2.1 Requirements/Story workflow

Expand
titlesee definitions

 

2.2 Defects/Bug workflow

Expand
titlesee definitions


2.3 Detailed activites in the issue lifecycle

Expand
titlesee explanations

Image Added

3.0 Step-by-step guidelines

 

 

Expand
title3.1 As a Functional Lead...

Image Added

Expand
title3.2 As a Developer...

Image Added

Expand
title3.3 As a Security team...

Image Added

Expand
title3.4 As a Tech Lead...

Image Added

Expand
title3.5 As a Deployment Lead...

Image Added

Expand
title3.6 As a Change Manager...

Image Added

Expand
title3.7 As a Tester in Adoption team...

Image Added

Expand
title3.8 As a Key User from GBU...

Image Added