On 6th March 2018 Redgate’s Product Division and Foundry ran their first internal conference. On the day after the event we, the conference organizers, asked everyone who attended to give us some feedback. Here’s what they told us.Read More What did Redgaters think of our first internal conference?
The need to inspect and adapt is the fundamental concept at the centre of the agile software development movement. However, it often seems that the drive to inspect and adapt is only deliberately applied to what we build and not how we build. This means how a team works together, how they use the technologies at their disposal and how they apply processes can go unimproved.Read More Inspect and adapt how you build as well as what you build
I attended an excellent talk by Jon Terry, the CEO of LeanKit, who talked about the approach LeanKit took to help their teams stay lean and make good decisions as they grew from a small start-up to a medium-sized enterprise.Read More How LeanKit helps it’s teams make effective decisions
One way to keep Retrospectives fresh is to set explicit goals for each session. However, just choosing a goal isn’t quite enough. You want to choose a Goldilocks Goal that opens up the discussion ‘just right’.Read More Goldilocks Goals: How to keep Retrospectives fresh and engaging
We’ve created a set of “working agreements”, which call out best practices and common aims we have, with a view to embedding these in all projects in the division and encouraging consistency.Read More Encouraging convergence: Our project management working agreements
Over the years, our development teams have evolved, disbanded and been created. Most of the time, each team has been given full autonomy over how they work. We have ended up with is a collection of teams with disparate approaches to the same mission – creating great software.Read More Encouraging convergence: Putting a framework around agile team autonomy
If times are tough on an agile project, whatever you do, don’t cancel the Retrospective meeting. If you think that having the team in a meeting room for one hour every two weeks is going to make your project fail, then it’s going to fail anyway.Read More When the going gets tough, don’t cancel the Retro