Articles for category: Delivery

March 13, 2024

Greg Thomas

What do you Get from your Status Meetings?

If it’s “not much” – chances are they aren’t as good as they should be. If you are the one running them and that’s your answer, I’d put a pause on them now.  Of all the people in the room, you’re the one who needs to be getting the most from those meetings and if you’re not, well there is a big, big problem. And if you don’t know what you need to get out of them, chances are your team doesn’t know either. You don’t need a meeting that gets you nowhere, you need value and this isn’t giving

March 7, 2024

Greg Thomas

The First Step

The first step in anything is yours to take. It’s yours because you know what the first step is and if you don’t take it, you’ll wish you had. No one said it was going to be an easy step to take. But you’ll make it worth it and never look back.

March 4, 2024

Greg Thomas

Breaking Code

Code is meant to be broken, reiterated over, broken again and again and again until it cannot function anymore. That is what code is meant to do. It works, it changes, it breaks, it gets fixed, it works again. Welcome to coding! Let the everlasting Frustration and Joy begin.

March 1, 2024

Greg Thomas

The Evolution of the Mute Button

When I used to build Contact Centre Software, I marveled at the impressiveness of the MUTE button – it worked 100% of the time without fail – and thank you so so much. Now it’s a joke when it comes to video conferencing – “you’re on mute”, “you’re still on mute”. We took this great, rock-solid implementation and we made it into a meme and a joke. But for years it was the most rock-solid dependable feature that people knew how to use without fail. Now, we forget about it all the time. Perhaps it’s how we built, hidden into

February 24, 2024

Greg Thomas

The Best Durations for Sprints

I’ve done 1 week to 6 week sprints (yes at 6 weeks we called it a sprint) – if you’re not sure what fits best for you, here’s some guidance. 1 Week – It’s all bugs, it’s all known quantities, you have minimal code and your deployment model is code, commit, deploy.  QA happens when you ship to Production, teams of 1 – 2 developers.  The Theme is “MVP”. 2 Weeks – User Stories are in the fray now, the team is growing, and there are other people in the mix (product management, QA) but the goal is continued output. 

© 2025 Rambli by Greg Thomas. All rights reserved.