LEGO Flow Game

I recently attended another workshop that was very insightful and also entertaining. This was the LEGO Flow Game. The rules are outlined in the link below if you want to read about how the game works.

It was extremely interesting to see how the different methodologies used (Waterfall, Scrum, Kanban) affected the process and outputs of the work that was being done. I have to say that Waterfall seemed the least affective, but the tasks were very ‘product line creation’ driven so perhaps its not best suited to begin with.

However the presenter, Julian Daddy, who works at the Discovery channel did state that he has done the game numerous times and with every team there is a different result, no matter what the methodology. So the team, the people and the communication is just as important as the process that is used.

The rules are outlined in the page below, but if you run this game yourself feel free to adapt them; as there is not a set in stone way of doing them.

LEGO_Flow_Game 

Advertisements

LEGO DUPLO Tiny Film Festival

I have had the great opportunity to work with LEGO and Disney on the LEGO DUPLO Tiny Film Festival. It was a great experience and I worked with a great team of people.

During this project I had to manage and deliver several simultaneous work streams. From a website build, strategy, creative and design work, and video production. It all came together well and was also a enjoyable project to work on.

Website: www.lego.com/tinyfilm

http://lbbonline.com/news/lego-duplo-disney-and-isobar-have-just-launched-the-worlds-tiniest-film-festival/

FireShot Capture - DUPLO Tiny Film Festival - https___tinyfilm lego com_

Agile and Waterfall: A key difference between the two (A quick note)

In a traditional waterfall approach everything is defined upfront. Plan, schedule, budget etc… In Agile this is not the case. The development is done in cycles and the approach is adaptable to what is happening in the project.

What is the difference between a Project Manager and a Scrum Master?

I searched the internet before writing this post and did find a lot of articles and discussions on the differences between a project manager and a scrum master. There are of course some key differences and some people would argue that the roles are completely different. However in the working world these  roles will at times, have merged and their has been cross over between the two roles. I believe myself one of the key elements to delivering success is not to work to a rigid structure and adjust according to what works best with the team and people working in the project. –  Just get a scrum on 🙂

Scrum Master:

It has been recommended in Agile Scrum that the scrum master should work for the team and remove all the impediments of the team. The scrum master is like a mentor and coach for the team. Driving them forward and creating the best possible working environment. 

Project Manager:

Although the project manager may also fill the roles as above. The role is more expected to be one that makes decisions on their own and will responsibilities such as project planning, monitoring, budget control and managing the project.

The following information below was written by Steve Hunton on the Scrum alliance website

Traditionally, the project manager is a leader, a decision maker, a planner, someone who manages the project and the team and is the person accountable to the business for accomplishing the project objectives. The ScrumMaster’s role is more that of coach and facilitator, a role that sits between the project and the customer. The ScrumMaster doesn’t manage the team that produces the work; instead, he supports the product owner, coaches the team, and makes sure that Scrum processes are adhered to. The ScrumMaster is responsible for the Scrum process, its correct and continuous implementation, and the maximization of its benefits.

The Video below from 352 Inc – also gives a good overview of the differences between the Scrum Master and Project Manager.