Do you find Portfolio and Project management difficult to blend in with lean and agile techniques? If yes then you definitely should try out LeanKit Kanban. With its recent ground breaking release specifically focusing around portfolio and project management at multiple levels and giving handle to users to drill down as necessary into kanban boards along with roll-up lean metrics, Leankit has demonstrated its prowess with kanban tools space.
Have you ever gone through the emotions of transitioning a team who are deep rooted with traditional waterfall implementation to a lean, agile way to deliver projects? I am sure most of you did. The biggest challenge while I was going through this phase was understanding the dynamics and behaviour of Agile teams, what an agile team should be and how do I mould the team to be agile. Mike Cohn in his book "Agile Estimating & Planning" talks about what "Agile Teams" are. I did like the chapter while i read a year ago but only understood recently on what he meant while trying to move my project team from traditional waterfall and chaos to much more agile.
When it comes to a tool that's designed with pure Kanban principles in mind and has matured over time, the one product that comes to my mind is LeanKit. Jon Terry, COO of LeanKit has been kind enough to speak to us on the recent partnership with VersionOne, the differentiating factors of LeanKit, Key challenges developing the product, Next Kanban Trends and much more.
Kanban, also spelled kamban and literally meaning "signboard" or "billboard", is a concept related to lean and just-in-time (JIT) production. According to Taiichi Ohno, the man credited with developing Just-in-time, kanban is one means through which JIT is achieved. Kanban is not an inventory control system. Rather, it is a scheduling system that tells you what to produce, when to produce it, and how much to produce.
Here is a Kanban tool that is packed with features and proved value for money for many of those implementing Kanban as their delivery framework. Swift-Kanban was launched few months ago and soon has grown as one of the leading player in Kanban tools world. It was good to see a team effectively taking customer feedback and promptly developing the product as promised. We spoke to Nitin Ramrakhyani, Product Owner for Swift-Kanban at Digite this week.
One of the great threats to the functioning of a team is a set of 5 dysfunctions that could plague the team. These dysfunctions build upon one another and could negatively affect the team in such a way that the team would eventually crumble.
VersionOne, recognized by agile practitioners as the leader in agile project management tools, announced the general availability of its latest release featuring an all-new user interface (UI). Inspired by feedback from customers and partners, VersionOne designed the new UI to accelerate user adoption, improve usability and increase productivity.
Scrum is one of the biggest process invention but it does not guarantee success. Even creators of Scrum accept that more than half of the Scrum implementation does not go well. Why is that? Scrum is critical but what is more critical than Scrum? Moving from waterfall model to Scrum is a welcoming change that makes people think in the right direction. So what is the right direction?
Traditionally, agile teams have always discouraged usage of agile tools for all the right reasons. However with the ever changing world it has become clear that an agile/scrum/kanban management software will greatly simplify life of project teams. Well if you are the one who just want about enough features to manage your kanban process, good news there is a very simple hosted product new to the market called "InkPlanner".
Agile tools have come a long way right from a simple Index Card to a full fledged software tool to manage enterprise level agile implementation. There always existed reservations on whether to use or not to use agile tools. Agile tools have not been used effectively so far either sometimes as a best practice to keep agile simple or at times a going by preference to use human interactions as much as possible than tools. I come across many small teams still using excel sheets which usually ends up with duplicating effort and unnecessary maintenance. While its good to use tools, lets see what are some trends or changes we are seeing developing agile tools this year.