A look at how to optimize your agile processes by removing any wasteful processes, or as it is known in Japanese, Muda.
A continuation on how we can ensure that we have good user stories and how we can actually go about slicing them up.
A introspective look at how we can slice and break down user stories and the benefits that come with it.
My current client is currently thinking about starting a new project. This got me thinking about some of the things we need to consider when starting up something new. What is the problem?
At my current project we have been doing the standard thing of going to planning sessions and estimating with using planning poker. As of late the project has been running full steam ahead
I recently came across a episode on Agile for Humans where they described the concept of Standup Poker. I was actually quite intrigued by it, and I could see how it could potentially
Recently, I started allowing other people to run our teams sprint planning and retrospectives. So far, this has had numerous benefits for the team such as allowing more time for myself to do
I'm sure a lot of teams have had the issues with people being late for stand up. In the past, I have been on teams that have tried things such as having to
Recently, while chatting to on colleague at work we were talking about setting up an automated deployment process so that the testers could deploy the solution by themselves. At first, I wasn't sure
I recently attended an Agile Training course which was held by some ex-ThoughtWorks employees. I found it to be extremely beneficial and the one thing that the presenter kept hammering on is the
Repetition causes boredom. I'm sure we have all experienced this at some point in our lives. We continue to do the same thing over and over again that our minds go on auto-pilot
As you know, I have recently been doing a lot of exploration on how to run better retrospectives. So far, the team are linking what I have tried and any improvements that we