Articles for category: Delivery

July 29, 2023

Greg Thomas

Does Everyone know the End Goal?

If everyone is not on the page with what the end goal is, then when it’s time to celebrate the delivery of the end goal not everyone will be happy. If the goal is taking considerably longer than originally thought, it’s important for you to ensure that everyone is still on the same page as to what the end goal is and what the team is working towards. Workloads and priorities shift and it’s easy for anyone to get tunnel vision into what they are doing and lose sight of what they were originally trying to accomplish until it’s too

July 28, 2023

Greg Thomas

The Stunted Start

Priorities are going to push your goals down, you might have 7 things you want to accomplish but can only get to 5 on a good week. You can either turf the other 2 or switch up the priorities – that’s the either/or option. The other option is to take a look at your 5 other priorities and think about what you need to do to enable the other 2 to happen, how can you create more time and space to be able to work on them without sacrificing the other 5. Sometimes it’s not about dumping what we didn’t

July 26, 2023

Greg Thomas

Training your Team

Only you know the training your team needs and only you know the path it requires for them to get there. They might be able to see it on the first day and it’s up to you to figure out how to get them there. You can either hold it into the very last day, or you can start from the beginning, map it out, do bit by bit every day, week, or month and plan for the moment when they get there and go – “I know this”.  Because when training the team, it’s not today they are being

July 22, 2023

Greg Thomas

Failure to Sprint

When you learned how to walk and fell flat on your face the first time did you give up? (Maybe for a bit). The same goes for Sprints and any new development process you are implementing – it’s not success out of the box – it’s a slow burn growth and then mass acceleration once it clicks with your team. If you fail to sprint the first time, start jogging the next (remove tickets), build up a tolerance, figure out what works for your team, and then try again. But don’t throw it all out because it didn’t work the

July 19, 2023

Greg Thomas

Good Backlogs

Everyone needs a backlog. If you don’t have a backlog, it doesn’t mean you are done, it means you don’t know what comes next. And that’s the value of a backlog, knowing what comes next, and taking it into account when building new features and planning for the future. When you start building out your first release, you plan for two iterations – the first release and the backlog – one is to deliver the now, and the other is to deliver the future.

© 2025 Rambli by Greg Thomas. All rights reserved.