Showing posts with label continuousDelivery. Show all posts
Showing posts with label continuousDelivery. Show all posts

How do you apply changes to your codebase? When should we merge the JoeBranch?

At our yearly 1 week Zühlke web camp a couple of us took the opportunity to share experiences with branching and release techniques.

code changes workshop

TL DR;

  • Focus on Continuous Integration
  • Every change that you have locally is a branch (a code version that is different than main)
  • Every kind of branching delays Continuous Integration
  • Only a healthy code base with a “green” Build + Automated Tests let you sleep like a baby at night.

How do you continuously improve yourself? An interview with SSW TV

This went viral on YouTube the other day, aka my mum clicked it 100 times.

Me and Adam Stephensen rambling around Clean Code, Quality, Releasing Software more often, Continuous Delivery and all things that make developers happy.
Figure: Me and Adam Stephensen rambling around

The Agile Manifesto 3.0

This is the 1st principle of the Agile Manifesto from the year 2001 that you can find on http://agilemanifesto.org/

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
Figure: First principle of the Agile Manifesto from 2001

Combine Scrum and Continuous Delivery to drive Innovation

After publishing the paper on scrum.org here, I wrote a german version for the dotnetpro magazine of January 2013.

Check it out!
And make sure to buy the magazine!

Innovation through Scrum + Continuous Delivery [VIDEO]

Update 2014-11-05: Fixed the video link since the Scrum.org Video Channel moved.

I almost forgot to publish this recording here… Smile


Figure: My talk on youtube https://www.youtube.com/watch?v=TMyhhuQPEow

  • How often do you release your product to your end users?
  • How often do your end users see and use your product?
  • Do you release in sync with your Sprint length, after the Sprint Review?
  • Is the Sprint Review meeting the only valid release point?
  • When do you plan your releases?

See how the cadence of Scrum and Continuous Integration can help you build the right thing, and when implemented properly, release it on time to ultimately deliver superior value to your customers.

Use Scrum + Continuous Delivery to build the right thing

How do you get feedback?
Figure: How and how often do you get feedback?  flickr
The two topics “Scrum” and “Continuous Delivery” kept me very excited in the last years, which resulted in two presentations and a whitepaper for scrum.org.

Latest Posts

Popular Posts