Learn about UrbanCode: https://ibm.biz/learnurbancode Learn the basics of UrbanCode Deploy and Deployment Automation. Get started here: http://www.ibm.com/cloud-computing/solutions/cloud-devops/automated-application-deployment/

1. “Worldwide
confusion
about
app release
and
deployment!”
“Worldwide
confusion
about
app release
and
deployment!”
What’s true and not true
MisinformationMisinformation
ReignsReigns

2. Developer hasn’t seen
Daylight in weeks
Family weeps for
lost loved one
Only one way
to deploy
enterprise apps
Only one way
to deploy
enterprise apps

3. Only way to deploy
enterprise apps.
Deployment setups that are
truly automatic don’t need
special scripts—they work
with the tools you already use.
Automation means automatic

4. loves
deployingDevteam !
“Not a special skill,”
many say
No details missedNo details missed

5. Only way to deploy
enterprise apps.
Don’t make your developers
design the deployment process.
Set it up so they can test first
and then deploy.
Deployment is a specialty

6. Enterprise-
level
releases
“easy to do”
Specialized tools deemed
unnecessary
Magic spreadsheet
tracks everything!

7. Sure, emails and spreadsheets
are OK for simple releases. But
what about complex, interdependent,
big releases? It’s impossible to
collaborate and trace those without
specialized tools.
Enterprise apps need more

8. Quality plummets with
automation!
Quality plummets with
automation!
“I should do
it manually,”
says exhausted
human.
Computers unfit
for repetitive tasks

9. When you automate, you let
computers do what they do best.
Plus, you’ll get tracking features
to help keep things straight.
Repetitive tasks are what
computers do

10. Savior of release coordination, developers say.
spreadsheet hailed!spreadsheet hailed!
great use of
“Repetitive manual tasks:
your time.”–management

11. Only way to deploy
enterprise apps.
Release coordination tools make development
faster, easier, and more precise.
Dealing with the spreadsheet is a
job in itself

12. Large Release
Seamless!
Large Release
Seamless!Interdependencies
“no biggie,” teams say
Conventional wisdom:
small, frequent changes
not profitable

13. Small, frequent changes are
easier, faster and less risky to
make. Automation helps free
developers to troubleshoot.
Many hands make lighT work,
and all that

14. Automation and build:
No transition
prep necessary
completely
separate
completely
separate
“We just hit a button, and
everything was perfect”

15. Test builds before they go into production.
Versioning them makes tracking simpler.
Automation requires preparation

16. Operations rejoices
over bottlenecks!
Operations rejoices
over bottlenecks!
No culture
changes in
sight, thank
goodness
Management “elated”
to hear of backlogs

17. If you’re going to use
release and deployment
tools, get your teams
ready for a change in the
way they work.
Backlogs are bad

18. All Problems
Vanished!Developers stymied
worldwide
Developers stymied
worldwide
“They were here, we automated,
now they’re gone,” dismayed
programmer says

19. There will be resistance and
frustration at first. Stick with it.
Getting a payoff takes time and work.

20. You’ve heard all the myths about automating
application release and deployment. Now let’s
get to the truth. Check here for the details.
go now