Month: February 2023

February 23, 2023

Greg Thomas

The Agile Goal of Multiple Teams and Multiple Processes

Multiple Teams can have multiple processes and systems for what they do. This isn’t a bad thing – build the process, methodology or system that fits the team for what they are doing. The Agile methodology for software is built around tenets to accomplish goals and not implementation details itself. If you are working with multiple teams with multiple ways of doing things and each team is performing well the question should be are you able to align the processes into one display of how everyone is doing – getting from comparing bananas and oranges to applying that are honey

February 22, 2023

Greg Thomas

Make your Delivery Process Valuable

Every process has to create value, otherwise, why are you doing it? TPS Reports are an example of a process that creates no value and/or the value it creates might be restricted to one (and not the person having to do the work surrounding the process). The tricky part of any new process is getting everyone to understand what it leads to.  It’s entirely possible they might not get it because they don’t see the problem you need to solve, that doesn’t mean you don’t need a process, it means you have to educate them on the problem. Each process

February 21, 2023

Greg Thomas

What Path do you Seek?

You can probably do many things – and are great at all of them. It doesn’t mean you should be doing all of them… because you probably don’t have the cycles to do all of them as well as you can if you were focused on just a few. When you look at successful training programs – Salesforce, Google – they break their training down into manageable paths focused on answering the one key question – “Where is your Focus?” You can’t run all paths at once, pick the few that will help you succeed.

February 20, 2023

Greg Thomas

When Styles Collide

Everyone has a different style of getting something done. Whether leading people, coding, testing, strategizing or writing requirements. No one does it exactly the same way – and that’s great because then we can learn from each other. When your style collides with someone else’s, the immediate reaction will be – “I do it this way and I know my way works” – because… well… it has. But the second thought you should have is – “Will it achieve the same goal as my style?  Will I get what I need out of it?  Am I losing anything from this?”.

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

© 2025 Rambli by Greg Thomas. All rights reserved.