Chris is a Development Manager at Redgate. His job is to lead agile software development teams; helping them to regularly deliver valuable software for our users, solve their own problems and continuously improve how they work.
At Redgate, encouraging personal development in our teams is fundamental to building amazing products. As well as developing new skills for employees to apply to their current work, personal development has a huge impact on job satisfaction. Drive by Daniel H. Pink discusses the principals behind what motivates us. He suggests that three main... Read more
When anyone visits Redgate HQ in Cambridge and takes a tour of the software development teams, their reaction is invariably the same. They’re surprised at the dress code (we don’t have one), they’re mystified by the walls plastered with Post-it notes, and they’re intrigued by the giant bean bags and cake everywhere. That’s the... Read more
As a project manager, the process of deploying software can be fraught with anxiety and dread. I can think about numerous times in my career where, in the shadow of an approaching release deadline, the thought of having to deploy our application was akin to contemplating an imminent visit to the dentist. In fact,... Read more
“Every software development team should have a fully automated deployment process.” That’s according to pretty much everyone I meet at conferences and events. It’s not even a debate. It’s a declaration. In actual fact there are only a small percentage of software development teams who have a ‘one-click’, totally hands-off, fully automated deployment process.... Read more
I’m a project manager, so unsurprisingly I can find myself in animated conversations with other project managers regarding how best to manage the work that our team members are doing. We all have our favourite techniques and methods, but the process generally starts with making the work each member of the team is planning... Read more
In a typical agile software development process, sprint retrospectives are meetings run at the end a development iteration. In those sessions the team looks back on what they have done and how they have done it, and decides what they can do to improve. More succinctly, the team inspect and adapt. In my experience,... Read more