Hurdles, the sprint with impediments on the way to automation.
The presentation talks about the common problems with automation and how to deal with it. Also the content covers a case study and how the author succeeded in implementing automation.
10. No body was ready for the extra mile
images@google
11. We were dealing with the hardest
thing in this Universe
images@google
12. “ continue to persist in its
state until it is compelled to change
its state by force impressed.”
EverybodyEvery body
What Newton said is right…
source@google
19. > Go slow and steady
Start with simple steps and keep on building
one by oneimages@google
20. #2 The Pace > to succeed you should
sustain
images@google
21. > Define the vision as a team
Past
Retrospective
Notes
Automation Backlog
Automate as many manual, boring jobs
images@google
22. > Showcase during Retrospective
Automation Backlog
Members started picking up line items voluntarily
and worked during the Sprint.
Retrospective
images@google
28. > Campaign “Go home early on release day…”
images@google
29. > Cast right tools for right problem
Again focus on “what works" not “what's best”images@google
30. > Set clear direction to the team.
Check-in Guidelines
Conduct Group Discussion
Training Sessions
State Do’s & Don'ts
images@google
31.
32. > Reach your destiny
Branching Strategy
Build
Automation
Build
Package
Compile
Configuration
Changes
Auto Release Emails
Deployment
Automation
Db Deploy
Automation
Test
Automation
33. Technical Details #1
Challenges we faced! What we did? What we gained
No proper source control
branching strategy, leading
to poor build/release
management.
Introduced new branching
strategy. Kept it simple .
More control over changes,
more control over build/ release
management.
34. Technical Details #2
Challenges we faced! What we did? What we gained
Database deployment was
painful as we were using
Redgate SQL as compared to
generate delta script for the
release.
Defined db script templates and
trusted developer to prepare the
deployment scripts and checkin
to source control.
Apprised developers to vet
database scripts against
development database before
checkin.
Switching to template driven
database scripts saved us a lot of
time. It no longer needed us to
generate scripts by comparing
the databases, a cumbersome
and time consuming job.
Database scripts were
automatically vetted at every
environment and were
stable by the time it reached the
production release. This
minimized database related
release issues.
35. Technical Details #3
Challenges we faced! What we did? What we gained
Compiling configuration
changes from various
change request notes was
cumbersome.
Took environment specific
configuration files to source
control and pushed it along with
build package.
Trusted developer to update
configuration file with respective
values.
Blending configuration changes
from source control to build
package eradicated the chance
of configuration mismatches and
errors.
36. Technical Details #4
Challenges we faced! What we did? What we gained
Preparing build package
was cumbersome.
Used ANT to build Java code
and parse Cold Fusion.
Used NANT to build .NET code.
Automated build and packaging
saved a lot of time.
Increased the release readiness
of the team and reduced post
release production issues to a
great extent.
37. Technical Details #5
Challenges we faced! What we did? What we gained
Careless checkin and integration
issues were breaking build
during release.
Setup Cruise Control .NET as
CI Server to perform nightly
builds.
Nightly build ensured that there
are no build errors and we are
good.
