1. Agile Process & the Role of CA PPM in the IT Ecosystem of Tools
Patrick Finkler & Eric Van Blarcum | May 4-6, 2015

2. Agenda To Integrate or Not to Integrate What Data Should be in CA PPM?
Source of Truth
Governance Tool Ecosystem
Common Integrations
Open Mic
Best Practices for Building Integrations
Agile and CA PPM

3. To Integrate or Not to Integrate
Is it Expensive?
10 years ago, integrations where very expensive, but now with improved integration technology and frequency, integrations are much more cost effective
10-15K is the cost of a typical Rego integration
Who Should be the Source?
CA PPM should NOT be the source of all truth
CA PPM is a decision making tool
It needs the information to make decisions, but not necessarily the source
Is the Process Mature?
Integrations are built to match process
You must detail the process and the flow of information
You must have a solid repeatable process and be able to identify programmatically the exceptions

4. What Data Should be in CA PPM?
Demand Management
Project Management
Time Management
Financial Management
Resource Management

5. When CA PPM is not the Source
Demand Management
Demand fed from SharePoint or SalesForce
Project Management
Tasks fed from Agile Tool
Issues, risks fed from SharePoint site
Time Management
Time fed from corporate system
Financial Management
Non-labor actuals fed from financial system
Contractor actuals fed from vendor management system
Resource Management
Resources fed from HR System

6. When CA PPM is the Source of Truth
Demand Management
Resource and financial forecast for demand
Project Management
Project information
Tasks and/or milestones (except agile and ITSM)
Resource and Financial Forecast
IRC + Status
Time Management
Actual time
Financial Management
Average rates for forecasting
Financial forecast
Resource Management
Idea and project demand
Resource information

7. Governance Sub-Process Ecosystem

8. Governance Tool Ecosystem

9. Common Integrations

10. Open Mic Who thinks they have “Over-integrated”? Why?
Who thinks they have “Under-integrated”? Why?
Common Interfaces – List interfaces you have

11. Agile & PPM

12. We are responsible for delivering high quality working software.
What’s More Important?
We are responsible for selecting, managing, and optimizing projects, programs, portfolios, resources & investments.
We are responsible for delivering high quality working software.
PMO
AGILE TEAMS

13. What’s More Important?
What can we deliver in the next few product releases?
I need to deliver this release, so please stop bothering me.
PMO
AGILE TEAMS

14. What’s More Important? – Decisions
I need a team of skilled people to stay together to focus on constant delivery.
Will you have the skilled resources available to deliver the product?
PMO
AGILE TEAMS

15. What’s More Important? Where are we spending our time?
Tracking time slows me down and is annoying.
PMO
AGILE TEAMS

16. We MUST Work Together
Agile
Portfolio
Governance

17. Agile and CA PPM Project and Portfolio Management
Business Strategy
Application Portfolio Management
Demand Management
Resource Management
Financial Management
Portfolio Reporting & Analytics
Traditional Waterfall Programs & Projects
Agile Program & Projects
Customer Delivery

18. Using CA PPM and an Agile Tool
With Agile, tool not as important as process
Key decisions
How to maintain governance
Integration points
Governance vs. Agile
Visibility for PMO & senior leadership needs to be maintained
Only a portion of your project or team may be agile
Water-Scrum-Fall
Ex: general Project Charter with a fixed time frame & budget

19. Integration Points Agile CA PPM Product or Release Sprint/Kanban Board
User Story/Issue
Task
Impediment
Team Member
Hours Logged
Remaining Hours
Project
Phase
Activity
Task
Issue
Team Member/Assignee
Timesheet/Trans. Hours
ETC

20. Vendor Overview N/A Vendor and Tool CA PPM Integration Methods
SaaS Solution Available
Key Features
On Premise Cost for 100 Users (annually)
SaaS Cost for 100 Users (annually)
CA CA PPM Agile
Yes
Scrum, Kanban
Out of the box CA PPM integration
N/A
$54,000
IBM Rational
Yes, 3rd party (Tasktop, Pervasive, or custom)
Scrum, IBM Agile Scaling Model
 Yes
largest vender in ALM market, large range of products
$100K - $150K plus CA PPM integration
IBM Rational Jazz
Atlassian JIRA + Agile
price, large user base, lots of add-ons and plugins
$6,000 ONE TIME FEE (plus CA PPM integration)
$5,400 (plus CA PPM integration)
TFS
$50K - $75K plus CA PPM integration
Web Service APIs and SDK
Rally Software
large feature-set, large agile-specific user base
$42,000 - $58,800 (plus CA PPM integration)
VersionOne
Scrum, Kanban, Lean, XP, Hybrid
large feature-set, supports many methodologies, large agile-specific user base
$34,800 - $46,800 (plus CA PPM integration)

21. Best Practice Building Integrations

22. Integration Basics – Triggers
Event Based
This type of Interface is triggered by event in the system (something got created or updated or deleted)
Batch
This type of interface is scheduled and triggered at a set time (nightly or at certain interval, etc.)
Since, batch interfaces will handle multiple instances, you want to address transaction managements (what happens when a record fails – one fail, all fail?)
Manual
This type of Interface is manually started by the user when they are ready for data transmittal
Clients

23. Integration Basics – Methods
Flat File
A .CSV file ftp’d onto a server can be pulled into CA PPM
The file can be read by custom GEL scripts within a process that can be scheduled or started manually.
This is CA’s preferred method of integration for the On-Demand
Web Services
XML based messaging making calls via URLs, or over HTTP to request data from or push data into CA PPM
This method could leverage GEL scripts, Java classes, or Stored Procedures in the DB
This is the most common approach used by any industry for Integrating different systems – Most of the big software vendors like SAP, Oracle, HP, CA have web service API’s developed for bi-directional data exchange with their systems
Database Links
Establish a link from the CA PPM DB to another system database and just pull data from one system to another using a stored procedure or SQL statement
Best practice in this form is to create a “view” in the source system vs. the core tables (not an option for On Demand Clients)
Third Party Tools
Leverage a third party integration tool like ITROI to build integrations
Leverage an integration service – Pervasive or Task Top

24. Comparing Methods Flat File Web Services DB Link Available in SaaS YesNo
Rough Effort*
40-60 Hours
Hours
Examples
Send journal entry for capital entry
Read data from any legacy system
Create SAP project from new CA PPM project
Auto create support tickets in CA PPM by reading data from ticketing system
Pull non-labor financials to CA PPM
Pull resources into CA PPM
Push assignment data from CA PPM
Components
Process to read
Error object
Process for outbound
Java for inbound
Error Object
View to read
Process to move from view to object
*With an integration, effort is needed on both the sending and receiving application. This means that any CA PPM integration will require some effort form the support team of the system you are integrating to. The level of effort depends on the type of interface.

25. Keys to Success Simpler is Better Get it Right the First Time
With integrations, the more complex the interface is the more difficult it will be to build and maintain
One Direction vs. Bi-Direction is simpler
Get it Right the First Time
We love agile and iterative development, but not when building an interface
Interfaces are best done with solid waterfall requirements and signoffs
Integrations are recurring jobs
Integrations are not for performing one time data loads
Integrations are for exchanging data between two systems on a regular basis
Data Ownership is Key
You must determine which system is the “source” vs. the “non-source” of the data
One source must be the owner of the data in case of conflict
Do not make the mistake to think CA PPM will be the “source” of everything
Leverage other systems to pull summarized data vs. all detail

26. Keys to Success, cont. Error Handling / Transaction Management
Errors are inevitable when two different systems are being integrated
Plan to develop an error handing mechanism to handle data errors, connectivity errors, and system outages
Equally important is transaction management and performance considerations
Trial First to Avoid Errors
Before you build the complete interface, try a semi-automated load to ensure the “process” you have defined is correct
Have a Testing Environment.
It is really important to have test environments that mirror the productions as much as possible and that the data is representative of actual production data

27. Questions Phone Email Website
We hope that you found this session informative and worthwhile. Our primary goal was to increase your understanding of the topic and CA PPM in general.
There were many concepts covered during the session, if you would like to contact any presenter with questions, please reach out to us.
Thank you for attending regoUniversity 2015!
Phone
Website