Some day, somewhere in the net there was iBlog. It was about everything and nothing. A few persons was reading it, some of them maybe even liked it. But I am not interested in writing about myself anymore. This blog will be about Project Management. Less personal, but in fact it will be my personal tool: to not forget what I have learnt. And what I ll learn in future.
Blog > Komentarze do wpisu

Why Do I Like Processes

Some people think processes are unneeded bueraucratic burden. Some people think processes make engineers' work unpleasant make them sink in papers, instead of doing their job. Some people think processes forbid them to improve anything, change the way they work even if the way is silly, inefficient or error prone.

But a good process description can be a one screen long Wiki page, with a snapshot of a handwritten lifecycle drawn on your whiteboard. And such a process description may be good enough to pass a CMMI audit.

But do you know why I do like processes so much? ...

Because I like to change them. It is very difficult to change something if something does not exist. If you don't have your baseline, you don't know what the f**k is going on and what to change.

Writing a one-pager process description is about two-three hours of talking with engineers and one hour of writing. Then you can change the way your people work in any way you could imagine. Try to do this if you don't have a process.


piątek, 22 lutego 2008, d_l_x

Polecane wpisy

  • Two management styles

    Management styles might be divided, at least for my own purpose, into two basic categories. The first category is black/white style. A black/white manager usual

  • Avoiding large penalty for a late change.

    One way to avoid the large penalty for a change during final production is to make the right design decision in the first place and avoid the need to change lat

  • Performance Rating of a Manager

    Performance rating of a manager cannot be higher than the one we would accord to his organization [he manages]. Andy Groove, High Output Management

Gość: kalamon, *
2008/02/25 22:37:51
Sorry man, but your desire to change the process is absolutely no valid reason to do it. Processes should only be changed by ones affected by them and only when the cost of changing them is smaller than the cost of efficiency loss introduced by bad process. Good development teams are willing and able to tweak their processes as they go without problems and instinctively know what has to be changed, when and why. Most attempts of external consultants, especially the ones "send for rescue" by upper management in order to "harmonize", "streamline" and "standardize" result in nightmarish f***ups. Been there, done that
2008/03/10 23:04:31
Have I written anything which is opposite to your opinion? You are absolutely right. The best people to change the process are those who use the process. You have to change things only to make them better and more efficient and process users know the best what to chage. I was only talking about defining the change, about consiuous changing the process.