Transcript
Page 1: Strong Arm Your Tools

© Tasktop 2016© Tasktop 2016

Strong ARM Your ToolsJanuary 28, 2016

Page 2: Strong Arm Your Tools

© Tasktop 2016

Tasktop Sync is an integration server that provides fully automated, enterprise-grade synchronization among the artifacts created and managed

within the disparate tools used in software development and delivery organizations.

What is Tasktop Sync?

Page 3: Strong Arm Your Tools

© Tasktop 2016

of the

Fortune

10033of the top 25 world banks7of the top 10 US insurers5of the top 6 health plans3

Tools Supported40

Tool versionstested200API tests run per day500K

Software

Lifecycle

Integration#1

Over

200,000 Sync Seats

Over

2,000,000Mylyn/Dev Users

Vancouver HQ

Offices in Austin,

Boston, UK.

Founded 2007

StrategicPartners24

Page 4: Strong Arm Your Tools

© Tasktop 2016

– Brittle point-to-point

– Requires developers

– Upgrade issues

A new kind of infrastructure

– Real-time lifecycle bus

– Configurable, extensible

– Connects people

– Manual, error prone

– Email & spreadsheets

– Does not scale

Page 5: Strong Arm Your Tools

© Tasktop 2016

Agile Project Mgmt

JIRA

Rally (CA Agile Central)

VersionOne

Mingle

IBM Bluemix

CA Agile Planning

ServiceNow SDLC

ALM

Microsoft TFS

MS VS Team Services (VSO)

IBM RTC

Polarion

Test Management

HPE QC/ALM

IBM RQM

Tricentis Tosca

Microsoft Test Manager

ITSM

ServiceNow

BMC Remedy

Zendesk

JIRA ServiceDesk

Issue Tracker

Bugzilla

GitHub Issues

Requirements Mgmt

Jama

IBM Rational DOORS NG

IBM Rational DOORS

IBM Requisite Pro

Serena Dimensions RM

iRise

Blueprint

Change/Workflow Mgmt

Serena Business Manager

Borland StarTeam

IBM Rational ClearQuest

CA Harvest

Project & Portfolio Mgmt

CA Clarity

ServiceNow PPM

Planview Enterprise

HPE PPM

Microsoft Project Server

Page 6: Strong Arm Your Tools

© Tasktop 2016

What is Tasktop Sync?

Uni-directional or bi-directional

updates

Tool 1 Tool 2

Artifact

SummaryStatusAssigneeDue DateIterationAttachmentsCommentsEtc.

Artifact

SummaryStatusAssigneeDue DateIterationAttachmentsCommentsEtc.

Artifacts =

StoriesDefectsRequirementsEtc.

Page 7: Strong Arm Your Tools

© Tasktop 2016

Artifacts are more than the “stuff inside them”

Page 8: Strong Arm Your Tools

© Tasktop 2016

Story A

Epic

Story B

Defect

Test Case

Story A

Epic

Story BDefect

Test Case

Epic

Defect

Story A

Defect

Story A

Epic

Story BDefect

Test Case

Story A

Epic

Story BDefect

Test Case

Story A

Relationships are Vital

Page 9: Strong Arm Your Tools

© Tasktop 2016

Artifact Relationship Management

Tasktop Sync understands and helps manage the relationships between artifacts…across your tools

What is ARM?

Page 10: Strong Arm Your Tools

© Tasktop 2016

Traceability

Organization

Release Readiness/Quality

Why do I need ARM?

Page 11: Strong Arm Your Tools

© Tasktop 2016

Different ways to look at traceability… We could talk about traceability matrixes, requirement test coverage, dependencies, traces, etc.

One piece of the puzzle:

Lifecycle of a requirement, where it originates, what it is derived from

Bi-directional traceability to predecessors and successors

Reuse of requirements

Example:

Visual use cases enabled by functional requirements

Functional Requirements constrained by non-functional requirements

Traceability

Page 12: Strong Arm Your Tools

© Tasktop 2016

Traceability

Functional Requirement

Use Case

Non-functional

Requirement

Use Case 2

Non-functional

Requirement

BlueprintHP ALM

Related to

Enabled by

constrained

constrained Functional Requirement

Use Case

Non-functional

Requirement

Use Case 2

Non-functional

Requirement

Related to

Enabled by

refined

refined

Use Case

Use Case 2

Non-functional

Requirement

Page 13: Strong Arm Your Tools

© Tasktop 2016

It is imperative to maintain the hierarchical organization of your work items across your

systems

Organization

Page 14: Strong Arm Your Tools

© Tasktop 2016

Keeping requirements management artifacts within their folders (in the correct hierarchical order) across tools

Folders (packages, containers, etc.) can represent:

Organizational units

Projects

Cycles, releases

Teams

Either way – maintaining the folder – requirement (and other artifact) hierarchy is critical to efficiently manage your work across the tools.

Not only to mirror, but to also *map* the differences and structural mismatches between tools

Container organization

Page 15: Strong Arm Your Tools

© Tasktop 2016

Aligning container organization of two systems

DOORS NG HP ALM

USA

Europe

Asia

Textual Requirements

Use Cases

Req 1

Req 2

Textual Requirements

Req 1

Req 2

Project USA

Project Europe

Project Asia

Textual Requirements

Use Cases

Req 1

Req 2

Textual Requirements

Req 1

Req 2

Tasktop Sync

Page 16: Strong Arm Your Tools

© Tasktop 2016

Multiple teams in the supply chain, each using different process and different tools

Goal – thorough visibility for the product managers, BAs, release managers, etc.

Leverage ARM capabilities to allow the teams:

Decide who does the work and where the work breakdown happens (Epics refined into stories)

Provides each team with their preferred level of detail

Bi-directional detailed, as well as high level status updates

Development work organization

Page 17: Strong Arm Your Tools

© Tasktop 2016

Supply chain

RTC JIRA

Epic 1

Epic 2

Story 1

Story 2

Story 3

Epic 1

Epic 2

Story 1

Story 2

Story 3

RTC

Team 1:- BAs- PMs- Etc..

Team 1:- Dev

Team 2:- Dev

Sub-task

Sub-task

Page 18: Strong Arm Your Tools

© Tasktop 2016

Aligning work between PMs and Development

Leverage ARM and fix discrepancies between PPM and dev tools. For example:

Your organization constantly launches new projects

Each project has a dev team assigned to it

For the Dev team, a project is viewed as a high level work item (not a whole project)

With ARM, allow projects to dictate high level artifact creation for dev teams:

Features

Initiatives

Epics

Also, maintain the hierarchy below the top level, therefore, allowing for consistent status and progress updates

PMO to Development organization

Page 19: Strong Arm Your Tools

© Tasktop 2016

PMO to Development

CA PPM RTC

Feature BrazilProject Brazil

Summary Task

Sub-Task

Sub-Task

Story

Sub-Task

Sub-Task

Project Latvia

Summary Task

Feature Latvia

Summary Task

Summary Task

Summary Task

Summary Task

Summary Task

Page 20: Strong Arm Your Tools

© Tasktop 2016

Demo Scenario

Epic Epic

Parent/Child

Derived From

Jama JIRA

Parent/Child

Blocks/Blocked By

User Story User Story

User Story User Story

Defect Defect

Page 21: Strong Arm Your Tools

© Tasktop 2016

Demo

Page 22: Strong Arm Your Tools

© Tasktop 2016

Your Other ARM

Page 23: Strong Arm Your Tools

© Tasktop 2016

What happens when an artifact cannot live on both sides?

You can link to the artifact from the other tool

What ‘other’ ARM?

Page 24: Strong Arm Your Tools

© Tasktop 2016

Other ARM

Requirement

Test 1

Requirement

Test 2

Weblink 1

Weblink 2

DOORS NG HP ALM

Page 25: Strong Arm Your Tools

© Tasktop 2016

Demo

Page 26: Strong Arm Your Tools

© Tasktop 2016

TasktopWe relieve your integration pain

ARMHow you solve your Organizational, Traceability & Quality

needs between various tools

Two Key Takeaways

Page 27: Strong Arm Your Tools

© Tasktop 2016

Questions?

Page 28: Strong Arm Your Tools

© Tasktop 2016

To learn how you can benefit from integrating your development environment with Tasktop:

Please contact us at www.tasktop.com/contact-us

Or email us at [email protected]

Page 29: Strong Arm Your Tools

© Tasktop 2016

Thank You


Top Related