0:00

I was talking about agile values earlier.

0:02

What are these famous agile values? These agile values that we hear

0:08

everywhere when researching Scrum, eXtreme Programming or Agility?

0:14

There are 4 values and they allow us to understand the spirit and principle of agility.

0:22

The principles that allows you to

0:24

understand each of the Agile methods which will be discovered later.

0:29

The first value is, individuals and their

0:31

interactions more than processes and tools.

0:34

As you can see, the focus is on the human

0:36

and the interactions that there may be between each human participant in the project.

0:42

It counts a lot more than setting processes and tools.

0:46

It's dehumanised.

0:49

We do it like this, we are trying to put the human at the centre.

0:55

The second value is, operational software,

0:58

more than detailed documentation. So I have an expression I like

1:02

to tell each of my clients, and also to trainees.

1:05

If you need to use an IKEA manual to use software, there's no chance it will work.

1:11

Imagine Facebook. Do you think Facebook

1:15

could deliver an IKEA manual to teach you how to use Facebook?

1:18

Same thing for Twitter? Instagram?

1:20

And any other site or applications?

1:22

No chance that their business will grow. If they had to do that. No.

1:27

You need to set up operational applications and make them intuitive very quickly.

1:32

Rather than wasting time on unnecessary documentation.

1:37

Third value is, collaboration with customers is very

1:42

important rather than the contractual negotiation.

1:46

I'm not saying that a contract to manage relationships is not useful.

1:50

It's very useful to protect yourself. That's very clear. But on the other hand,

1:54

you need to focus first about collaborating with your customers

1:59

rather than only managing the contractual aspect.

2:04

You'll see that you'll be able to produce more efficient software.

2:09

And that the customer will be happier if you

2:12

involve him in everything throughout development.

2:16

So be careful, little parenthesis before I move on to the 4th value,

2:20

this is where sometimes some customers who do not master agility,

2:25

but who want to see it in one purely financial aspect could tell you:

2:29

I'd like you to be agile. Basically for them.

2:31

I'd like you to do the product and the project as cheaply as possible.

2:35

No, that doesn't mean that. Collaboration with clients,

2:38

it's not saying that because the client will collaborate with me,

2:42

I can make the product in such a way more expensive or cheaper.

2:45

That's not the idea. A little parenthesis in what I hear

2:48

always with the customers who tell me I would like it to be more agile.

2:52

Basically, I would like you to make it less expensive. Well, that's not agility.

2:56

Small parenthesis that I close directly.

2:58

We'll talk about it later. The fourth value is

3:02

adaptation to change rather than following a plan.

3:06

I said at the beginning, the idea is to be able to do anything in the face of the unexpected.

3:10

Well, if we're not able to manage something unexpected and especially in the world

3:15

"VULCAIN", to resume it using this well known expression,

3:18

a world where we don't know what will happen tomorrow,

3:22

but we know we'll have to face tomorrow.

3:24

So we have to be able to adapt. Well, you have to adapt.

3:28

As part of the management of a project and the agile method,

3:31

by using agile methods, you will be able to do this in a very effective way.

3:36

So the idea, as I say, is that we fully recognise

3:40

the value of the second part of each sentence.

3:42

More than processes, than tools, more than exhaustive documentation,

3:47

more than negotiating contract, more than a planned follow-up.

3:51

But we prefer the first. The emphasis is on human beings, collaboration,

3:56

exchange and above all software delivery

4:02

that is functional and operational very

4:05

quickly. We'll see this when we talk about Sprints.

4:08

The idea is that at the end of each sprint, we deliver what we call an increment of the software.

4:15

So, excuse me, I'm starting right now to use Scrum's jargon.

4:20

I am Scrum certified, so I have to.

4:22

You're going to learn these terms of Sprint, increments, etc.

4:25

Don't worry. If at first you do not understand everything.

4:28

These terms, as we go, I will define them.

4:31

Don't worry, keep in mind that the idea,

4:34

is that at the end of this training session you will master everything and you