Articles for category: Delivery

February 19, 2023

Greg Thomas

Building Software Processes

Here is how you build a software delivery process; What bugs you about your current system (this is whiteboarding time)? What do you want to get out of the delivery (metrics, delivering faster, more on time, a more relaxed team)? Who is involved in the delivery (either stakeholder or the roles within the process)? What things do you care about in the process (what matters to people – trust, empowerment, control, etc)? That’s it, it doesn’t matter what system, process, workflow, or automation you use, everything will spring out of those 4 questions.  The key to building any software process

February 18, 2023

Greg Thomas

What goes into Logs?

What happened? (Debug/Verbose, Info, Warning, Error, Critical) When it happened. (Dates but don’t forget timezone offsets) Why did it happen? (who did what and where) What you should do next. (is there a KB?  Does this happen often) Those are the four components of any great log file, if you have those in your file the people that have to go troubleshoot will thank you kindly. The fifth component of any great log file is ensuring people know where to go and find the information, disseminate it, and do something with it.

February 15, 2023

Greg Thomas

The Clicking Moment

The clicking moment is an easy one – it’s when it all comes together and everyone goes “oh look it worked”! They don’t see the hours, days, weeks, months, and maybe even years of work that went into getting it to that point – all they see is when it clicks. That’s okay, you know what went into making that happen, the drive and initiative for it to happen. You know what it takes to make things click and that’s what matters to be able to lead yourself and others there.

February 9, 2023

Greg Thomas

When to Break a Cycle

Cycles are great to get into, they are predetermined, we know the outcome, and we can see the start, middle, and end – they are awesome at helping generate predictability and visibility into what we are doing. But they can go bad, they can wear you down, and they can take you down the wrong path simply out of habit. When we transition from intent and action to auto-pilot in our systems we fall into the trap of – “this is how we’ve always done it” – which is a defense mechanism to the cycle you are in, not a

February 3, 2023

Greg Thomas

Does the Whole Team Need Agile?

The developers are doing agile. Your testers are doing agile. The Product Team is doing agile. Does your finance, sales, and marketing teams need to do all of their work in agile?  Does your entire organization need to follow agile? No, they don’t. The benefit of agile is to deliver units of software that can be viewed and accessed by these teams in a more iterative way so they can see the building of the solution to the final product. Teams outside of your software delivery will never sell the iterations, they will always want the completion solution, the iterations

© 2025 Rambli by Greg Thomas. All rights reserved.