Posted on August 6th, 2013 in Kanban, Lean by siddharta || No Comment
I recently did a short mini-webinar for SolutionsIQ on the topic of slowing down to speed up. The webinar is based on the systems thinking principle that local optimisations can sometimes be bad for the global system.
Often times in agile, we look for process improvement at the delivery team only. This is fine in the early stages when the team is the bottleneck in the process, but after about 8-12 months they stop being the bottleneck. At that point, it makes more sense to look at the rest of the system, rather than focusing on the delivery team alone.
See the video recording of the webinar below:
Posted on June 23rd, 2013 in Infographic, Kanban by Divya Sornaraja || No Comment
Posted on June 6th, 2013 in News & Updates by siddharta || No Comment
We just released a small new feature to the board functionality. You can now add a column policy or definition of done to a column, and it will show up on the board.
Just enter the details when configuring the board columns. Once you do that, an icon will appear on the board and you’ll be able to hover over it to see the column policy or definition of done.
Posted on April 14th, 2013 in Tools For Agile by siddharta || No Comment
One of the main reasons why Agile tool adoptions fail is not because of a lack of features or not enough reports, but something much simpler — “informal requests” that come in which never get tracked. This is not so much of an issue when you have a “strict” agile process where the product owner or equivalent is the only one through which all requests come in. But for many teams, requests come in to team members via email, via phone calls or even just someone going to a team member and making a request directly.
None of these informal requests ever get added to the backlog simply because it is too much of an effort for team members to open a browser, go to the server, log in, and fill up a form. As a result anywhere between 10%-30% of the actual work that team members do might not be tracked. Worse, it is sometimes unimportant work that ends up taking the time of a high priority task.
Compared to other tools, Tools For Agile makes it very simple to add cards to the backlog, but we can go a step further and make it braindead easy. Read on to see how.
Continue reading ‘Solving the “informal request” problem’ »
Posted on April 12th, 2013 in Visual Management by siddharta || 3 Comments
One of the really nice things about putting a chart on the wall is the subconcious way in which everyone knows whats going on in the team. I already blogged about why visualisation is the key to being agile. I’ll just summarise that post here. Click the link if you want to read the whole post:
- Donald Gray’s experiment on three leadership systems shows that in complex systems, decentralised decision making within a framework is superior to centralised decision making.
- In order to make decisions, team members need to have, and understand, the current context in which they are working.
- David McCandles’ TED talk shows how our brain has evolved to process visual information. We can easily understand a picture in under 100 milliseconds, while it takes a few seconds to get the answer to a mathematical calculation like 13 x 24 x 3.
Continue reading ‘Ubiquitous Visualisation’ »