Did you ever experience the phenomenon were the project status is red but getting greener and greener when climbing to the to top of the management ladder? This is named “Watermelon reporting”. This video explains the main reasons for this behavior and gives the right tools to fight messy reporting processes. You will learn practical tools and ideas that can be used to get rid of or at least minimize dysfunctional reporting behavior in your own teams and company.

What do Lean, Kanban, Jazz and Origami have in common… and where do they differ? In this presentation I will talk about important aspects of Lean and Kanban that I consider to be key to their success and to be what sets them apart form other approaches and methodologies such as Agile and Scrum, yet could be easily ignored.

There are a lot of different situations in software projects with distributed teams. You can seen both successful and disastrous projects in terms of the ways communication and coordination was designed. People can be pretty much on the same page in terms of project goals while seating in different offices and in different countries. You can also witness people being completely off the track, suffering and losing motivation. Based on experience, this video tries to explains what make some projects good places to be and some not.

This video presents a case study of a small team which decided to use Lean and Kanban to rapidly iterate over the development of the BBC iPlayer.

In this video, Sam Phillips discusses the best ways to organize your teams and plan your projects. Sam is currently an agile evangelist in a start-up and was previously Technical Director for a Ruby/Rails software agency.

This very short video gives an overview of the Kanban practices for project management in the context of software development.

To date, much of the focus on Agile transitions have focused on the team. But the business side of an organization, and the management that serves them, are not truly interested in the mechanisms of Agile teams.

At the Lean Kanban Central Europe conference in Munich, David J Anderson clarifies the way in which Kanban breaks the context for Brooks law. Brooks’s law is a principle in software development which says that “adding manpower to a late software project makes it later”.

Showing concepts and techniques of using a pull-based system to manage JIT development approach. This video covers Kanban as a way to visualize your workflow and ensure you are working on the most valuable task at hand.

Agile is the only way to go for a fixed price project, because with Agile, a project is 50% complete when 50% of the features have been completed. With non iterative processes that don’t regularly produce a product in a stable state, you just don’t know how complete it is. Completing fixed price projects is a lot about risk management. This presentation explains how to identify and minimize the risk in the bidding, planning and execution stages of a fixed-price, fixed-scope software development project.