How I went to the gym to see something ridiculous – and why it matters to the way your team works.

Read more

A while ago, I got to visit a software company experiencing post-startup phase. The moment in which the business is no longer small enough for everybody to know each other, yet it’s still too small to have the usual inclinations towards corporate mindset. This time is very special, as it defines and clarifies it’s culture for the next period of time.

There are places where you can spot culture at a glance, in an unusual way. Read more

Unwillingly, I rolled down the window. Police officer standing by my vehicle introduced himself in a regulatory way and then moved into the essentials:

– You were driving a bit fast…
– Yes, I know – I was sincere, which wasn’t necessarily the best option.
– Where’s the rush?

I didn’t have a decent and believable answer to that. I needed to figure something out. Read more

If you have enough agile practitioners in your social network, it’s almost certain that you will notice someone posting an article on team development. In majority of cases, it will be based on research done by Bruce Tuckman in the 1960s. Even if you’ve never heard of him, you surely must have heard of the four phases: forming, storming, norming, and performing. Let’s have a quick overview of them. Read more

Sometime last year, when I still allowed myself to mindlessly surf the web every now and then, I stumbled onto really weird photo. While it’s easier to find something like this than something worthwhile, this one was really odd. It showed, for lack of a better description, a bunch of obese people destroying bathroom scales with baseball bats. Read more

Is your business, project, or whatever other endeavor you may pursue (say – life) prepared to handle sudden changes in environment around it? Very special video, recorded in a very special place.

Typical pattern of becoming Agile – make a decision, decide to try Scrum, fail miserably, return to previous way of working (or reinvent the wheel). Here’s the news: you SHOULD fail with Scrum at the beginning. It’s specifically designed to highlight all the deficiencies
of your organization. Whether you do something about them or not – well, that’s your call.

The usual scenario for people returning from courses and trainings is as follows: be super excited, try applying new skills instantly, fail miserably, decay into disappointment. The way around it is easy – though not really intuitive: to go faster, you need to go slower.