תוכניות ניהול הידע בתע״א פעילויות עיקריות

Knowledge is something that helps us to perform, but only as long it is in someone's head. We want the knowledge to be accessible. It can be stored as text, video, sound or any other form, but mostly text today. Instead of documents - contents (blogs, forums, social networks...). 6 activities: 1. Reuse Every business wants to reuse, but it is a very difficult process. The reason ego and need to invent. if you want a developer to create a reusable component, it has to be one of the goals of the project. 2.communities of practice Great system to share knowledge. For success: internal engine and external engine. Internal is at least one person who is really pacionate and external is a sponsor (manager). 3. Portals and document management. Documents not accessible, no version control, no Internet based technology. 4. Investigations (תחקירים) It is better when happens as part of the operations and not per project or action. Knowledge management works best when it is transparent to the users. If I create an app that integrates some knowledge - all users will benefit from that knowledge. Aar - after action review. 5. knowledge continuity Two types: People who leave, 6. and continuos knowledge. If someone don't want to share his knowledge - no big deal! Avi Kedem.

The presentations day

 

Here is a link to our presentation: http://bit.ly/KNgQ0O

 

To be continued…

wiki.co.il– bad, bad wiki

 

I never thought that I would hate so much to work with wiki. I think that wiki.co.il (and no, typing wiki.co.il will not take you to the website, only www.wiki.co.il will! ) is one of the most confusing and not user friendly websites I’ve used in a while.

I will not start describing all my issues with it, but I would really appreciate if someone could help me understand how it works. So here is where I’m stuck.

I’ve created a user in the website, and I’ve created a page (kmwork.wiki.co.il), and I’ve even managed to invite my team members to make changes to this website. So far so good (although it was not simple at all), but here is a puzzle.

I go to the main www.wiki.co.il page, and try to login with my account (which I’m using for a week now), and this is what I get:

So, maybe I’m wrong, maybe I’ve been dreaming all this week and I don’t have an account?

But no, here is kmwork.wiki.co.il

Ok, so this is a mystery, but it is not over yet.

I remember wiki making me to create a general wiki account that should let me login to the main page with vvvlad username. So let’s try using it. Yep, it worked,

and now I’m logged in with vvvlad to the main page on wiki.co.il and this is probably the all system account I should use, right? But NO!!!

When I try to use it on kmwork.wiki.co.il this is what I get:

Excuse my French, but WTF???!!!

Does this means that each web gets separate account? WHY, oh WHY?

Ok, so last mystery for today, here is my page URL : kmwork.wiki.co.il right? You know it is there, and I know it is there, but does wiki.co.il knows?

Nope! So, maybe I’m stupid, and I’m looking for a wrong value, maybe I should be looking for one of the pages and not the main sub domain, right?

Our wiki has this page http://kmwork.wiki.co.il/index.php/GKMF, so it should be found….I was so much hopeful it would, but…

 

Where should we go from here? Not to wiki.co.il, that’s for sure.

Vlad out.

Lecture 9 - million monkeys

Crowds are very powerful. When many people organize and decide to do something good – very good things happen. When mindless crowds follow a smart leader, very bed things happen.

In this lecture we talked about wisdom of crowds.

The most appealing part for me is actually wisdom of small, professional teams.

In software development, and I’m a software developer right now, there are many methodologies, but the one that I can really relate to is Scrum.

Scrum is an agile methodology, which basically means that instead of rigid rules and requirements – the planning and development is done in small chunks (sprints).

But this is not why I mention it.

One of the nice things about Scrum is that it tries to be fun. And makes some of the most difficult decisions in project management to be fun.

In classic project management, the project manager asks the developers for time estimations and decides how long each task should take. Basically, PM is a single person who makes those decisions. Not FUN!

In Scrum, there is a game. It is called the Scrum Poker! The game is very simple:

Every developer has a set of cards with numbers, and each number represent a number of days. Product owner (this is the guy that represents the customer) describes a feature, this feature converted to tasks. This is when the game begins. For each task, each developer chooses a card that represents how many days he thinks this task can take, but he puts the card face down on the table. When everybody is ready, all cards flipped. If everybody had relatively the same numbers, the mean number is taken. If, on the other hand, one number is higher than the others, that developer explains why in his opinion the task may take longer. When done, the same game played for the same task (with the new information).

In my experience, this is an amazing way for planning the development timings. Not only these are more accurate, but it is also a much more involving experience for the developers. The developers are usually much more committed to the timelines that they have decided about.

Here is a video (as usual):