Sif E. Elharti's Blog

Even small acts can have a great impact…

Archive for June 2010

About the “50% of what you think is wrong by Jeff Sutherland”

leave a comment »

As Jeff said in his post : “50% of what you think is wrong…” and you can prove it to yourself. I’ll try to summarise and give my opinion about knowledge.

Great and deep thinking Jeff, thank you for sharing. The animation is a bit fast which may distract from focussing more on what is said, but it’s nice – very good job -.

To summarise my understanding from the text and the presentation (and maybe it’s 50% wrong!)

1-      50 % of our thinking is wrong

2-      Motivation in most organisations is based on rewarding and punishing – (not so productive ways and even obvious in some cases).

3-      For better performance, people need

  • Autonomy
  • Mastering
  • Purpose

I totally agree with 2 and 3 and they are the main idea behind this post. But, if you don’t mind, I would like to add a note about the first one (Philosophical thinking about knowledge).

Indeed, maybe 50 % of one’s knowledge or common knowledge is wrong and history of science is here to enforce this position. But if we push the analysis a little forward we will have two problems ( or results depending on how you qualify them) with that:

1-      There is no absolute knowledge: 50 % of our thinking is wrong, and since we have no idea which thought is in which context (wrong or right), we can say that no thought is absolutely right.

2-      Maybe the statement that “50% is wrong” is part of the 50% that is wrong: This is the case of recurrent logic which rejects its parent and ends to rejecting itself.

In my opinion, it’s not about wrong or right at absolute level. It’s rather about better or worse at relative and local level. To keep going, we need to choose our path and this is done by each one using his personal reference of better or worse from his point of view. And this last can only be a relative and a local one.

Thus, sharing our thoughts is the best way to check how far they are “right” and learn from each other!

Sif E. Elharti

Even small acts can have a great impact…


Written by selharti

June 22, 2010 at 2:43 am

Traduction du guide Scrum en Arabe (version finale non officielle)

leave a comment »

 (Texte en Français plus bas)

Here is the final but non official version of the Scrum guide translation to Arabic:

Scrum Guide – Arabic.trans (final non official Version)

Thanks to everyone who participated or showed his interest to accomplish this project.


Sif E. Elharti

– If you notice any error or have any comment please let me know. –

===== French ==========

Voici la version finale non officielle du Guide Scrum (en attendant la publication sur

Scrum Guide – Arabic.trans (Version finale non officielle)

Merci à tous ceux qui ont participé ou montré leur intérêt pour  la réalisation de ce projet.


Sif E. Elharti

– Si vous trouvez des erreurs ou avez des commentaires, n’hésitez pas à me contacter svp.-

Written by selharti

June 19, 2010 at 12:25 am

Posted in Agile, Scrum

Agile main best practices – with Ron and Chet –

leave a comment »

I had a great occasion to attend a conference animated by Ron Jeffries and Chet Hendrickson, and organized by Agile Quebec. Ron is one of the authors of the Agile Manifesto and Chet is one of the first signatories of the manifesto. Both of them have a huge experience with software development and agile adoption.  It was not hard for me, and I believe for anyone in audience, to figure the confidence and the large mastering they have about agile practices.

After a short introduction about the main reason for adopting an agile approach versus a classical one, specifically early delivery in incremental way, they focused on the best practices to ensure a successful project.

Key points are (but not limited to) the following:

First of all: Testing. This is not something to be done will the customer is using your product. It’s done during all the project life time. There must be, at least, two kinds of tests: Unit tests at any piece of code level and Acceptance test at product level. Ron and Chat went further and suggested that the Acceptance test must be available before any code is written for given feature.

Second: Refactoring. This is to handle the design challenge. Since the team is working with a short visibility about the upcoming features, they have to adapt their architectural design for any new feature. And once again, this must be done continuously; other ways, the design and the product itself will become an uncontrollable spaghetti.

 Third: Continuous Integration. This is to avoid the overhead of late integration when one discovers that each piece of his product is working fine but only individually and once tied together none is working.

And for sure, all of this can’t be done without a High technical skills and a good Collaboration between team members and the customer.

Enjoy agility, it’s a mindset!

Sif E. Elharti

Even small acts can have a great impact…

Written by selharti

June 3, 2010 at 11:42 pm

%d bloggers like this: