Monday 28 July 2014

Time for Plan B - Why our plans have failed?

Hi,

In 5-July-2014, we have published our final IRQLinux Team Structure according to our plans. Sadly, that plan has failed for these reasons - without knowing the reasons, we shall never ever make any progress and therefore, we shall share that with everyone:


  1. Out of 70 members joined our team and so many willing to join, 10 members ONLY or less are active. Out of those 10 or less, very very few are proactive.
  2. Iraq's situation - example: Electricity, Internet, etc.
  3. So many are interested to help but the lack of experience, skills and time was a very valid reason that prevented them to do anything for the project.
  4. Sadly, Iraqi people (most not all) do not really go and do any kind of search/research. Most (not all) depends on someone else to do that for them. 80% of our time was gone and wasted because of that.
  5. Members refused to stop using Facebook and move to another reliable platform despite the fact that we have asked them so many times to stop using Facebook. This FULL GUIDE was published with each and everything to explain how to communicate. Yet, 1% only from the team are following that.
There are more reasons and before someone starts to blame the founder of IRQLinux, you need to understand the tasks that the founder of IRQLinux has been doing and still do on daily basis:

  • IRQLinux Founder was (and still) doing EVERYTHING by himself except: Artwork, Packaging and Development.
  • Communicate with everyone which drained most if not all the time + energy.
  • All the previous Team Leaders have become inactive for many and different reasons.
  • He had to explain everything and I mean EVERYTHING to almost everyone. No one was willing nor showing any interest to do something him/her self.
  • Because of the above, the founder had zero time to write + assign tasks to people since very few are proactive and the majority don't ask, they sit and wait for someone to give them something to do.
  • Other reasons.

There was a plan to overcome all the above. The plan was:

  1. Instead of one man to lead everything, we came up with the idea of having two people: one is the community manager (the founder of IRQLinux) and another one who is the technical manager (team leader of GNU/Linux Team within ICSF).
  2. Beside #1, the team leader of ICSF QA has been assigned to be the 3rd person who is in charge or IRQLinux. So, total 3 persons so far. One Founder and two acting project managers (each acting is already a team leader).
  3. That was not all. We have found two people to join each acting project manager: one for packaging and one for QA.
Sadly, the above plan failed as well - NO, I'm not going to explain any further why it has failed. Almost the same above reasons - mainly 'communications problem'.

To sum up all the above, basically, everything is messed up and has fallen and all the previous mentioned plans failed.

The only progress that we have made so far that worth mentioning:
  • IRQLinux Artwork Team has been given all the tasks that must be done so everything has been discussed and it is just about time until the work starts according to the plan.
  • We have established new Facebook/Marketing Team for IRQLinux. Tasks have been assigned to that team and everyone knows what he/she has to do.
  • IRQLinux Development (Packaging + QA) are working on IRQLinux Pre-Alpha which supposed to be released very shortly.
  • IRQLinux Blog became more informative and has very useful details.
  • For HR, there is an automated system that requires no intervention. All what need to be done is those who would like to join IRQLinux, they just need to send an email to this address. The automated system will do the rest.
Thanks to all the hard and great work from the people on these 3 teams mentioned above.


For all the above, we have to change our plans. One of these plans is to change the structure of IRQLinux team all together.

Previous one - see this.

We shall publish the new one on a new post.

Thanks a lot for reading :)

No comments:

Post a Comment