Articles for category: Delivery

October 7, 2019

Greg Thomas

Half of Nothing

The beginning of a Sprint and/or Release are exciting times, everyone wants to jump on every feature and story and get them done. Mid-way through either though, we start to realize that we are not going to be able to deliver it all and now we are left with a bunch of half-completed work items. It’s not a great feeling and it’s one Agile/Scrum is supposed to eliminate but still, there’s that pesky feeling we all have that “we can do it”. I know it, I get it all the time. I was having this conversation with a project manager

October 3, 2019

Greg Thomas

Always Thank The Team

Because if you’re not, someone else will and when they do, they will no longer be your team, they will now be on this other person’s team. Org charts do not define who belongs to what team, they only define who you report to. We all know whose team everyone belongs to.

October 2, 2019

Greg Thomas

It’s Not the Late Nights

They aren’t going to kill you. Or the early mornings. Or everything in between. None of that is going to stop your idea from seeing the light of day. From getting your code out there into the wild for people to use. The only thing that’s going to stop it, that might kill it, is if you stop working on it because you’re worried about the Late Nights, the early mornings and everything in between.

September 27, 2019

Greg Thomas

What is Good Enough?

Everyone struggles with what is actually good enough. Not because we all have different levels of what we feel is “actually” good enough but rather because we are at our most critical when trying to decide if our work is at the stage of being good enough to show others. “It doesn’t do these seven things” “I need to make one last edit” “I think it should be red, not orange.” Your good enough, my good enough are very different. The best way to get past it is to ask for someone’s opinion, what do they think (and pick someone

September 26, 2019

Greg Thomas

The Problem with Project Plans

The moment they are created they are out of date. The second you send out the file with the attachment, they are old. When you go to revisit them two weeks later and you need to change all the tasks because the project has changed, they are rendered useless. When the dates don’t line up to the work that is being done (because not everything has been written down) they miss the point. That’s the problem with Project Plans. Fix that and you’ve got something of value.

© 2025 Rambli by Greg Thomas. All rights reserved.