Here’s a few quick points on what I've been up to:
Podcast I'm listening to..
Jocko Podcast - Jocko Willink (American retired United States Navy SEAL) and Echo Charles discipline and leadership... extensively.
Quote from the book
Prioritize your problems and take care of them one at a time, the highest priority first. Don’t try to do everything at once or you won’t be successful - Jocko Willink
Recently, we've managed to successfully release a big piece of code with alot of story points with no major outages! We got our reward of Krispy Kreme donuts as our 'prize', the original glazed ones are my favourite.
With the release of this, now comes with a backlog of testing. In my previous post, I described how to prioritise testing. Similar to the quote from the book I'm reading, test the most important first based on impact. Here's a quick way in which we sort the order of the tests that we do:
- Critical - The most important ticket we can test for the business now
- High - This task needs to be done to achieve our sprint goal
- Medium - This is a ‘nice-to-have’, you can do this after you’ve done your critical and high priority tasks
- Low - Minimal impact, non-client visible and mostly for internal users.