Articles for category: Delivery

June 19, 2024

Greg Thomas

The Lost Sprint

You want to reduce your lost sprints when it comes to building a release. Lost sprints happen – customer bugs come in and they derail everything you’re doing.  Or a seemingly well-estimated bug blows up in your face and ends up becoming a feature that still needs to be done this sprint, but everything else will be pushed out. The sprint becomes lost when more and more of your team starts to work on these unplanned activities and continually pulls in more of your team. How do you stop losing sprints? Whoever is setting the sprints, knows the landscape of

June 16, 2024

Greg Thomas

All Problems, All the Time

Problems are the bread and butter of your success. How many can you solve? How fast can you solve them? How do they scale? How much effort do they take? What is needed to fix them? When hiring, you always want problem solvers because no matter what they know, have on them or know through their network – they’ll be the ones to figure it out and that’s what you need.

June 14, 2024

Greg Thomas

Know your Basics

I saw this picture the other day and it speaks volumes, not only for sports but for work as well. Your basics are what set you apart from everyone else. Knowing what they are is what makes you indispensable because then you can start focusing in on them, refining them, and making them stronger. But if you don’t know what your basics are, what your fundamentals are – then you’re just practicing everything, everywhere and not getting anywhere.

June 7, 2024

Greg Thomas

Overly Complex Configurations

Any piece of software has a set of configurations, toggles, and switches that make it come alive. The configuration is what makes the software work for your customer and makes it “their own, unique copy”. Four things a configuration should always have; A place to go and make the change, not forcing the customer to jump here, there, and everywhere. Settings that do what they are supposed to do. Be simple in their implementation, if it can be explained simply by the developer, the end user will never be able to consume it. Work. The worst thing is when a

June 4, 2024

Greg Thomas

It’s Not Your Code

That’s the lesson I learned many years ago writing my first legit lines of code. It’s not yours, it’s not theirs, it’s ours. So if I get a bug and have to go in and fix it, no harm, no foul, I’m fixing our code. There is no ownership of code, there is no baby, and there is only our collective code being distributed to our customers. Yes you put a lot of effort into writing it, but once it hits git, it’s everyones.

© 2025 Rambli by Greg Thomas. All rights reserved.