Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
Agile Data Warehousing
Transcript of Agile Data Warehousing
Agile Data Warehousing
Where we’re at now
What the journey to Agile looked like
What was required
Results, good and not so good
Roles, Process and Infrastructure
Agile at Cobalt
An Agile Success Story
Let's Migrate the
Benefits, Challenges, Next Steps
Now: 70+ releases / year
Before: 6 – 8 releases / year
Now: 1 “must fix” issue / quarter
Before: 1 “must fix” issue / month, at least :)
No longer need headcount dedicated to testing
Growth in technical skill set on team
Able to adjust as business demands
Phase 3: Automate Everything!
What Does the Team Look Like?
Improve the break / fix cycle
Move along the Continuous Integration path
Continue to build “generalized specialists”
Make testing cycles more efficient
Rolling out Agile to all of ADP development
Rolling out to EMC development
Where Do We Go From Here?
Finding qualified Product Owners
Teams bog down without good inputs
Growing the Dev team’s skill set
Must focus on tests first. Not their preferred tasks.
Traditional ETL work turned into SW Engineering.
Need to invest in learning curves
Coordination across multiple fast moving teams
Coding and testing standards
Feature incompatibility or collision
Agile with 5 teams and 3 time zones is tough
Lots of early morning or late night meetings
Key stakeholder, has vision of what is to be built
Process owner, coach, removes obstacles, protector
5-9 people, cross-functional, self-organizing
Phase 2: Starting the Move to Agile
2009: The Manual Days
Waterfall process, one small team
2010: Move to Agile
Team gets introduced to Agile
BI culture starts to evolve
2011: Automate, automate, automate
Team growing rapidly
2012: Complete migration
Marketing Services for the Automotive Industry
Platform: Websites, Inventory, Search, Display, Email, Social
Covering ~50% of US market, and 4 countries
Our BI focus is to measure:
Vehicle supply / demand
Automobile manufacturers and dealers
Bid Engine, Ad Optimization Specialists
What Does Our Team Do?
Chris Mills – firstname.lastname@example.org
Bruce Szalwinski – email@example.com
Getting to Agile
Phase 1: Everything is Manual
Three easy phases :)
(c) ADP Dealer Services, Inc. All Rights Reserved. Confidential and Proprietary.
Doing an Agile Migration
100's of Reports
5,000 Unit Tests
2,000 more tests
Where we have been since Feb 2013
Build a build light, emphasis on being responsible for checkins
Looking for ways to test dynamic data sources
Rotating scrum master role
Agile continuing to rollout across ADP