DZone
Agile Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Agile Zone > Does Going Agile Save You Time?

Does Going Agile Save You Time?

Agile development teams are almost 25 percent more productive than their peers, according to recent industry studies.

Yaniv Yehuda user avatar by
Yaniv Yehuda
·
May. 14, 16 · Agile Zone · Opinion
Like (3)
Save
Tweet
4.62K Views

Join the DZone community and get the full member experience.

Join For Free

Agile development teams are almost 25 percent more productive than their peers, according to recent industry studies. Agile development methodology allows developers to ensure “more scope delivered within the same time frame”.

With Agile development, time becomes a valuable resource. Iterations are short, and there is less time to review changes or perform rollbacks. In order to support these abbreviated, yet more frequent iterations, and ensure the delivery of high quality results in a timely manner, development teams require extensive automation. This automation should consist of a series of automated testing procedures (from regression to acceptance), as well as automated build and deploy processes, designed to keep the overhead associated with the delivery of the final “product” at the end of every sprint at a minimum.

While the need for automation is important on the application/software side, it becomes even more crucial when it comes to handling database changes. Unlike application change deployments, where developers can simply copy and replace the executables, databases contain business data that must be preserved. Therefore, the focus of database change deployment is about the path from the current state to the desired one (the output of development activities). While application deployment processes repeat themselves – new executables are copied to the correct path – database deployment is, by definition, a onetime process, since after the first deployment the current state has been changed. So a new deployment script that takes the current state into consideration must be generated for future changes.

A comprehensive database change management solution can deliver the needed automation. With the right solution in place, one that goes beyond compare-and-sync tools, to provide risk free full impact analysis, development teams can enable fast and automated deployments, nightly builds, or partial builds based on business requirements. This, in turn, can even further increase the productivity of Agile development efforts, while minimizing costs, mitigating risks, and reducing downtime.

For more on this topic, read our free eBook: In Database Automation We Trust

agile

Published at DZone with permission of Yaniv Yehuda, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Cypress: The Future of Test Automation! Advantages and Disadvantages
  • Functional vs. Non-Functional Requirements: The Full Guide, Definitions, and Technical Examples
  • Federated Schema Design
  • 9 Strategies to Improve Your Software Development Process

Comments

Agile Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo