Archive for the ‘Learning’ category

Graphical Recording, the Cheap Way

January 25th, 2012

A couple of months ago I did a graphical facilitation training with fellow Thoughtworkers in Sydney. The training itself was excellent and gave us a much better understanding on how to use graphics to facilitate a meeting/workshop. Unfortunately I haven’t been in many situations that would allow me to use those skills lately, but wanting to somehow exercise them, I’ve decided to use graphical recording on my notebook to try to follow the presentations I attended at LESS 2011.

Here are some examples of the results. I’m sure I could get better at it but the fact that I’m able to look a t it 2 months later and still remember what was presented says to me I’m on the right track.

 

 

 

 

 

 

Apart from that, the act of recording and try to create an explanation of what is being said makes me pay much more attention on the content. And it also helps me perceive when Im actually not understanding what is being said (or it is actually too hard to understand..), which happened a couple of times during the conference, as you can see from this example.

Beyond Budgeting at LESS 2011

January 20th, 2012

One of the things that attracted my interest to LESS 2011 was the Beyond Budgeting track. Having read the book a couple of years ago, it is definitely a topic that catches my interest. And it was even better that the first keynote was presented by Bjarte Bogsnes, talking about how beyond budgeting is used at StatOil

As any presentation write-up, this is just my understanding about what was presented, so please don’t hold the presenter on to what I’m writing here :)

Why ?

The first question Bjarte addressed was why the need for something different. And I believe this sentence explains it all

January-December is artificial for business and just works for accounting. But this is not accounting

He followed by explaining that StatOil is always trying to get the best performance they can (who isn’t!), and coupling everything they do to an accounting mechanism (the budget) doesn’t make sense for them. He illustrated it with a comparison between the use of traffic lights and roundabouts. While the first is easier to use and provides more control, the latter actually provides better results because it relies more in the current situation than on statistical analysis.

We need to find more self regulating ways to manage a business, and beyond budgeting is one of them.

Bjarte used Douglas McGregor’s Theories X and Y to explain how we traditional management doesn’t usually trust people and relies on a stable environment to succeed, but in a dynamic environment in which most companies are inserted today, we need to start trusting our employees much more, and that is where beyond budgeting stands.

He had a nice example to show the lack of trust some companies impose, about a friend who is a SAS pilot, and even when he is trusted to fly planes full of people around, if he wants to change his shirt more often than it’s stated in the company’s policy, he needs a written authorization for it.

How does it work ?

According to Bjartes, the problem with budget is that it’s a single tool used for three separate purposes: Setting targets, creating forecats and allocating resources. Since these results are usually different from each other (targets are what we want, forecasts are what we expect to get), we won’t get an optimal result from using it.

In StatOil they have developed an alternative format of planning called Ambition to Action. These are a few principles that are used when cdefining it:

  • Good performance is being better than those we compare ourselves with
    • It could be external companies or even ourselves, which means we are learning.
  • Do the right thing
    • Every new joiner receives a StatOil book (a thin one!) with some of the principles that guide the company, so they can all use their business judgement and make decisions when needed.
  • Resources are made available and allocated on a case by case basis
    • Bjartes compared having an yearly budget to having a bank that opens for only a month throughout the year. How can anyone make timely decisions with that ?
  • Business is forward looking and action oriented
  • Performance measurement is holistic, and composed by 50% results and 50% behaviour

These principles are used to define what to do in the company, in a process that goes like this:

1. Strategic Objectives -> 2. KPI’s -> 3. Action & Forecast -> 4.Individual goals

So the company is going to set strategic objectives which are then converted in KPI’s. These are used to define the things that need to be done (Ambition to action), which reflect on how performance is measured for everyone in the company.

Some interesting thoughts he shared when explaining the process were:

  • The perfect KPI doesn’t exist, since not everything that counts can be counted.
  • StatOil creates around 1100 Ambition to action plans, and these are not a reporting tool, but more a guidance on how you as an employee should manage him/herself. Apart from that, everything is open, so everyone can see everyone’s else goals.
  • Performance measurement is usually based on teams and, as said before, divided between results and behaviour. Assuming that the environment very often changes, how someone behaved in that occasion is as important as the results he/she delivered.

The last point that was made during the presentation is how StatOil is moving from a calendar-driven model to a business-driven one. There are no more annual versions of Ambition to Action being created, and they can be changed at any time. The performance review is still happening annually, but Bjartes mentioned they are currently revisiting it now.

Overall it was a great introduction to Beyond Budgeting and how it is applied at StatOil. If you are interested, there is more information here and here.

Bjartes is speaking in the Thoughtworks Live Australia event. If you have a chance to go, don’t miss it.

Kaizen Lego Game @ Agile 2011

October 2nd, 2011

Everytime me and Danilo presented the Lean Lego Game, the common phrase we heard from the participants was

 We want to make this process better!

so for some time we had thought it creating a similar game focused only in continuous improvement, which would allow attendees to learn about improvement principles and practices while having some fun with Lego bricks : )

 

This idea has turned into reality in the format of the Kaizen Lego Game, which was presented for the first time at Agile 2011 in SaltLake City, earlier this year. Unfortunately Danilo couldn’t make it, but I was lucky enough to have Pat Kua as the substitute, helping me a lot with all the work involved in it.

 

Keeping the same format as the original one, the idea behind this workshop was to create an immersive environment where we could introduce continuous improvement principles and practices while improving a small Lego production line. Amongst the topics we focused during the workshop were:

  •  Kaizen
  • Value Stream Mapping
  • Inventory
  • Waste
  • Standards & Improvement
  • Cycle Time
  • 5 Whys
  • Cumulative Flow Diagram (CFD)

I was quite pleased with the result for the first time we presented it. The attendance was very good and we had great positive feedback (and also suggestions for improvements, which were great!).

Want to run it yourself ?

As with the Lean Lego Game, all the material to run the workshop is available through a Creative Commons Attribution-Non-Commercial license. If you are interested, feel free to run and adapt it, as long as we get given the appropriate credit and that you don’t use it for commercial purposes. We also would appreciate receiving some feedback on how it worked out for you.

We have created a package containing all you need to try it out in your environment, including:

  •  Facilitator’s Guide: instructions on how to run the workshop
  • Print material: instructions for participants and worksheets using during the activity
  • Slides

Just get in touch via email to request it!

Kaizen Lego Game by Francisco Trindade & Danilo Sato is licensed under a Creative Commons Attribution-Non-Commercial 3.0 Unported License.

 

Lean Lego Game at Agile Australia

June 13th, 2011

This week I will be participating for the first time at Agile Australia. Have heard lots of good things about it, so I am quite interested in presenting and also looking around what’s being presented. Besides meeting lots of interesting people, which is a given in conferences : )

We will be presenting the Lean Lego Game, which introduces Lean concepts using a fun and entertaining activity. This game was already presented at Agile US and XP Europe, but it’s the first time we are doing it in Australia.

Since Danilo couldn’t come (Australia is still far away from everything…), this time I will be presenting with Fabio Pereira, who has kindly agreed to help me. Everything is quite exciting since we made some changes to it based on feedback we’ve got, so we’re quite keen to see how it goes!

If you are around, please come join us on Thursday morning, and hopefully you will get something out of it. If you do, don’t forget to let us know your opinions.

And in case you don’t know it already, the game is distributed under the Creative Commons license. In case you want to run it in your company or some other group, we have all the material ready to help you, and are happy to distribute it.

Are You Learning Anything ?

June 13th, 2011

At TWU XX, me, Mark and Jim were usually trying to come up with ways to deliver the content we needed without boring anyone to death.

As typical Gen-Y students, the new TWers from our term had a very short attention span, and would (correctly!) reject any topic that wasn’t of their interest, which made us come up with different formats in order to try to make everything interesting.

In this case, it all started when we had to deliver a presentation on a new concept and a challenge was made:

How fast can you deliver this presentation so we can go back to coding ?

As proud trainers that we were, we took the bait and stated that we could deliver a 1.5 hr session in 10 mins. It doesn’t need to be said that we didn’t do it, but from that experiment we started a new format of sessions, based on very short feedback loops.

The idea was to deliver the sessions in 10 min chunks, asking for feedback and adapting every time, in a process like this:

  1. Ask every student to raise their hand describing how confident they were in the subject we wanted to talk about. They could show any number btw 1 (not confident at all) to 5 (I should be delivering this session, not you!).
  2. Have a timeboxed 10 min presentation on the topic
  3. Have the students voting again and question them about what they weren’t understanding or doubts they still had.
  4. Do it again

We repeated that process until everyone was voting around 3 or 4.
I was quite satisfied with the result. We managed to get a lot of good feedback during the sessions, which is usually hard, and also wouldn’t have to (or couldn’t) prepare to much, since we didn’t know which direction the presentation would take.

In some cases the first 10 minutes were a complete disaster, with everyone saying that they didn’t learn anything, but since we were stopping and discussing it, we were able to change direction (sometimes by changing the presenter :P) and fix it.
In addition to that, we did finish most of the presentations that were usually done in 1.5hrs in less than 30 min, which is always good to hear :)

If you are running an informal (or even formal) session, I would definitely recommend this format. Im sure you will get surprised about what you hear!

ThoughtWorks University XXI

June 13th, 2011

In March and April of this year I finally made to India to be a trainer at ThoughtWorks University. This had been a personal goal since I was a student there more than 3 years ago now, so I’m pretty happy I have achieved it.

After being back for more than a month, I’ve finally decided to stop being lazy and write about it, so there will be a couple of posts here in the near future (hopefully!) about the experience I had over there.

As a short summary though, it was truly amazing! :)

In the format that it was created (thanks Summeet for that), TWU sets a challenge to the trainers, who are asked to deliver an interesting 6 weeks training to students that are already pretty good at what they do. There were no constraints set on what we could try, and we were responsible for deciding what would be done.

For someone with no training background as me, I could not ask for a better learning experience.

If you are interested in the subject, please check also Mark’s posts about it. Im pretty sure Im not going to be able as much as him about it. :P

Porto Alegre Agile Weekend 2009

April 6th, 2009

For the Brazilian crowd (or anyone who wants to be part of it), between the 25th and 26th of April will take place in Porto Alegre (my home town : ) ), the 2009 Agile Weekend, which has my friend Daniel Wildt as part of the organizing team.

This will be hopefully the first of many Agile conferences happening in South Brazil, and will serve to boost even more Agile adoption in the region.

portoalegreagileweekend2009_banner_468x60

Needless to say, I really wanted to go, but London is not close enough to Brazil yet…

T-Shaped People vs Generalists

March 3rd, 2009

I’ve been reading Mary and Tom Poppendieck’s new book on Lean Software Development, and in one of the already released chapters, it mentioned the term T-Shaped people, which I had never heard in this context, and suddenly clarified a concept I have in my head for some time.

Since Scott Ambler published the essay Generalizing Specialists, it has become a trend in software development to talk about how generalists are better than specialists for a team, which (in a misinterpretation of what Scott meant) has leaded to a common anti-pattern, where persons become generalists in a lot of stuff, without having a deeper knowledge in any any area.

This way they know a little about a lot of languages, tools  and methodologies, but when it comes to make a difference, these persons are no assets to any team, since they don’t have any deep knowledge on any subject.

This was already covered by Jay Fields in this post, and what I want to point here is how the T-shaped term makes so much difference.
According to IDEO’s Tim Brown, in the  the article is called “Strategy By Design”, here is how a T-shaped person could be described:

“We look for people who are so inquisitive about the world that they’re willing to try to do what you do. We call them “T-shaped people.” They have a principal skill that describes the vertical leg of the T — they’re mechanical engineers or industrial designers. But they are so empathetic that they can branch out into other skills, such as anthropology, and do them as well. They are able to explore insights from many different perspectives and recognize patterns of behavior that point to a universal human need. That’s what you’re after at this point — patterns that yield ideas.”

And that’s what happens in software development. Once you have a deep knowledge in some language, for example, it is easy to branch out to different ones, since you can recognize the same (technical and behavioral) patterns, which will lead you to soon become competent in that area too.

But this situation does not happen if you always stay at the novice level, without never mastering anything you do.