Articles for category: Delivery

November 6, 2018

Greg Thomas

The Kick-Off

There are always two competing agendas occurring at a Project Kick-Off. The Customer I want it yesterday, here is everyone you need to meet, start delivering. You (the Developer) I’d like to tell you how we’re going to delivering your project. From the onset, they are in disagreement because one is driven by immediacy and the other by a pragmatic approach. The developer wants to make sure they do it right for the customer the first time, the customer wants it done now because the problem has become so severe they cannot wait any longer. But there is always time,

October 31, 2018

Greg Thomas

Experience! Experience! Experience!

No not the experience and/or qualifications you need to get a “job”. I’m talking about the experience you feel when you try something new for the first time. What’s the expectation that a customer can be up and running with your product in how you have shown it after they purchase it? One Hour? One Day? One Week? Does that line up with the reasons as to why your customer purchased your product? I run this blog on WordPress and some of the themes that are premium in nature, are downright painful to install, always require support and never install

October 26, 2018

Greg Thomas

Our Greatest Failure if Software Delivery Teams

Yesterday’s unit test results. Last week’s build breakage. Last month’s bad update. Last year’s roll-out that went sideways and didn’t make it in until the third try. These alone aren’t bad when they occur, but when we hold onto them, reference them in meetings when someone wants to try something new, test out a new idea or approach and use them as justification for not implementing change. This is when they become our biggest failure. Holding onto what didn’t go well for you yesterday is a surefire ticket to never let your team grow, never let yourself grow and never

October 22, 2018

Greg Thomas

Nimble, Swift, Agile, Waterfall and River

Ways of doing things? Directions on going down the river? Here’s a secret – “It doesn’t matter what methodology you use.” You could deliver a project using Agile that someone might have used Waterfall to deliver that someone else might be coming up with their own homegrown solution. What matters is software being delivered, that makes sense and provides value. Start there, work backwards and figure out what your team needs to make it happen.

October 11, 2018

Greg Thomas

The Uninitiated Requested Upgrade

Two instances today of upgrades that went sideways as of late. While running a critical program my desktop upgraded.  I had to dig into the settings to force it to notify me (the audacity) when it can decide to reboot. And restart my program again, losing 8 hours of work. This process could have been tweaked with a simple pop-up – “Hey, it looks like you’re doing some work, want us to wait?”. I have other ideas, but that’s the simplest (and they know work is going on, they built the programs). The second was a request to upgrade a

© 2025 Rambli by Greg Thomas. All rights reserved.