This is the second of a series of blog posts trailing our new process-integrated board functionality, targeted at agile development organisations using kanban methodology (as we do).
Sprints are great for initial build projects or overlapping major releases but for steady continuous-improvement based development interspersed with new features, kanban is just easier, more flexible and more reactive.
Standalone smart board software can really help you visualise this stuff and resolve choke points. It can also be of great help in resource allocation, ensuring you’re managing the distribution of work correctly. But it has one major drawback: further bi-directional interfaces to worry about. If the interfaces are not robust, you will need double entry and that’s just the same as saying that your boards will be out of date until the next stand-up meeting - not good.