Difference between Continuous Integration & Continuous Delivery

What is Continuous Integration and What is not Continuous Delivery ?


Often I have been asked “What is the difference between Continuous Integration and Continuous Delivery”. Thought I will shed some light on this topic.

Martin Fowler has described Continuous Integration as “A development practice that requires developers to integrate code into a shared repository … ”

In addition Thought works also explain Continuous Delivery as “An approach in which teams ensure that every change to the system is releasable, and release any version with the push of a button.”

So what is the difference?

Continuous integration allows multiple developers to integrate the source code into a single code base. This helps the team members to identify integration related issues early and address quickly. CI will lead to minimal SIT cycles.


Once you have implemented Continuous Integration, then you should start working towards Continuous Delivery. Continuous delivery will make sure the changes are ready to deploy to production if required.


Fancy to read more ?


Agile Estimates for SSRS Report Development

How to do Agile Estimates for SSRS report development?

Agile estimation is an art and it will take reasonable time to gain experience. These simple steps will help you out.

Step 1: Assess the complexity of the report by asking these high level questions

  1. How many sources have been involved?
  2. How many datasets need to be developed (Apprx) ?
  3. How many Tablix / Table can be expected ?
  4. How many parameters are needed to be generate the report ?
  5. Presentation and formatting requirements
  6. How many no of Sub Reports / Drill Down reports are associated with this report ?

Step 2: Now decide the story point (or use the T-shirt size estimation techniques)


General Guidelines from experts:

  • As a general practice, it is accepted that the Development team will be in a better position to estimate after Sprint-2  or 3. Only after this time, the Sprint velocity can be used for future sprint planning.
  • Avoid estimating like an expert. Always assume that a developer who has got reasonable experience will be doing the development.
  • As a team, make use of the Sprint retrospectives and learn from mistakes.

Frequently Asked Questions:

  1. How to do the estimation for Sprint-1 ?

You could use previous experience to come up with a rough estimation.