This is a series of blogs of my thoughts on the most important of human endeavours, Work and its associated things like Productivity and Processes. This is third in the series. In this blog we explore the possibility of creating conditions for optimal experience at our work and jobs, more commonly referred to as “Flow State”.
Many organizations today are spending a lot of time and resources to try and create conditions for optimal experience at work, more commonly referred to as the “Flow State”.
A lot of sports-persons and artists refer to it as “Being in the Zone” or “In the groove”. With “Flow” productivity is high, creativity is enhanced and it is a rewarding experience in itself. It increases well being and happiness. In turn, well being and happiness increases engagement and productivity. This sets up a virtuous reinforcing cycle. Sir Richard Branson says, “In two hours in flow I can accomplish tremendous things.” Read More…
We’ve added a couple of new features and enhanced some existing ones to make SwiftKanban even more compelling to teams working with Kanban! Here is a quick rundown -
Highlight Cards at Risk of Delay
Wouldn’t you love to have your Kanban board tell you what cards might be about to get delayed? SwiftKanban can now give you visual cue when cards may be at risk of delay! You can configure the number of days you want a card to be highlighted before the card’s ‘deadline date’. You can do this for different thresholds on different boards – this is a project level setting.
How do you design your first Kanban board? This thought was triggered by a question posted by someone who works at an agency and were trying to figure out the best way to set up their Kanban board. The agency appears to be a small team working on multiple customer assignments and they wanted to use Kanban to track all of the work they do.
I’m sure most of us have seen the famous cartoon strip about requirements management – which highlights what the customer asked for vs. what they really wanted!
The same applies to software or product development processes. Most teams have a general idea of what their development process is or looks like. In fact a lot of them have the processes well-documented as well (altho’ not many people might be able to find that documentation! But that is a different post.)
We’ve added some new features and made quite a few enhancements to SwiftKanban over the past few weeks. This post details some of the highlights.
New! Net Work-Time Report
Get a report of the ‘net’ work-time for each card while the card was in an ‘in-progress’ lane, and was neither blocked nor unassigned. This enables you to compare the actual work on a card to the initial estimation. Read More…