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 the manual
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.
Living Simultaneously With and Without Agile
Simon Stormon 31 March 2014
Transcript of Living Simultaneously With and Without Agile
Financial Services Technology Company
Excess FDIC Insurance through CDARS & ICS
Online Asset Marketplace with BankAssetpoint.com
Audited, Examined, Poked and Probed
With and Without Agile
Common Agile Pitfalls
Why were we successful?
Support from our business
Cross department support
Strong technical talent
Additional positions available
Small, co-located team
Insurmountable Technical Debt
Afraid to make changes
Long release cycles
Every enhancement is hard
Long regression testing cycles
Regularly introduce new bugs with fixes
Huge learning curve
Compounding Productivity Gains
Over a year of two week sprints ending with a deployment
Meetings are more effective
Deployments require only one team instead of six
Business understands and appreciates methodology
The Last Bullet.....
Continuous huh? Test driven what?
Promontory's Agile Transformation
Culture of Continuous Improvement
CDARS / ICS
The unexpected cost.....
New deployment strategies needed like feature toggles
Needed a more robust version control system
Upgraded build tools to meet new requirements
Developers must be able to develop across all the tiers
Developers spend a large amount of time writing test cases
Quality Assurance Engineers learning to write Java
Business Analysts writing test cases in Gherkin
System, Application and Network Engineers writing Puppet manifests and learning Ruby
Oh.....and one more thing.....
The Application Needed to Be Rebuilt
Fundamental shift from developing a complex, highly configurable application to simple, easy to code application
Removed brand new web services tier
Chose to evolve application versus rebuild
- jury is still out
Automated tests required significant refactoring
How to get it done
Dedicated Feature Team
20% of capacity is dedicated to technical debt
One sprint every quarter is dedicated to technical debt
Representation from Application Engineering, System Engineering, Network Engineering, Database Administrators, Development and Quality Assurance
Focused on implementing and evolving the deployment pipeline
Dedicated Automated Testing Team
Hired consulting firm including 3 senior java developers and 3 college students
Realizing the Agile Dream
How do we cure Dr. Jekyll?
Highlight Assetpoint successes
Continuous Delivery - Humble & Farley
The Phoenix Project - Gene Kim
Local Area Meetups
Work starts to get easier
Things don't go wrong as often
Success begins to appear in the strangest places
People want to be a part of it
The impossible becomes attainable
Don't get discouraged
Without automation Agile is still beneficial
Easier to adapt to change
Less time wasted looking too far in the future
Make sure you weigh the benefits versus the costs
Needlessly breaking down tasks into small chunks
Too many long meetings
Consider a hybrid model
Introduce monthly retrospectives to a long waterfall project
Add daily stand-ups to improve communication
Consider alternative Agile implementations like Kanban
Understanding the importance of automation
What is Continuous Delivery
8 Principles of Continuous Delivery
The process for releasing/deploying software MUST be repeatable and reliable
If something is difficult or painful, do it more often
Keep everything in source control
Done means “released”
Build quality in!
Everybody has responsibility for the release process
Promontory CD Pipeline
September 26th, 2013
Promontory CD Pipeline
Promontory CD Pipeline
Static Code Analysis
The New World.....
Pure Agile Implementation
Push Button Deployments
Infrastructure as Code
Lack of Executive Commitment
Weak Strategy (insufficient coaching, etc.)
Underestimating the Importance of Culture
Silo’d Agile Adoption
Practices Without Principles
Neglecting the Need for Technical Excellence
"Although Agile will improve most processes immediately, sustained improvement when building high quality software and systems in short cycles requires disciplined and rigorous technical practices like continuous integration and deployment, refactoring, test automation and test-driven development. This requires a culture of technical craftsmanship."