Training
Leadership in an Agile environment
by Patti Mandarino – December 4, 2012
One of the four value statements from the Agile Manifesto states:
Individuals and interactions over processes and tools.
Two principles supporting the Agile Manifesto are:
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Go, Continuous Delivery
How do I do CD with Go?: Part 3: Traceability with upstream pipeline labeling
by Sriram Narayan – December 3, 2012
You can get good traceability for your builds by using Go’s custom pipeline labels effectively.
Go, Continuous Delivery
Updated: How To Use NuGet With ThoughtWorks Go
by Mark Richter – November 30, 2012
Developers using the Microsoft technology stack have adopted NuGet as a primary dependency manager. NuGet provides a clean way to acquire interesting reusable components from a reliable public source, stay up to date with new versions of the components (or not), and even use your own NuGet private NuGet repository internally.
One of Go’s strengths is its extensibility. Almost anything that can be run from a command line can be integrated into a Go pipeline and value stream.
Go, Continuous Delivery
…Enter Snap!
by Badrinath Janakiraman – November 27, 2012
Last time around, I claimed that taking time to set up infrastructure for builds and baby-sitting a CI server was a less than ideal use of your time. However, I will also say this: I deeply believe that the ability to reliably release your application, early & often, with a degree of quality you feel comfortable with, is an essential aspect of development discipline.
Mingle, Agile Project Management
Bug Triage – How exposed are you?
by Scott Turnquest – November 26, 2012
Our software has bugs. We fix most of our bugs.
So far our team probably sounds a lot like yours. Where we may begin to differ is in how we go about deciding which bugs to fix and how we signal to ourselves that we need to focus on bugs above other forms of valuable work.
Exposure: Another view on bugs to fix
Go, Continuous Delivery
How do I do CD with Go?: Part 2: Pipelines and Value Streams
by Sriram Narayan – November 13, 2012
A Go Pipeline does not necessarily map one-to-one with what is referred to as the automated deployment pipeline in continuous delivery litreature. The automated deployment pipeline is essentially the end-to-end CD value stream. This end to end value stream is often better modeled using multiple Go Pipelines.
Go, Continuous Delivery
How do I do CD with Go?: Part 1: Domain model, concepts & abstractions
by Sriram Narayan – November 13, 2012
In this first of a six-part series we’ll do a deep dive into doing Continuous Delivery with Go
The official Go documentation explains some key concepts with the help of a nice diagram:
Go, Continuous Delivery
Automate Almost Everything
by Scott Turnquest – November 2, 2012
Where’d my tail go? – Using Continuous Delivery principles to shorten our release tail
This is the story of how the ThoughtWorks Studios Mingle team used continuous delivery principles to reduce the testing period at the end of our release cycle from 2-3 weeks to 1 day.