Crucial Conversations happen where the stakes are high, opinions vary and emotions run strong. These situations arise all the time in agile development teams and can lead to misunderstandings, inaction or strained relationships. In this post I'll explain when Crucial Conversations can pop up and give you some tips on how to tackle them.
When people talk about why they adopt an agile approach to software development, they talk about the many benefits of delivering working software iteratively. Rarely do I hear people call out the key reason why we should be taking an agile approach; it's part of the answer to giving people fulfilling and rewarding work.
At the end of June Redgate's Product Development organisation ran a retrospective session to review how things have gone in our corner of Redgate in the first half of 2019. This post explains how we ran the large scale retrospective and what we discovered by doing it.
How Redgate has learnt from our first ever internal product development conference to make this year's event, Level Up 2019, even better.
I attended the Agile Manchester 2018 conference to share Redgate’s journey with team autonomy and learn from other agile practitioners. Here are my highlights from the conference and my biggest takeaway - it's all about The Why.
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.
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.
The 'Agile Release Train' has been popularised as part of the Scaled Agile Framework - a set of guidelines aimed to bring agile software development to the enterprise and programme delivery. In the framework, the train metaphor is used to describe a series of iterative releases set to a strict schedule that multiple teams must abide by... Continue Reading →
Last week, my team released a beta version of the product we have been working on for the last six months - SQL Lighthouse. This week, everyone on the team has been reminded how motivating it is to see an idea you've been working on start to gather recognition and, more importantly for us, users. At... Continue Reading →