球学员Jacky来到Tim Gallwey面前,“我的反手总有问题,能不能帮我纠正一下?”\nTim: “当然可以,那你的问题是?”\nJacky:”我反手挥拍的时候拍柄老是抬得过高,我找过五个教练了,他们教给我很多的要领,可是我的问题还是没有解决”\nTim: “那你能在我面前试挥几下反拍么?”\nJack: “当然可以”。\n果然如此,Tim暗想: “可是为什么前面的那些教练都不能成功帮助他改正呢?”\nTim: “你的反手不错,如果能做一些小的调整就更好了,这样吧,你先自己观察一下自己的反手?”\nTim把Jacky领到一个大的玻璃墙面前,”你在对这镜子挥几下反拍吧?”\nJacky: “啊,我的天!我打反手的时候,拍柄怎么翘得这么高?”\n渐渐的,Jacky开始照着镜子慢慢降低拍柄。\n开始有感觉了,离开镜子,继续保持这样的感觉。\nJacky: “天呐,就十分钟的时间,这个问题就解决了,我原来单为这个上了二十个小时的专项训练课!”\nTim: “那我教你什么了?”\nJacky: “哦?你好像什么都没有教我,你就是能够让我更近的关注我自己、关注我自己的问题。”\n改编摘自“Inner Game of Tennis – The Classic Guide to the Mental Side of Peak Performance” by Timothy Gallwey\n帮助学员发现问题,并帮助他们用“放大镜”去关注这些问题。\n知道问题,没有意识到问题,意识到问题,自然解决\n\n\n
我们知道头发乱,并没有真正意识到头发乱\nClean up in the morning to look better\nBad hair style\n镜子给我们带来了什么呢?\n
Reflect some facts\ndata, flaw, unacceptable truth\n
Reflect some facts\ndata, flaw, unacceptable truth\n
Reflect some facts\ndata, flaw, unacceptable truth\n
Reflect some facts\ndata, flaw, unacceptable truth\n
Reflect some facts\ndata, flaw, unacceptable truth\n
Reflect some facts\ndata, flaw, unacceptable truth\n
Reflect some facts\ndata, flaw, unacceptable truth\n
Feedback is the way to show reality.\nfeedback of what we have done so far\n
\n
Sprint backlog,sprint status,done & undone,WIP\nreflect of sprint\neasy to operate, green, walk by to see\n没有白板的时候,自己做自己的,不知道其他人在做什么,只管完成手上的工作,没有目标,不是一个团队。使用白班后,知道现在正在发生什么,WIP比较容易控制。翻书过程中也碰到\n
Sprint backlog,sprint status,done & undone,WIP\nreflect of sprint\neasy to operate, green, walk by to see\n没有白板的时候,自己做自己的,不知道其他人在做什么,只管完成手上的工作,没有目标,不是一个团队。使用白班后,知道现在正在发生什么,WIP比较容易控制。翻书过程中也碰到\n
reflect of progress\nchanges in sprint\npressure,easy to draw,direct\n只是知道我们有些晚了,却不知道真是进度是怎样,burndown可以解决;估算过大,进度超前,具体如何?如何调整;翻书\n
reflect of progress\nchanges in sprint\npressure,easy to draw,direct\n只是知道我们有些晚了,却不知道真是进度是怎样,burndown可以解决;估算过大,进度超前,具体如何?如何调整;翻书\n
reflect of code\ndescription, quality,Internal & External\nconfident\nTDD时UT经常运行,Integration Test、Acceptance Test进场运行才能知道系统个功能状况\n
reflect of code\ndescription, quality,Internal & External\nconfident\nTDD时UT经常运行,Integration Test、Acceptance Test进场运行才能知道系统个功能状况\n
reflection of integration, Quality\nfast feedback\n就在我来的前一天,我做了一个功能,改变涉及数据库,DataObject,DTO,其它项目编译不通过,数据库视图编译出错。\n
reflection of integration, Quality\nfast feedback\n就在我来的前一天,我做了一个功能,改变涉及数据库,DataObject,DTO,其它项目编译不通过,数据库视图编译出错。\n
有多少人使用了以上的工具?他们都可见吗?\nwhite board besides team?\nburndown on board?\nRun ut frequently to see the result?\neasy to see ci?\n
\n
make ci visible\ninformation radiator\npush not pull\ncolor,build sheriff\ntraffic light, red yellow green\nsound joke\n\n\n
code quality, coverage, complexity, any other index can measure\nclasses with most changes\n每天做,集成到CI里,各个度量的变化\n选一个要改进的量,top5\ncode coverage的变化\n
online website status,request per minute, CPU, Memory, Network\nsome online website company put it where people usually walk by, with fruit\n每日构建,上线,性能影响。。。\n
leave,milestone,event, customer go live,\nanything you can visualize to reflect company, project, product, team....\nbuild environment\n
most effective way: face to face conversation with white board\npeople need visualized information, v/b pronunciation,\n图形,图像,Simple,如burndown,CIMonitor,chart\n
prefer white board to electronic tools\nto see easily\n
start or being a self-organize team need visibility\nhelp them to improve & evolve\ncode quality\n
to see, not to pursue\n不要太多,比如代码衡量标准,容易分散,不专注\n不要量化标准,变成team追求的目标\n