Articles for category: Delivery

March 5, 2018

Greg Thomas

Questions to Always ask when giving a Demo

What do you like? Because there will be things that they like. What do you not like? Because there will be things that they will not like and this is much more important than what they do like. What do you feel is missing? Because once they see it, they will start thinking about what they want to see next. Are there changes we should be making? Because having a thought for change or what might be missing, doesn’t necessarily mean you have to do it. The questions themselves are not hard to ask, it’s the answers that generate that

February 27, 2018

Greg Thomas

Delivery

Deliveries are our most visible “wins”, but they are a double-edged sword.  Leapers are always aware to not let things like process, methodology, meetings, extraneous decision making and other activities become slated as “deliverables”.   Attending a meeting is not a delivery. Sending in your status report is not a delivery. Ensuring your team knows when the customer is expecting those last second hot-featured fixes and having it in their hands a day early IS delivery. Helping your team by taking on the grunt work, reducing their bug piles so you can get the latest release out the door (maybe

February 19, 2018

Greg Thomas

What is a Core Feature?

I had become very dismayed with the default podcast on my iPhone lately. The biggest feature that was driving me over the edge was the “You haven’t listened to this in awhile, we’ve stopped downloading it” function which cannot be turned off. There are two problems with the implementation this function; The assumption that I have not listened to casts in awhile because I have chosen not to do so (when this is wrong, the reason is I get busy sometimes). I cannot disable this function (a simple on/off switch). The lesson I took from these problems is that if

February 14, 2018

Greg Thomas

Product vs Project

Everything you code is a product. Whether it’s for an internal user or an external customer. They are both paying for it. They both need you to support it. They both want it yesterday. You wouldn’t treat one different than the other. So now we know we are building products regardless of who our customer is and what schedule or process we use to deliver it. It’s all product. There is no project.

February 9, 2018

Greg Thomas

When the Dates Don’t Change

The people sure do to make them happen. Not the process. Not the code. Not the features. Not the bugs. Only the people and their dedication to getting the product done and shipped to your customers. (sometimes we all need to be remind of what it is that really changes when we ship to meet the date and change nothing else).

© 2025 Rambli by Greg Thomas. All rights reserved.