Continuous Development Sahil Kumar
Reduce Batch Size Increase Tempo of production
Gives the developers a better chance to innovate/experiment
Teams stay in the flow of development when the feedbacks come in, hence resolution is prompt.
If feedbacks come in slow, batch size of the code with the developers increases, hence more work may be needed to be retra...
In case of large batch sizes of code, integration is usually the last step, and is error prone
Working with small batches, features are deferred less since they need not be 100% complete before deployment, thereby kee...
Continuous deployment, does not have the idea of hot fixes.
In case of working with large deployments, the padding estimates of the people involved is usually an overestimate, thereb...
If something breaks, the rest of the team does not deploy until the problem is handled.
Instead of individuals concentrating solely on their progress and deliverables, continuous deployment involve the whole te...
Upcoming SlideShare
Loading in …5
×

Continuous deployment

724 views

Published on

5 Comments
1 Like
Statistics
Notes
No Downloads
Views
Total views
724
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
7
Comments
5
Likes
1
Embeds 0
No embeds

No notes for slide

Continuous deployment

  1. 1. Continuous Development Sahil Kumar
  2. 2. Reduce Batch Size Increase Tempo of production
  3. 3. Gives the developers a better chance to innovate/experiment
  4. 4. Teams stay in the flow of development when the feedbacks come in, hence resolution is prompt.
  5. 5. If feedbacks come in slow, batch size of the code with the developers increases, hence more work may be needed to be retracted.
  6. 6. In case of large batch sizes of code, integration is usually the last step, and is error prone
  7. 7. Working with small batches, features are deferred less since they need not be 100% complete before deployment, thereby keeping the process dynamic and fast.
  8. 8. Continuous deployment, does not have the idea of hot fixes.
  9. 9. In case of working with large deployments, the padding estimates of the people involved is usually an overestimate, thereby contributing to the slowing down of the whole process.
  10. 10. If something breaks, the rest of the team does not deploy until the problem is handled.
  11. 11. Instead of individuals concentrating solely on their progress and deliverables, continuous deployment involve the whole team.

×