Nimble Blog

This is a common dilemma for teams wanting to use Kanban for ‘fixed price, fixed cost” projects.  On the one hand, you have a business demand to commit up-front to a timeline and scope (and cost) to deliver a product; on the other hand, you have a promising tool – Kanban – that completely does away with any concept of time (or scope) bucketing but yet promises higher value and better quality to the customer.

Hello again! We’ve improved our card search capabilities with this update and you now have the ability to track throughput for every Smart Lane!

Sometime back, we published a blog post Due Dates in Kanban Systems – which drew some flak from some folks who objected to the line of reasoning in that post. However, one of the commenters made a good point – that it made sense to have Due Dates in a Kanban system if in fact the process being visualized on the Kanban board already needed Due Dates.

Projects are often executed by dynamic teams. They start with a small core team and as the project gains momentum, add resources over time. This is commonly seen in IT service organizations that do fixed price projects. Fixed price projects have a defined scope that needs to be delivered within a contracted budget and within a negotiated timeline. For the purpose of this experience report, “Dynamic teams” or “Fixed Price projects” will be used interchangeably.

Energetic, responsive, trying harder – those were some of the best compliments we received from our customers.  As one of them, who switched from a competing product to us, said, “It looks like you guys are always trying harder and better than the rest of them.” Absolutely!

There is a lot of attention given to Lean/ Agile product development teams around the work done and the (Lean/ Agile) processes adopted in by the Dev team once a set of features (backlog items) have been identified for a set of sprints (scrums) and/ or Releases.

That was the question posed in a recent discussion. The question further provides the following details – “I work within an agile team. We have a released product and we are still working towards a future release. Every sprint we receive anywhere from 0 to 5 tickets to fix bugs in the released product. Our team is composed of software engineers (to handle new development) and maintenance software engineers ( to handle tickets).

Digité Infotech, Pvt. Ltd. today handed over a check in favor of the Prime Minister’s Relief Fund (India) towards the efforts to rebuild and provide relief to the flood-affected regions in the North Indian states of Uttarakhand and Himachal Pradesh. The donation comprised a day’s salary of the company’s employees and was the result of a spontaneous move by the Digité employees to do something to help.

We’re back again with some small, but really useful improvements in SwiftKanban. Here’s a quick overview of the new enhancements added in SwiftKanban v3.2:

We’re back again with some small, but really useful improvements in SwiftKanban.

After we released our 3.0 version with a complete UI uplift, we were eager to add-on to it for a richer user experience.

Mountain View, CA