When was the last time you were able to learn a complex concept, or complete a non-trivial task without understanding the context that surrounds the thing you were working on? For example: understanding requirements (or user stories) is difficult without understanding the business initiative (or epic) that gave rise to it, understanding a defect is difficult without understanding the conditions that uncovered it, creating test cases is difficult without understanding how the application is supposed to work.

1. © Tasktop 2016© Tasktop 2016
Strong ARM Your Tools
January 28, 2016

2. © 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?

3. © Tasktop 2016
of the
Fortune
10033
of the top
25 world
banks7
of the top
10 US
insurers5
of the top
6 health
plans3
Tools
Supported40
Tool versions
tested200
API tests
run per day500K
Software
Lifecycle
Integration#1
Over
200,000
Sync Seats
Over
2,000,000
Mylyn/Dev Users
Vancouver HQ
Offices in Austin,
Boston, UK.
Founded 2007
Strategic
Partners24

4. © 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

5. © 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

6. © Tasktop 2016
What is Tasktop Sync?
Uni-directional or
bi-directional
updates
Tool 1 Tool 2
Artifact
Summary
Status
Assignee
Due Date
Iteration
Attachments
Comments
Etc.
Artifact
Summary
Status
Assignee
Due Date
Iteration
Attachments
Comments
Etc.
Artifacts =
Stories
Defects
Requirements
Etc.

7. © Tasktop 2016
Artifacts are more than the
“stuff inside them”

8. © Tasktop 2016
Story A
Epic
Story B
Defect
Test Case
Story A
Epic
Story B
Defect
Test Case
Epic
Defect
Story A
Defect
Story A
Epic
Story B
Defect
Test Case
Story A
Epic
Story B
Defect
Test Case
Story A
Relationships are Vital

9. © Tasktop 2016
Artifact Relationship Management
Tasktop Sync understands and helps manage the relationships between
artifacts…across your tools
What is ARM?

10. © Tasktop 2016
Traceability
Organization
Release Readiness/Quality
Why do I need ARM?

11. © 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

12. © Tasktop 2016
Traceability
Functional
Requirement
Use Case
Non-
functional
Requirement
Use Case 2
Non-
functional
Requirement
Blueprint
HP 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

13. © Tasktop 2016
It is imperative to maintain the hierarchical
organization of your work items across your
systems
Organization

14. © 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

15. © Tasktop 2016
Aligning container organization of two
systemsDOORS 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

16. © 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

17. © 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

18. © 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

19. © Tasktop 2016
PMO to Development
CA PPM RTC
Feature Brazil
Project 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

20. © 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

21. © Tasktop 2016
Demo

22. © Tasktop 2016
Your Other ARM

23. © 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?

24. © Tasktop 2016
Other ARM
Requirement
Test 1
Requirement
Test 2
Weblink 1
Weblink 2
DOORS NG HP ALM

25. © Tasktop 2016
Demo

26. © Tasktop 2016
Tasktop
We relieve your integration pain
ARM
How you solve your Organizational, Traceability & Quality
needs between various tools
Two Key Takeaways

27. © Tasktop 2016
Questions?

28. © 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 info@tasktop.com

29. © Tasktop 2016
Thank You