About importance of reading

We badly need to incentivize listening. And online, listening = reading. That old school program from my childhood was right, so deeply fundamentally right. Reading. Reading is Foundamental.

Let’s say you’re interested in World War II. Who would you rather have a discussion with about that? The guy who just skimmed the Wikipedia Article, or the gal who read the entirety of The Rise and Fall of the Third Reich?

If you’ve posted five times in the last 10 years, but you’ve read every single thing your community has ever written, I can guarantee that you, Mr. or Mrs. Lurker, are a far more important part of that community’s culture and social norms than someone who posted 100 times in the last two weeks. Value to a community should be measured every bit by how much you’ve read as much as how much you talked.”

- From “Because Reading is Foundamental” at CodingHorror Blog

We should save Scrum from Scrum

It seems a paradox but it isn’t. I start to think that we should save Scrum from Scrum: from the weight of his popularity that could transform it in something different.

More and more often I see Scrum not well understood and applied in organizations. This concerns different aspects: Scrum roles, collaboration of people, estimation, etc. We have already a name for such situations: it’s the well known “ScrumBut”. The real problem is when the “But” part is much more bigger than the “Scrum” part and what is kept it’s just an iterative framework with people playing the Scrum roles and doing some ceremonies with the fundamental agile principles negatively impacted or no more present. You can see development managers playing the Product Owner role instead of someone with business knowledge, ScrumMaster with a subordinate hierarchical link with the PO, Scrum Masters who assign the tasks to people, estimation done by the team with in reality a Gantt Chart already done to tell how things should go… I’m sure you have already seen such situations and many others.

I think it’s time for reflection to understand where “Scrum” is no more “Scrum” and when it’s not bringing anymore the benefits it was developed for and why we have such common situations. Read more of this post

One thought before sleep… why is management changing so slowly ?

Midnight is passed… I’m reading some pages of the book “How to Change the World” of Jurgen Appelo… and I’ve found just in some lines the sum up of my feelings…  I share it with you, to be your thought for today, your thought for tonight:

W.  Edwards  Deming  wrote  decades  ago  that  bonuses  are  bad  for  business
[Deming  1986].  But  most  managers  around  the  world  are  still  using  them.
Peter F. Drucker    said    ages    ago    that knowledge    workers    cannot    be
subordinates of managers [Drucker 1974], but managers still act as if they are
other   people’s   superiors.   And   research   tells   us   again   and   again   that
performance appraisals don’t work [Bobinski 2010]. But many managers keep
relying on them as their primary evaluation technique.

Why?

Why is management changing so slowly (or not at all)?

Agile misconception – fixed scope and fixed deadline

agileMisconception

Drive: What Motivates Us

The philosopher Ludwig Feuerbach said “man is what he eats”. I would say that a man is also the books he reads and Drive, the book of Daniel H.Pink about motivation is one of those books that can influence you and change the way you think, inspiring you to act. An amazing book.

Drive of Daniel H. Pink

Drive of Daniel H. Pink

Drive teaches us that, when it comes to motivation, there’s a gap between what the science knows and what business does. “The current system of motivation put in place in organizations often doesn’t work and often does harm. If we want to build better organizations, elevate our lives and improve the world a new approach is needed”.

In the introduction Pink explains that human beings behaviour is driven by what is known as the biological drive that comes from within and includes hunger, thirst and sex (Motivation 1.0). Then a second drive that comes from without is to respond to rewards and punishments in our environment (Motivation 2.0). In the middle of the last century however few scientists began to discover that there was a third drive that they called intrinsic motivation, our innate need to direct our own lives, to learn and to create new things, and to do better by ourselves and our world (Motivation 3.0). Read more of this post

Impediments to agile

Just reading an article on things that impede agile… I share two points here (extracted from the original article):

  • Technical Practices

” …you cannot scale agile on crappy code, without collective code ownership and continuous integration – period, no debate!”

  • PMO

“The mother-ship of all agile impediments – actually not my quote!

A bit harsh? Well it depends.

A PMO that is steeped in governance that adds no value then absolutely! Gated controls are great provided they add value – have the requirements been signed by the Business, has the design been signed by the CTO, have you produced your weekly report, have you correctly RAG your Risks and issues. Mother-ship!

But a PMO that has made both the cultural and mindset shift to agile can be a huge enabler.”

People is more important than everything

I’m more and more convinced about this: “people is more important than everything”. For many years in the software industry we tought to have found the good method for successfull software development, always searching for processes, practices, framework… but did these practices and methods provide the expected results? Today the risk is that agile will be another of such methods that didn’t bring the expected results if we don’t understand what “agile” is.

I see a situation in which many people wants to use “agile” and start to do it, but what I see in reality is the fall of agile: “fragile”, “wagile”, “srum-buts”… so the question is:  what “agile” really means?
My passion for agile comes from the idea that the interactions between people are more important than processes, that people are the key factor in the software success. Attendind people’s need and the close collaboration among people can bring back the enjoyment to developing successful software. The agile manifesto defines what agile is, we can find in it the same idea:

indivuals and interactions between process and tools”
“customer collaboration over contract negotiation”
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Agile is not doing it but “being agile”… for that we should start focusing more on people.

Follow

Get every new post delivered to your Inbox.