1. WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester

2. why agile? 40% Clarity customers use Agile 2x Agile growth in last 3 years Customers use both Waterfall and Agile

3. agile management + executive visibility Agile Community to Gather Ideas Team Edition with Agile Functionality Enterprise Edition with Clarity Integration Dreamforce Nov ‘09 March 2010June 2010 CA Agile Vision Create and manage requirements for Agile projects Manage sprints and backlogs for distributed teams Get visibility into all types of projects through CA Clarity PPM integration

4. support for agile teams Inline create, edit, decompose, prioritize, rank, and estimate project, release and sprint backlog Assign resources, and update progress for user stories and tasks. Create and manage requirements for Agile projects Intuitive UI to create multiple time-based sprints, assign backlog, and monitor sprint progress. Virtual wall of requirements Facilitate sprint planning in an Agile planning process Burn-down chart with velocity, velocity-based forecasting Personalized views and dashboards Collaborative workspace for daily stand-up meetings

5. building CA Agile Vision the agile way — The team − QA : 10 − Dev: 12 − Product Owner: 1 − Scrummaster: 1 − Tech Pubs: 2 — 16 2-week sprints − Last two sprints were Stabilization and RTM − Beta overlapped sprints 12-14 — Interesting details: − 3 different companies involved − 6 sites over 4 time zones and on 3 continents

6. agile project performance points delivered vs. planned by performance — QA is part of the sprint — Points do not count at all if a PBI is not completely done (including development, testing, fixing bugs, and validating fixes)

7. working within our governance process — Scheduled gates to match up with sprint completion — Corporate beta overlapped sprints 12 and 14 using Sprint 11 product — RTM Process after completing stabilization sprint # — During RTM period the team completed documentation of their code — Differences for agile projects − Could show incremental product every two weeks to customers − Had to explain why defect curve didn’t look like a traditional project

8. lessons learned — Don’t forget sprint zero — Be flexible – Chicago worked late and Beijing worked early to connect every day — Let the team self-govern and learn how to work together — Break backlog items down as much as possible to get complete closure during a sprint — Important to understand how the backlog is being built and prioritized — Tools used to build CA Agile Vision − ExtJS, FusionCharts (flash-based charting), JQuery, Ant, Java, Watij 8May 16-20, 2010 Copyright © 2010 CA. All rights reserved.

9. driven by the agile community Share, vote and discuss ideas Get updates on idea inclusion in products Provide feedback on current product ca.com/agile

11. thank you

12. CA Agile Vision – Clarity Integration CA Clarity PPM Project and Portfolio Governance Scrum Team CA Agile Vision Scrum Team Project Info and Resources Release, Sprint, User Stories, Tasks and Assignments

13. Agile Vision Enterprise – Clarity Integration CA Clarity CA Agile Vision Project Information maps to Agile Vision Releases Project Dates Project Name Project Desc Time captured on Agile tasks will populate Clarity timesheets Agile Vision passes Release, Sprint, User Story, Task and Assignment Info to CA Clarity Resources allocated in Clarity to an Agile project will be created in Agile Vision Agile Tasks are assigned Charge Codes in Clarity by mapping task types in Agile Vision

14. Accurately track all costs of delivering on customer commitments with your Agile and non-Agile projects. control your costs Predict how much Agile deliverables are going to cost by using team velocity to create accurate forecasts Report actuals to plan with Agile projects including labor and non-labor costs around the world Accurately capitalize costs for Agile projects and get the tax credits you deserve

15. Forecast when customer commitments will be delivered with your Agile and non-Agile projects. deliver with confidence Easily see the status for both Agile and non-Agile deliverables by having a complete portfolio view of all deliverables, projects, status, issues and risks Predict when Agile deliverables will be done by translating Agile work into common business language

16. Balance demand across all Agile and non-Agile projects. get insight into your people See what people are working on by having an integrated view of development resources across all projects Simplify time reporting by having one place for developers to enter time for Agile and non-Agile work Intelligently trade off resources amongst projects by having an integrated view of demand across all current & future projects