How IT Projects Really Work by Project Cartoon

I came across this awesome image quite a while ago. Most of times, people describe how projects work in words, and what I can get is just a rough impression on how good or bad these projects are; and often times, their description cannot reflect problems/issues in the projects. This image, however, just uses such a simple example and explains all!

If you haven’t seen it, take a little time to go through. If you are IT worker, you will get it fast:)

Project Cartoon: How IT Projects Really Work

This image is from Project Cartoon.

Maybe you had a laugh when going through them. I did, too. I was surprised (and a bit amused) about how the difference between everyone’s performance, and gaps between expectation and delivery. But it’s possible that most of them can happen in one project.

This image, at least from my perspective, gives us an idea about what different roles’ focuses are, and what issues they might have when facing customers. Well. If we want a project to be perfect in every aspect… Easier said than done, but if we have this idea in mind, and do more communication with customers/clients, keep every role involved in the project on a “similar” page, and know each other’s expectation/limitation, we will say “oh great, my project this time doesn’t have so many issues as in this image!”

3 Comments How IT Projects Really Work by Project Cartoon

    1. yingying

      哈,我解释一下吧。假设现在要做一个项目,项目中不同的角色是怎样理解项目需求的:

      顾客对自己的需求的讲解(其实跟他的真正需求不一样,看倒数第三幅图);
      项目经理对顾客需求的理解(与客户描述有偏差);
      分析师的理解(又与项目经理的理解有偏差);
      程序员对需求的实现(又没有完全按照上面两人的要求来);
      Beta版测试人员的测试结果(进一步偏差);
      销售人员对外宣传这个项目时的说法(销售人员总是把事物描述得很美好);
      项目需求文档的完成情况(啥文档都没有);
      操作人员给客户安装程序的时候(安装不完善或者出错);
      项目结帐时,客户的账单情况(被收了一大笔钱);
      客户的真正需求(说明客户的需求往往跟他的描述不一样);
      在使用了Digg以后,程序的情况(毁了。。。因为可能用户流量一下大增);
      修复计划(修复计划没有准备完善)

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *