The Guilty Paradigm

In this post we will explore the difference between two different mindsets: 

Guilty vs Responsible. 

The Field Principle

Hello Quarantiners !!!

Today I want to share with you one of my last and fresh thougths. 

The Field Principle 

The Soccer teams has a big advantage over Software Teams: they have a Field. 

In this Field managers cannot walk in during the game play. 

This Field is the space where they can play the game. Inside this constraints, they can be self-organized. That means: they can take a sort amount of decisions by them self. In front of a problem, they are empowered to immediately implement a solution. Actually, they are accountable for. 

Imagine how annoying could be for the players if outside people just walk in, control the ball, give them some indications, tell them "what to do", and a long etcetera...

Let your teams play 

Let your people do their job. They will be thankful. 

In a Scrum Team, the scrum master is accountable for keeping the rules in the game, and in this case, to keep the "Field" clean from intruders. 

But be careful with the metaphor, "putting a foot into the field" does not means specifically "to not put a foot into the developers office". Yes, that's one meaning. But there is more: 

Decisions. 

There is some sort of decisions, that should belong to the team. That's the meaning of "empowering" them. but, coming back to the "field" metaphor, to "invade the field" is also to take decisions that belongs to the team. 

There is no general model, and in everyplace this may vary, so I cannot tell you exactly what sort of decisions belongs to the team. You should decide and design in your space, what's better for you. Anyway, I can share some "field invasion" examples:

• Assigning a Commitment without being accepted
• Deciding about Team structure, without asking the Team 
• Doing estimations without asking the Team 
• Micro management and micro controlling 
• Writing requirements and detailed plans, without communicating a Vision neither nor transparent Strategies. 
• Sitting the developer as far as possible from customers and end users
  

 

As you can see, and maybe understand, is not only about respecting "physical space" but also "decisions space". 

And what about you? 

• What way are you invading and dis-empowering your teams? 
• What kind of "healthy distance" can you stablish to enable your teams to perform? 
• How much are you interfering and cutting  their Flow? 
• Do your teams has everything they need to create value? 
• How does your processes help everybody to see the Field limits and co working rules? 

Have a nice and safe day...

Daniel 

Coaching a Scrum Team

(picture source: www.tuleap.org)

Welcome to my new post. 

Today I want to share with you some perspective about how to use "Onthological Coching" questions to support a Scrum Team. This is a good example about how much has to do the "Coaching" discipline with the "Scrum Master" and/or "Agile Coach" roles. 

Long story short, I will share with you some "model quesions" to each Scrum Event. 

 

Enjoy! 

Keep safe and healthy. 

• Refinement 
• Are we ready for planning? 
• Do we see impediments or dependencies on the way?
  
• Sprint Planning 
• What do you want to achieve in this Sprint? 
  
• What is our Commitment? 
• What's Sprint Goal and/or Purpose?
  
• Daily
  
• What is happening? 
• What is holding us back from performing? 
• What's our progress toward Sprint Goal?
  
• Sprint Review 
• What is the delivered Value? 
• What did End Users won? 
• What represents Delivered Quality?
  
• Retrospective 
• What you want to change?  
• What did you learn from this experience? 
• What's your new discovery? 
• Given "x" problem: What can we do about?
  
• What change looks difficult or impossible? 
  
• What is preventing us to reach more optimized performance? 
  
• What if...? 

Coaching Decision Processes

Hello dear readers, today I will explore with you the topic: "Decisions". 

 

Decision and emotions factor: the Fear

One of the main factors behind our decision process, is Fear. When we choose an option, we are leaving the others behind.

To decide, is to choose an option. And to not choose others. 

Sometimes the Fear is an obstacle for decisions, sometimes is a motivation. 

A critical component...

...of making decisions, guess what: is commitment. 

 

 

Breakdown 

Define Values

After a Decision, comes Action 

"I am what I decide" 

To help someone to make a decision, is not to decide for him. 

"If I were you, I would do this" 

What holds you back from making a decision?

Decisions are personal, because decisions are an act of Freedom, and Freedom comes with Responsibility. 

Winning and loosing

When we make a decision, we always win something, and loose something. One frequent factor in the decision process, is to be aware of "what we could win" and "what we could loose", and accept both. 

We need to be aware, that when we decide, we are choosing to win, and we are choosing to loose. 

Hard decisions 

Sometimes, we need to decide to make a big lost. There is "hard to make decisions" in life. And they are also necesary. 

In the decision game, we need to be good winners, and good losers. 

Shared decisions 

Many times our decisions are individual and personal, but in other situations, decisions comes from agreement with others. Group decision, Team decisions, Couple decisions are some examples of that. 

In this situations, when someone decides a "no", then is "no" for everybody.

Decision Components:

• Emotions
• Fear
  
• Sorry 
• Regret 
  
• Commitment
• Winning and losings  
• Time 
• Definitive
  

The Decision Process

• Identify the need
• is it real? 
• is my desire? or is from others? 
• Search options
  
• What I will do with my necessity? 
• What Options do I have? 
• What Options do exists? 
• If there is only 1 option, then we are not deciding. 
  
• Identify one option
• Do that cover the need? 
• Is that functional? 
• What's my winning in this option? 
  
• What I'm choosing to loose? 
• Validate
  
• What's the risk to decide? 
• What's the risk to not decide? 
• When is the proper time for decision? 
• What resources do I count with? 
• Who can help me? 
• What do I feel in front of the options?  
• How can be this implemented?
  
•  Choose 
• Responsibility
  
• Commitment 
• Document 
• Why we choose this option? 
• Discard
  
•  all the rest options, do not exists anymore. 
• Action 
• We decide to make an Action, not to be successful. 
• No result
• The important of a decision, is not the result. 
  

 

"I'm proud of everything I tried" 

Hellen Keller

Testing inside an Agile Team

 Dear readers, 

...today I want to share with all of you, a beautiful experience I had during the last months. 

I'm participating in a software development project, for free, as volunteer. My role there is not Coach or Scrum Master, is Developer. 

For one side, I was always implementing small solutions and coding, during the last years. But to work in a project, from zero to launch, its been years since I don't do that. 

So for me was really exciting to do that. Honestly speaking, I was not sure if I could make it happens...but at the end, it worked well. Inside my limitations, of course, but it works. 

I will explain, now, my main happy surprises during this project.

Architecture 

For our surprise, our Architecture skills were powerful. I think that has to do with "collective intelligence". And the learning process that walk with you during the entire path. 

"Learning is part of the process"

We can find many different definitions of Architecture. One I love is: Architecture is the set of decisions, that are hard to change later. 

So in that way, Architecture is simple strategy. Is to prepare the territory for future changes. 

"Architecture, is the skill to split and differentiate"

Testing  Driven Development 

We implemented, until now, 351 tests adding all categories. Twas an amazing experience, that makes me believe, that a real developer cannot live without TDD. 

Twas my best professional experience, in a non-professional environment. I've never participated on a so well organized process. 

I've got the opportunity to implement many of my own theories, and conceptions, like the Business Tests.

Development Layers: how to remove excess of engineering

As we moved forward in development, one of the frequent obstacles or impediments we found, was related to complexity. But complexity is not a curst that falls from the sky because we are sinners. 

A big portion of the complexity, is created by us in the code. In the decisions. 

One of the key leranings was: too much quality, and too much engineering sometimes is a waste. Is a problem. 

To keep a "stupid simple" code is important. Some times we wanted to add a new field into a model, and we faced an issue with the "security token" that was blocking us to develop and test. 

After this experience I found out the importance of splitting the development process into different layers:

• Layer 0
  
• Test environments
  
• Models and its relations 
• CRUD scaffolding
  
• Layer 1
  
• User Graphic interface (usability)
  
• Layer 3
  
• Integration with other systems 
• Layer 4
  
• Security
  
• Esthetics
  

Business Tests Driven Development 

I had

The Power of Unbalanced Teams 

We discover, the power of unbalanced Team.

The Power of Commitment and Agility 

The end of the path is on sight. 

WS24 stands for: Walking Skeleton 24. And cause of our commitment, we set up a deadline for 5th november. 

I can't believe that so much commitment and discipline we put into this project. We start with some codelines, a couple of objects, and now we have an entire application that integrates google login, a django backend, with google maps and many other components. 

So thanks for reading, and here you have my "take out" learnings. 

Keep safe at home! and keep coding! 

• TDD and BDD are amazing, and they work well.
  
• Unbalanced teams are powerful. 
• Commitment is key 
• Agile is about Flow, Team Work, Improvement and Commitment 
• Keep it small, simple and ugly (beauty comes later) 
• 
  

How to enjoy your conflicts

Dear apocalypse survivors,

Some colleagues asked me how can we use a "coaching approach" in order to deal with conflicts.

So, now we are talking about that.

First of all, would like to do a "language distinction". And I may say that I don't find these verbs functional in front of human conflicts:

• solve 
  
• resolve
  
• deal
  
• manage 
  
• reduce
  
• remove
  
• avoid
  

Many of them, assumes that a conflict is a "problem to solve", or at least some kind of "disgusting reality" that we want to avoid. And if we can reduce the amount of conflicts to zero, then we will be happy.

Can you imagine a World without Conflicts?

That's why I decided to use the word "enjoy". Because it can break down all negative assumptions about conflicts.

Conflicts are something to avoid? to remove? to solve?

No. Absolutely not.

Conflicts are part of our human nature and interaction. It's a gap.

And many times, we may found in a situation where we should "create a conflict". Because through the conflict, we can change reality.

Conflicts are opportunities

I see conflicts like opportunities for:

• Intelligence
  
• Learning
• Performance
• Improvement
  

The conflict is an opportunity to grow and increase your soft skills and performance.

They are opportunities for Intelligence, because you can discover if you are holding a wrong position by listening to people that thinks different.

And of course, they are opportunities for Learning, for self-discovery, for self-improvement. We can develop many skills, thanks to the conflict.

aja... ok, then...

What can we do?

First we need to understand conflict's nature.

The main point behind a conflict is a "disagreement". Into that disagreement lies the opportunity for new ideas, knowledge and intelligence. As we can discover new ways of thinking, and of course new perspectives and options.

Of course the connection between the two sides of this disagreement is the language. Both verbal and non-verbal.

One of the key secrets to discover something new is to make an effort to understand other persons perspectives, instead of defending your own subjective one.

Moreover: the fact that you (may) be right, doesn't mean the other is wrong.

A maturity metric

A clear metric about people, teams and organizations maturity, is the skill they have to walk through (enjoy) the conflicts.

I don't remember now, where I listen this affirmation:

"High performance teams,

are able to solve conflicts

without assistance..."

Its a great one. That means: a great team, do have conflicts.

We can scale it to the organization:

"Organizations with a mature culture,

have many open spaces for discussion."

A low maturity mindset could consider the conflict as a "competition to win", the opposite, will see the possibility that we can "win by loosing". You can get a benefit, when you help others.

We can fell in the trap to think "what others should do for me" instead of "what I can do for others".

To Discuss or to not discuss, that's the question

In front of a conflict, there is two possible paths: to discuss, or to not.

The path for "no discuss" is the path for a breakup. Is the path to the divorce. Termination.

The discussion is the space where we can find the new solution.

In front of a conflict we normally see two options: fight or flight. Compete or escape.

And if we are not brave enough to compete, then we may choose an avoiding path. To became silent, invisible, or to move away from that place. To resign.... to emigrate.

To be able to open this space in the middle between "fight" and "flight" needs our talent. It can start, with a question.

A Coach can bring those questions to invite people to think about "what is possible?", instead of "how to win", or "how to escape".

And many times, even when we can hold a respectful and friendly conversation, is not enough to walk through the conflict, and not even to find a new overcoming reality.

then...

How to transform a fight into a discussion

Our mission, as Coaches, is to open a discussion space, between the fight and flight space.

In other words:

• assist people to face conflicts they are avoiding
  
• assist people on how to explore it without fighting
  

As Coaches, we can observe "Language". And that could be a great clue to know, if we are in presence of a fight, or a debate.

A discussion, can be converted into a fight, by using some of these "discussion enemies" (linguistic weapons)

Here is a collection of them, with some samples and possible solutions.

• being "too busy" to address the discussion
  
• Solution: focus on the value for each part, to bring priority for the discussion
  
• being demanding
  
• Solution: open negotiation and avoid judgements.
  
• denial
  
• "you cannot talk about this"
  
• exaggerations
  
• "what you did is terrible"
  
• Solution: focus on solution and cooperation instead of blaming.
  
• generalizations
• using words like "always", "never", "everytime"
  
• "you never help me"
  
• "you never listen to me"
  
• Solution: allow the counter part to express his perspective.
  
• guessing
  
• suppose others intentions
  
• "I know why you say that"
  
• "I know why you do that"
  
• Solution: "we are here to find a win-win plan, not the guilty"
  
• reiterative speech
• try to paraphrase, instead repeating
  
• Solution: invite to paraphrase and provide examples.
  
• choose worst place and moment 
• hostilely attack
  
• insults, adjectives, silence
  
• Solution:
  
• moderate.
  
• If the climax is not appropriate, advice that the meeting can be postponed or cancelled.
  
• reproaching
• bringing old problems to the table to get advantage
  
• Solution: focus on the future and possibilities.
  
• threatening
• "if you do this..."
  
• "if you don't do this..."
  
• "If you don't do this, I will do that"
  
• "If you do not do what I ask, when you ask me I will not..."
  
• Solution: moderate.
  
• manipulation
  
• appeal to guilty feelings
  
• Solution: invite to negotiate or sell the idea.
  

The 4 weapons for a fight are:

• reproach
• the blame
• the threat
• disqualification

A fight focus on: manipulation, domination, defeat, victory

A discussion focus on: negotiation, win-win

When there is no space for discussion,

then we must fight.

How to facilitate a discussion?

• avoid to mediate or arbitrate
  
• establish peer to peer communication (no enemies, no hierarchies)
• expose each position
• focus on finding a common understanding about the problem definition 
  
• What is happening?
  
• assist them to validate language and paraphrase
  
• assist them to make offers and petitions
  
• What do you need?
  
• What can you offer?
  
• assist them to build an action plan with shared responsibilities.
  
• help them to declare their commitments
  

Practical example:

• Preparation
  
• Each person prepares his position before meeting
  
• Invite them to "leave weapons behind"
  
• "We are here to explain our perspective, we are here to listen, and we are here to negotiate"
  
• "We are here to find a win-win plan"
• Do you want to find a solution?
  
• (question to find out current commitment)
  
• Exposition
  
• What's your issue?
  
• What's happening?
  
• What do you need from others?
  
• What are you missing?
  
• Paraphrasing
  
• What did you understood, on your own words?
  
• Offers and petitions. Negotiation
  
• What do you need from the other side?
• What can you offer?
  
• Action Plan
  
• What you plan to do for the change?
  
• Commitments
  
• Where do you focus your commitments?
  
• What's your new commitment after this conversation?
  

The purpose of facilitation are:

• build link's health
  
• identify and transparent differences
  
• negotiate mutual benefits
  
• build a balanced action plan
  
• paraphrase and summarize
  
• make commitments

I wish you Happy Conflicting!

Thanks for reading!

Until next time!

Daniel

What does an agile coach do?

Dear coronavirus survivers,

today I bring to you a simple metaphor, that may help you to understand the Agile Coach Role.

(that applies also to Scrum Masters, Coaches, Leaders, whatever-role-is-supporting-people)

Many times I heard these questions:

• what does an agile coach do?

That's a "Mechanic"question

To think that  a role is defined by its daily tasks, is related to the logic "resource-assignment".

In my opinion, a role is more defined by its "mission".

But anyway, come back to the topic: what does an "Agile Coach" do?

There is not only 1 right way to answer this questions. But maybe this metaphor can help you to watch from another pespective.

What is "Coaching"

Its a conversation discipline (knowledge-cognitive).  

We can find its origin is in the ancient Greek. They used a method of making questions to invite the other to find the truth by himself.

Around 1974, Timothy Gallwey developed in "The Inner Game" book a method to help tennis players to achieve great performance, by solving "psychological impediments".

The name "Coaching" (Sir John Whitmore) comes from the sports business. And has to do to empower an athlete, who already has a great performance, to unblock him for achieving a higher performance.

So: Coaching is a "High Performance" business.

Keeping a long story short, I introduce you our "Coach Sample" for today:

Mickey Goldmill

Of course he is a fictional character but, in Internet, many people agree that he is the best one. I will assume that you already watched this classical movie (Rocky), and move forward:

- If he was the best (fictional) Coach, then...

What did Mickey, for Rocky Balboa?

He was a Cheerleader?

He was his assistant?

He was a Secretary?

He was a pizza delivery-boy?

Maybe he could do those "tasks",

but that was not his "role".

That was not his mission.

Why he was not doing exercise with Rocky?

No he didn't.

Because it was not his job.

Then... what's a Coach's mission?

What was Mickey's mission?

He was a Mentor, as experienced in the business.

He transfer decades of experience to Rocky.

He was also the Coach. He assited him on taking strategic decision (training, food, techniques). His job was to be a "second voice" in Rocky's head.

A Coach can help you to think "out of the box", to focus on what is more relevant, what can allow you to be more strategic by saving energy, time and money.

My opinion is that he was using different "language" for different situations.

Coaching is about Learning. By performing weekly experiments, you can collect the learnings and continuously improve your performance.

The Coach is there to help you develop your own best version. 

A Coach is educating a "winner mentality". Coaching is an invite to change, to think differently and to allow you to see the world through an alternative perspective.

In the corner, the Coach acts as a "second voice".

During "hard to think" moments,

the Coach brings a "cold insight"

In moments where Rocky could not think by himself,

sometimes to listen specific commands:

"Use your left!"

"move your feet!"

"go away from there!"

A good Coach works with emotions. But not by considering them as "a problem", but an opportunity. For a Coach mentality, everything is an opportunity.

A Learn and Improve opportunity.

A Coach is not your secretary, or your assitant.

Its role is also not to be "your friend". Also not "your boss".

Every role is defined by its mission, not its tasks.

A Coach mission, is to help you to learn and grow from your experience.

To allow you to walk the distance between "Intentions" and "Results".

So thanks Mickey, for letting us such a beautiful metaphor about what is...

a great Coach.

Thanks for reading,

Happy Change! 

Daniel

Hello coronavirus survivers!

In the last days I'd contact with this article:

https://www.bcg.com/publications/2020/end-management-as-we-know-it.aspx

and decided to make this post.

Management is under extinction

Yes.

If you are a manager, that plays politics... if you repeal talented people... if you are a control freak... if you are not listening any critic from your subordinates... you are in the risk group.

Sorry to write so hard words, but I find a value on being honest with you.

I'm here to help you.

Even if it hurts.

Maybe no one told you the origin of Agile. Twas written in a manifesto.

Do you know what a "manifesto" is?

Yes, a declaration letter. A strike.

People was tired of bad management. And the Agile founders express that exactly today. If you ask them about... take a look on this picture:

This is Martin Fowler, agile manifesto founder, in his video "Explaining Agile".

At minute 12:51 he says "People are not predictable", and dedicate this finger to someone. (maybe a manager?)

 https://www.youtube.com/watch?v=GE6lbPLEAzc

but...

What is "management"?

During the 19th and 20th centuries, we lived in a "production society". The "owners" of lands, machines and factories were the "landlords" in the economy.

They could crash and mistreat any human being, only driving them with the Fear of being Fired.

The "management" developed a culture of "productivity and control". With strong hierarchies, and a "command and control" system. Of course that includes a "reporting culture", which also includes the 1-directional Feedback (top to bottom)

The Gods (bosses) could judge you as worker, and you could not have any chance of complaining.

With the arrive of technology, internet and communications, we switched from the "production society" to the "Knowlege Society".

The Game changed.

Before, the productive machine, was property of the factory owner. Now the productive machine (the brain), belongs to the employee, and has legs to walk out the door.

Now we have a deprecated management social class. Many of them are already extinguish, but the rest (maybe including you) are next.

What's the difference?

In the old structure, the manager social class, were like Land-Lords in feudal system. Each Lord has its territory, and everything inside it should obey and follow his command.

Now we are moving more into an "internal capitalism" were "free exchange" trends to be the new standard. Negotiation and freedom flows inside constraints.

Now you cannot command, you need to negotiate. You need now to learn how to cultivate a relation with your employees. Build Trust, and gain respect.

In the past, scientific managers created a value to the company, providing control, hire and fire power. Keeping people scared of being fired to hold high productivity rates.

Nowadays, ir some manager is a "Fear Creator" he is a problem. No, sorry...

He is THE problem

Because Fear kills mind. And for Brain workers, that's toxic. So yes, good conclusion. Old management behaviour is Toxic.

Its Profit's Enemy...

Traditional managers are not only problem creators, they are expensive.

A big portion of Budget Waste are "Internal Politics Game".

A Politician is someone that will take decisions for his own benefit, and not for the Company, the Customer or the Employees.

That's why today big companies trends to split into small startups, and to flat hierarchies.

But this is not enough...

We are lacking a cultural change.

The good news:

• this can change
• you can change
• we can change together
  

Ok, gotcha. but... What I can do?

Exactly, thanks Yoda.

You must abandon and weak your old competences, and train, develop, cultivate new ones.

For example: to listen.

In the Jurassic World, your work was to speak (maybe to scream?). Now is to listen.

First step: stay open to change, learn and adapt.

Second step: connect with the "Value Creation Layer"

What the fuck is that ! ?

hahaha... nice.

Pic Author: Niels Pfläging

In every organization you have 3 social components.

• Formal (rules, hierarchies, contracts)
  
• Informal (relations, trust)
  
• Value Creation (Productive)
  

If you are a shitty traditional manager (a Dinosaur) you will focus on the formal structure, hierarchies a lot. And you will use the Informal layer for influence people (manipulate)... but basically this is the consequence:

The more you focus on Formal and Informal layers,

the less space left for Creating Value.

And, my friend, everything that is outside the Vaue Creation layer...

Is a Waste.

So, now, my friend. Ask yourself how you are contributing to the Value Creation layer. And maximize it.

Minimize formalities, hierarchies, meetings, politics. They could exists, but please...

... minimize.

You have now in front of you a path of self discovery.

• How old fashioned are you?
• Are you listening to people?
• Are you caring about what they need?
• Are you a "helper", or a "demander"?
• Are you committed to your people?
• You manipulate them like "resources", or you cultivate a relation with them as "people"?
• Do you give, what you want to receive?

I hope this post was as much painful as possible to help you wake up, and I wish you a wonderful travel of self-trasnformation.

Daniel

Toyota Lean principles for Fitness

Welcome back to my blog coronavirus survivers!

Today I share with you a personal experience with my own Fitness project:

How to apply Toyota principles to my Fitness Board

What is this?

This is my TABATA board with 3 sequences.

TABATA is a high intensity train that combine 20 seconds effort and 10 seconds break. Each TABATA sequence has 8 exercises. And this is repeated 8 times.

In total is 1 hour training.

So let's go, let's see how I improve it:

Step 1: observe 

The reason to improve this board, was that it was not so flexible or easy to read.

The first color code identifies the columns. But the problem is when I decide to move an exercise to other column, the result is like this:

Now is not so clear what exercise belongs to the yellow or the orange. So it didn't work out. Its incoherent. And I'm misusing the opportunity to have a functional color code (waste)

• Decision: we need a new color code. 
• Why: to simplify and avoid information noise.

Step 2: classify

I didn't know if its better to classify exercises between pull/push or by body parts.

At the end, and given the info I had, I decided that to split by body part is more relevant. The other distinction didn't represents a big difference.

So we classify to differentiate.

Done. Color code applied to the board. 

Effect: situations becames visible.

Nice, now I can see realities that were hidden. But wait a moment...

In sequence A, there only 1 yellow. Hmm that's bad.

And for "easy reading" the column titles should be the same color...

• Decision: change title colors.
• why: to avoid confusion and noise. (information noise is a waste) 
• Decision: define a "business value": my priority is to train arms. (yellow)
• why: not every activity creates "value", and we don't manage activities, but a "value flow". 

Step 3: sort

This way I detected that I was not putting effort into the priority. I was "just moving". That's not the goal.

"Movement is not progress"

• Decision: Put a red mark on "value creating exercises".
• Why: to make "value creation" more visible.  

Step 4: balance

Yes, that's looks better.

But now I have a lot of blue items on Sequence B.

• Decision: put priority exercise as top as possible.
• Why: I want to do them when I have more energy. 
• Decision: balance colors 
• Why: to balance training through body.

That looks better.

Step 5: optimize

Observation: there very few red marks, maybe we can increase the effort investment in high value exercises.

• Decision: duplicate high value exercises. 
• Why: dedicate more effort to the valuable exercises.

Final results:

• Now we can easly move every exercise to every position without breaking the color code. 
• We can produce more effect with the same effort / time. 
• We balance the full body. 
• Now we know the "value priority" (arms) 
• Priority is visible.  

Step 6: keep improving

As "Kanbaners", our job is to search always the "small and cheap" improvements. 

Process Review

Let's take a look into the Improvement process:

Color Code. We search simplicity and to reduce information.

Make things visual. That you, without reading, can see the situation and take decisions.

There is things we will not work. Discard them, clear the way.

Is important, additionally, to identify and reduce waste.

If you don't measure, you can't see.

A good metric can show your progress, but it needs to be simple and functional. (in this case "kilos", taking a snapshot per week)

My target was to loose 20 kilos, I have already lost 18.

Question: I think Kilos is not a good metric. How you choose your metric?

Nice question!

In my philosophical opinion would answer:

A good metric is:

• Global
• Imperfect 
• Easy to take
• Meaningful 

Should be global, because we want to metric the "entire system performance" and not specific performances of some parts in the system (sub-optimization)

Should be imperfect, to avoid many psichological effects.

Like:

• obsessing with the metric, 
• measuring success with it (is not) and 
• to feed your illusion of control

For example: after some success, by loosing 17 kilos, and given my goal was 20 kilos, I made these strategical decisions:

"given my method worked well, if I do it harder, it will work better"

So I decided: yes! go for it! double the bet, and we will get more progress!

I think you can guess the result: total disaster.

I've lost control of weight, some weeks down, some weeks up...

then I was totally confused. Until I remembered that rule of balance between variables in an stable system. This kind of useless things we learn at school.



If you make an hipocaloric diet, your body enters in panic. Then he "decides" to save energy, and keep reserves to face the hunger challenge.

Anything that can put your body into stress, can affect totally or partially how your body reacts to the situation. So at the end is not about "how much you train", or "how much you eat", that's a mechanicist approach.

Familiar?

We have an organic echosystem of variables, in a perfect balance. And we think we have a machine with pieces.

That's the mechanic mindset.

The Illusion of control is one of the most common mental diseases for Project Managers.

To believe that we can "tell" to a complex reality how to behave.

To believe that we can "manipulate" results "managing" variables.

- "ok, I understand the problem, but... where is the answer?... what can we do?" 

Nice question. And the answer is philosophical: the law of moderation.

A moderate exercise, with a moderate diet, with moderate fasting, with moderate everything... creates a great lifestyle.

Then the body adapts to this great lifestyle, and find its perfect balance.

The body weight loosing, is just a consequence of the good life quality.

It should be also "meaningful". It means, should be "good enough" to valorate if our strategy is functional or not.



Prioritize. There is always a capacity limit. Time is a hard reality we cannot change. A week will always have 7 days.

Then you need to put your time and effort in the bigger winning activities.

Make them visible, and prioritize.

All these change are part of a continuous process: Improve. 

Next steps

And from your side, in what areas of your life you can implement these Kanban / Lean optimization strategies? 

Share your experience with me to learn together.

Thanks for reading, and stay healthy! 

Daniel

Pull vs Push

Hello dear followers! I hope your safe and healthy at home during this pandemia.

Today we will explore a classical topic: pull vs push systems.

But as usual, we will not speak only about systems and methods, but also about cultures.

First of all, what is push and pull systems?

Regarding Wikipedia, this is a good definition:




In a Push system there is an "order" that trigger the production process, pushing into the process start point.

In a Pull system, there is a "request" that trigger the production process, pulling from the end point of the production line.

Let's watch a matematical example:

Situation zero:

• We setup a production line with 3 steps,
• each step feeds the stock of the next one (depending process)
• We decided (PUSH) to setup a production capacity of 10
• On zero time our profit is minus (Minus)1200  

 

• when we put the plant to full production (PUSH) our profit became 1600
  Bingo! We are using full capacity (PUSH)
   

 

• then we optimize the system to follow to the market demand (PULL)
• then we duplicate Profit 
• and we use half of capacity 

But that is at process level. For mechanic mindsets.

We can think also in another dimensions like philosophy, cultural, etc...

Let's try, suppose that instead of "processes" we have "ideas".

You can be pushing those Ideas, or pulling them.

If you "push" you will decide which idea is better regarding your own mindset.

If you "pull", you will discover, which idea is better regarding a real demand.


If we could consider that exists a "push mindset", it could include some of this behaviours:

• To care always and only in to keep capacity full and busy (Busyness)
• To "design teams" without a reason or demand from the market 
• To write requirements to keep teams busy and working 
• To design products that the market didn't asked for. 
• To take decisions in base of structure, more than marketing strategy. 
• "business decisions" are made by a "manager" instead a market expert in contact with the real customer or end user. 
• To adapt "business" strategies, to the internal political strategies or hierarchies.

So the... Scrum is a Push system?

Scrum is also a Pull system. We pull stories from the Backlog. And we will not do "everything".

This is a typical mistake, to consider that Scrum is a Push system. And to optimize Scrum and make it better, a good strategy is to apply Kanban / Lean principles to it.

That means: clean the backlog, focus on the sprint, identify values, eliminate wastes, etc...

You know the rest, sing alone...

I hope you enjoy this piece... have a nice day and stay healthy.

Bye...

  

Scrum vs Kanban?

Hello agilers!

Today I write about what's the difference between Scrum and Kanban?

Which one is better? For what situation?

Whenever you listen "which options do you have to work with your team" the two options comes to the light: Scrum or Kanban.

Ok, let's go!

So, I think one of the main differences between them is that Scrum has Sprints.

But wait... Kanban has also cycles, with different names


In kanban they name "cadences".

But, without prescription...

Ok sorry for that,will try again...

Let me think.

Scrum has a Retrospective meeting.

And, Kanban also. It has 3 of them.


Ok, will save time, as you can see on this picture, it has also some sort of Planning, daily standup, and review.

So at the end everything is about Cycle and Feedback.

hmmm...

let me search a difference....

The Backlog! Scrum has a Backlog!

And Kanban... has...

Also.

Ok, I'm getting bored of this game. let's try in the other direction.

Kanban has a WIP limit!

ahaa!!! there you have!



Scrum also, when you calculate "capacity", measure your "velocity" and plan a "sprint backlog" you are setting up a "WIP limit".

Well sorry ladies and gentlemans, I give up.

There is no difference between Scrum and Kanban, more than "naming" and "prescription".

They are the "same thing" with different setup and names.

Scrum is a prescribed Kanban.

Follow me for more desceptions and myth busting!!!!

Have a nice day....

Daniel

The Best Results cannot be planned

Hello learners!

Thanks for reading my blog. Today I bring to you another learning experience.

After celebrating the 2020 new years eve, I was reviewing my last 8 years, of my life travel. This 8 years iteration is complete and finished, and now I'm ready for a big change.



During this years I move out from Argentina and started to live and work as an agilist in Europe. First year in Barcelona working as Scrum Master, and then life started to play with me: I was moved to Germany.

(yes, "was moved")

On this review, I found an interesting pattern: I had many plans, but the best things from my history, were not planned.



The best things that happened to me were: to meet my music master, who teaches me hundreds of lessons for free, and we share a music world. He pushed me into an stage to play and sing. At the beginning people told me that I had a good voice, but I could not believe it much.

Anyway, watching now to behind, I see that I dedicated myself to the music the last 4 years.

I learnt a lot!

And I could enjoy so many things that could not be possible. Now I have my own Youtube channel, where I share my passion for Music, and I'm also starting in a professional band as a singer.

Everyting sounds nice, but hold on a moment...

When in my plans did I conceived the possibility to became a musician?

I explored a little bit more into my life travel, and found more parts that where "high scores". They were also not planned. And honestly speaking, the "planned" part of my history was not working well. A lot of disappointments, frustration and fights.

Now I think to myself. If the best parts of my history were not planned, can someone do that?

Can best results be planned?

I cannot imagine someone planning like this:

I will go to buy some bread, turn left on the corner at 10:15 and meet a lady in red. I will fall in love with her, and we will get married 2 years after.

Aha!

If the universe of happenings that can be planned are so -small-, and in life, best things cannot be planned...

then...

what if, "best results" in business can also not be planned?

what if, our planning culture is holding us under a limited universe of probabilities and opportunities?

that makes sense for me.

If we plan everything, when comes innovation?

And if, innovation cannot exists, when we will do something disruptive, special?

Exactly: never.

But our reporting culture forces people to do only the targets and activities that can be:

• Planned
• Controlled
• Reported 

You will keep this "controlled" environment?

What are you waiting to free and empower your teams to strike the market with their creativity?

Thanks for reading,

Daniel