Как козаки для больших agile организации инструменты...

CIKLUM

CONSULTING

1

How Cossacks have

chosen tools

Ciklum Consulting,

March 26, 2014

2

Purpose of the speech

AGENDA

3

• Why listen to me?

• Initial request

• Our approach

• Solution

• Challenges

• Alternative tools

4

Why Listen To Me?

Yuri Kudin

• More than 8 years in IT

• Technical background

• Last few years working with

Distributed Agile teams

• Consulting experience

• Practical experience with Atlassian

products during the last 6 years

5

Client

Automotive parts web shop

• US based

• 400+ people in UA entity

• 30+ people in development unit

6

Initial Request

7

Approach

TOOLS

TRAININGAUDIT WORKSHOP TOOLS CONFIGURATION

WORKSHOP WITH

THE TEAM

8

Audit & Solution

9

Org and Product Structure

CAT

Catalogues teams Order team

3rd partyProviders

ORDER

IMPORT-EXPORT

3rd partyProviders

INTERNAL

Internal team

10

Project Workflow

Formalization Preparation Development Publishing

11

Backlog Items

Project

Epic

• Story

• Bug

• Technical Debt

• Investigation

• Task

• Technical Task

Product

Project

Task

12

Theory VS Practice

Portfolio

Program

Team

Business

epics

Arch

Epics

Features

Arch

Features

Theory Our Case

High level

epics

Technical

Epics

Stories,

Sub-tasks

Spikes,

Refact. etc

Epics

Stories,

Sub-tasks

Tech Debt,

Tasks

13

Requirements Structure

Confluence

Jira

High level

requirements

Epic

Story

Tech. Task

14

Boards Structure

Epics

Portfolio

Management

Confluence

Team

TeamTeam

Link

Team

Parallel Sprints

CAT board ORDERD & INTERNAL board

15

Implementation

16

Confluence

17

Epic workflow

18

Epic workflow

19

Epics Board Status Mapping

20

Epics Board Status Mapping

21

Epics Board

22

Reporting

23

Story workflow

24

Technical task workflow

25

Task Board

26

Task board: Priority issue

27

Sprint Reporting

28

JIRA restrictions in scaled agile

• Challenges with multi-level hierarchy

visualization

• No automated update of linked items

• Limited amount of columns

• Lack out of box reporting for scaled agile

29

Alternative tools

30

JIRA vs V1

JIRA VS V1

31

JIRA vs V1

Advantages• Suitable for scaled Agile (SAFe

support)• Out of the box supports all aspects of

Agile Software development• Great relation visualization

Disadvantages • Less flexible • Restriction with reporting (incl. V1

Analytics)

Advantages• Powerful workflow engine • Great user experience • Flexible reporting • Huge amount of plugins

Disadvantages • Lack of flexibility in extending items

hierarchy • Lack of out of box preconfigured

templates

32

Official comparison

• https://www.atlassian.com/software/

jira/agile/agile-comparison#!greenhopper-versionone

• http://www.versionone.com/vs/versionone-vs-altassian-jira-agile/

33

Summary

• Often, a wish to change a tool is a wish

to change a process

• Match tools to the process

• Choose the tool according to needs

www.ciklum.com/consulting34

Yuri KudinTechnical ConsultantConsulting Office (CSC)

P +38 044 545 77 45 (ext. 2348)M +38 097 922 76 79E yuk@ciklum.comW www.ciklum.com/consultingS ykudin

We would be glad to answer your questions!

Contacts