download zip of files only
Sun Aug 25 13:45:48 GMT 2024
From /weblog/software_engineering/team
Servant Leadership - http://www.inc.com[..]t-be-my-style-of-servant-leadership.html , similarly, what a leader should do is helping other to do better, not to be the best of the team - http://blog.vincentx.info[..]/03/onthings-manga-taught-me-leadership/ http://www.infoq.com[..]what-do-you-look-for-in-a-servant-leader Mentorship - http://www.javacodegeeks.com[..]entorship-in-software-craftsmanship.html Keep focus, or lose - http://googlesystem.blogspot.com[..]0/how-steve-jobs-influenced-googles.html The anti-pattern and suggestion about new joiner - http://5whys.com[..]-you-will-face-as-a-software-team-l.html Believe me, the objective was not to make decisions, but to create the right environment so that the right decision would be made. http://tech.groups.yahoo.com/group/leandevelopment/message/1952 A nice set of questions to ask for a leader - http://jchyip.blogspot.com[..]3/questions-on-influence-and-growth.html In short, don't put your shoes on others' foot - http://www.inc.com[..]earned-in-the-army_Printer_Friendly.html 4 types of leadership style, well, I think he model leadership a little too simple - http://softwarecreation.org[..]s-the-best-leader-for-the-software-team/ Your experts are spending all their time mentoring novices. Therefore: Put one expert in charge of all the novices, let the others develop the system. - http://gigix.agilechina.net[..]010/2/25/organizational-pattern-day-care What is the key Characteristics of great team - http://www.infoq.com/news/2011/01/characteristics-agile-org This is very insightful obversation, in many time we look into something work in short term but not really solve the problem, a discussion about why so many people like micromanagement even if they know it is bad - http://www.thoughtclusters.com[..]m/2011/01/programmers-and-micromanaging/ http://www.adoptionofagile.com[..]best-thing-you-can-do-for-your-team.html <- is provide required information, probably more transparent. Don't make me think... but you have no business not allowing me to think if I choose to. - http://jchyip.blogspot.com[..]allow-me-to-think-just-dont-make-me.html How To Lead Clever People, actually I am double about this, let's see - http://business.in.com/printcontent/28632 http://business.in.com/media/images/2011/Sep/img_56852_wise.jpg How to grow the leadership - http://www.jrothman.com[..]og/mpd/2012/11/nurturing-leadership.html 他在公司的名言是「When you give, you get」。他在上海成立科研中心，大方讓上汽參與，他認為各懷鬼貽的氣氛不可能做出成績。合資公司理論上是獨立個體，合資公司員工應把合資公司利益放到最前，而不是自己原屬公司的利益，但很少人做得到。慢慢下來，上汽也逐漸對墨菲產生尊重。 在美國和上海工作過的GM員工，指上海GM的工作氣氛跟美國截然不同，甚至認為上海GM形成一套自己的文化，這套文化建基於信任。墨菲跟員工打成一片，工餘在家中安排活動，中美關係罕有地融洽。 http://www.thehousenews.com/finance/由傲慢製造的優秀企業/ 10. 永遠記得，做出決定前要先綜觀全局。 9. 否定別人跟切換開關一樣容易。但你最好拼死抵抗這種衝動，因為你也曾經做過蠢事。你做過爛決定，然後學習、成長，別人也一樣。 8. 掃地、擦桌、關燈。哪裡有漏洞要補就去補——即便那很瑣碎、沒人會注意。你必須做這些事去造福你的產品、你的公司，以及所有你們團隊共同打造的，令眾人驚艷、神奇的事物。 7. 你無法做所有的事。閉上眼睛，向後仰倒，學會信任。 6. 顯然有某種更為有效的方法能處理你正在做的事。是什麼呢？在每天回家的路上反覆思考吧。 5. 找出總是在依賴你的人，想想要怎麼做才能協助他們，讓他們自力更生。或許你覺得當個壟斷市場的鮭魚供應商很重要，但如果小鎮的所有人都學會捕魚，便能將你解放出來去做別的事。像是學習種小麥，或是如何馴服那些可愛的小狼。 4. 別說任何對當下討論沒有貢獻的話。你的聲音並非悠揚到絕對必須被聽見。 3. 做得出最好的決定比不上處在得以確保做出更多最佳決定的流程。 2. 就像你經常發表意見那樣，多說感謝和鼓勵的話語。 1. 最重要的是：永遠要掃除障礙物。那怕只是玩玩手指、看看窗外的雲，也別讓你那愚蠢、幼稚的自我阻礙團隊前進的腳步。 http://www.inside.com.tw/2013/02/04/a-manager-s-maifesto http://joeduffyblog.com[..]oftware-leadership-6-read-every-checkin/ http://www.engineeringandcareering.co.uk[..]o.uk/2014/10/leading-and-delegating.html https://www.thekua.com[..]op-5-mistakes-for-first-time-tech-leads/ http://www.yegor256.com/2015/01/08/morning-standup-meetings.html How to lead with diplomatic - http://www.crucialskills.com[..]how-to-be-both-assertive-and-diplomatic/ Dr. Nico Rose cites research that finds that happy people tend to be more effective leaders. - http://www.forbes.com[..]-your-money-managing-your-life-part-one/ https://www.infoq.com/news/2017/02/humility-positive-trait https://medium.com[..]ge-manager-vs-great-manager-cf8a2e30907d https://simpleprogrammer.com/coaching-programmers/ Don't pretend - https://medium.com[..]ad-my-five-biggest-mistakes-fd7f4a2f1808 https://medium.com[..]les-of-effective-leadership-d2f9d28a49fb Being Glue - https://noidea.dog/glue 7 ways to delegate better and unleash your team’s full potential - https://www.fastcompany.com[..]er-and-unleash-your-teams-full-potential How to lead a team of senior engineers - https://blog.practicalengineering.management[..]-a-team-of-senior-engineers-8e8d69576d1e 技术管理者如何“好好说人话” - https://www.infoq.cn/article/yYylg1XRI0ZWdqh5AYYH Rather than starting your criticism with a compliment, start by saying that you are going to dig into ways that your employee can improve their performance and that you’re giving this direct feedback because you know that with the right guidance they can improve. - https://www.fastcompany.com[..]ve-criticism-according-to-a-psychologist
(google search)
(amazon search)
Fri Mar 15 00:21:16 GMT 2024
From /weblog/software_engineering/team
Building trust for team - http://cocreatr.typepad.com[..]nity-of-practice-and-trust-building.html One nice article about teamwork: Directing (hi directive + lo supportive, for "enthusiastic beginners") Supporting (hi directive + hi supportive, for "disillusioned learners") Coaching (lo directive + hi supportive, for "reluctant contributors") Delegating (lo directive + lo supportive, for "peak performers") http://www.cmcrossroads.com[..]bbthreads/showflat.php?Cat=&Number=64809 Is it a people problem or process problem - http://blog.nayima.be[..]01/21/people-problem-or-process-problem/ importance of teamwork - http://www.butunclebob.com[..]leS.MichaelFeathers.ProgrammingOnYourOwn 5 Dysfunctions of a Team - http://www.anticlue.net/archives/000279.htm A Leaner Start: Reducing Team Setup Times - http://www.infoq.com/articles/pat-kua-onboarding-new , I think article "letting-go" is really insightful - http://www.thekua.com[..]007/09/24/onboarding-strategy-letting-go A good explanation of what is courage, and the result of didn't have courage. It also mention a bit of how to bulit courage within the team, but not much about it - http://www.xprogramming.com/xpmag/NotXP.htm A potential issue of focus too much on people, rely on few heros - http://jchyip.blogspot.com[..]12/people-over-process-misses-point.html Our agile process requires people to spend the effort to listen and talk to each other, working closely. You have to be a people person to like it. It doesn't suit sociopaths. Accidently hiring a sociopath is going to make XP impossible. Trust me, I know. To me this is XP's fundamental weakness. http://jchyip.blogspot.com[..]12/extreme-programmings-fundamental.html What important is team but not idea - http://www.codinghorror.com[..]g/2010/01/cultivate-teams-not-ideas.html http://www.infoq.com/news/2011/11/enable-high-performance-teams http://www.infoq.com/presentations/Co-Making-Great-Products A Measure of Your Team’s Health: How You Treat Your “Idiot” - http://quickbase.intuit.com[..]r-teams-health-how-you-treat-your-idiot/ http://www.inside.com.tw[..]ur-teams-health-how-you-treat-your-idiot https://www.infoq.com/news/2018/05/culture-safety-ei-teams How to Create a Great Team Culture (and Why It Matters) - https://queue.acm.org/detail.cfm?ref=rss&id=3323993 https://noidea.dog/glue Psychological Safety - https://www.buildsoftwarebetter.org[..]tally-healthy-environment-for-developers https://hbr.org[..]chological-safety-heres-how-to-create-it ‘As long as everyone got a chance to talk, the team did well. But if only one person or a small group spoke all the time, the collective intelligence declined.’ - https://www.nytimes.com[..]its-quest-to-build-the-perfect-team.html The secret ingredient to successful team building is not what you think - https://www.fastcompany.com[..]sful-team-building-is-not-what-you-think
(google search)
(amazon search)
Sun Feb 25 12:35:18 GMT 2024
From /weblog/software_engineering/team
Stop Demotivating Me! - http://www.cio.com/article/print/123406 The key takeaways are a number of tools that you can use to try to help yourself or help others follow through on their goals. One key takeaway is that whenever you want to help somebody follow through on a goal, one thing you should do is actually prompt them to think about exactly when and where and how they will accomplish that goal. - http://knowledge.wharton.upenn.edu[..]at-make-a-big-impact-on-achieving-goals/ Quiet Quitting & Strategy, The Humanity Imperative - https://rogermartin.medium.com[..]com/quiet-quitting-strategy-1fe6892c975b Employees said they’d work harder if recognized. These are the types of recognition they want - https://www.fastcompany.com[..]loyees-work-harder-recognition-they-want
(google search)
(amazon search)
Thu Nov 03 23:55:18 GMT 2022
From /weblog/software_engineering/team
Cool diagram showing what slow us down - http://www.targetprocess.com[..]m/blog/2012/01/faster-faster-faster.html Usually, not a good idea to grow a team too big too soon - http://martinfowler.com/bliki/PrematureRampUp.html Taken from Interview of Charles Simonyi ( http://www.shamit.org/charles_simonyi.htm ) , both the interview and the discussion are nice to read: http://discuss.joelonsoftware.com/default.asp?joel.3.341396 , However, I will think if team work effective, 1+1 > 2 What we should really care about is effectiveness and not efficiency. and effectiveness is often inefficient - http://www.markhneedham.com[..]our-obsession-with-efficiency-dan-north/ Handling emergencies or crisis situations Handling work stress Solving problems creatively Dealing with uncertain and unpredictable work situations Learning work tasks, technologies, and procedures Demonstrating interpersonal adaptability Demonstrating cultural adaptability Demonstrating physical-oriented adaptability - http://jchyip.blogspot.com[..]2010/12/8-behavioural-dimensions-of.html http://www.funretrospectives.com/anchors-and-engine/ <- a simple way to check what make team move faster, and things that slow team down. http://www.targetprocess.com[..]icles/speed-in-software-development.html The emergency team, in our understanding, was supposed to work as a point of entry for new developers, so they could know the codebase better. However, we didn’t get into account that newcomers needed to check on some things with the “old” developers. That hindered the work, and we eventually switched back to ~1 month rotation principle. - http://www.targetprocess.com[..]/how-we-handle-bug-fixes-and-rework.html Your team’s strength is not a function of the talent of individual members. It’s a function of their collaboration, tenacity, and mutual respect. - https://medium.freecodecamp.org[..]-best-decision-we-ever-made-4c0a99728fde https://ronjeffries.com/articles/019-01ff/kate-red-threads/ http://testobsessed.com/2020/02/momentum-urgency How To Update Your Status During Standup Like a Senior Engineer - https://betterprogramming.pub[..]d-up-like-a-senior-engineer-f05f3c7f91e4
(google search)
(amazon search)
Tue Nov 12 12:09:43 GMT 2019
From /weblog/software_engineering/team
Recently I help the company offshore some work to CN developers, many difficulty I've encounter, most difficult one is it is hard to share the vision and big picture to CN developers. This article mention a few good notes http://martinfowler.com/articles/agileOffshore.html , the one I think I am lacking is having short meeting with them often. I will see if we can have video conferencing so that we are easier to meet. The other tips here - http://www.theserverside.com[..]_id=45367&asrc=EM_NLN_1439070&uid=703565 but I think the tips list is too long and probably only apply to large enterprise Tips of communication with offshore team - http://www.acceptic.com[..]on-in-software-development-projects.html http://martinfowler.com/articles/remote-or-co-located.html https://www.infoq.com/articles/top5-problems-distributed https://www.infoq.com/articles/be-agile-distributed-teams http://www.infoq.com/cn/articles/be-agile-distributed-teams https://angel.co[..]ur-remote-team-and-then-getting-it-right
(google search)
(amazon search)
Sat Feb 24 16:23:55 GMT 2018
From /weblog/software_engineering/team
No problem is a big problem, So we want to actually encourage conflict in the sense of encouraging openness about disagreement, which in turn suggests that it is essential that we are prepared to resolve conflict - http://jchyip.blogspot.com[..]0/conflict-will-and-should-occur-be.html Should DEV work in prod? - http://swreflections.blogspot.hk[..]developers-working-in-production-of.html
(google search)
(amazon search)
Fri Jan 06 14:08:55 GMT 2017
From /weblog/software_engineering/team
Discussion toolkit - http://www.stickyminds.com[..]YCOLUMN&ObjectId=12875&objecttype=ARTCOL Other tips - http://www.infoq.com/articles/satir-communication-model-teams Appreciation inquiry, a communication tool helping adopting new thing - http://www.threeriversinstitute.org/AppreciatingYourWayToXP.htm A lot of engineer will silence when under stress, how do you communicate with them that time? Here are some suggestions - http://now.eloqua.com[..]048&elq=1C1DC5420DC8451CB08AEBA44D4F6BC7 There are five dangerous faults, which may effect to a software engineer: http://www.petrikainulainen.net[..]/the-five-faults-of-a-software-engineer/ Benefit of whiteboard over software, communication! - http://www.iamhukai.com/?p=422 How to communicate with difference type of learners Active versus reflective learners: "Active learners tend to retain and understand information best by doing something active with it--discussing or applying it or explaining it to others. Reflective learners prefer to think about it quietly first." Sensing versus intuitive learners: "Sensors often like solving problems by well-established methods and dislike complications and surprises; intuitors like innovation and dislike repetition." Visual versus verbal learners: "Visual learners remember best what they see--pictures, diagrams, flow charts, time lines, films, and demonstrations. Verbal learners get more out of words--written and spoken explanations. Everyone learns more when information is presented both visually and verbally." Sequential versus global learners: "Sequential learners tend to gain understanding in linear steps, with each step following logically from the previous one. Global learners tend to learn in large jumps, absorbing material almost randomly without seeing connections, and then suddenly 'getting it.'" http://pagilista.blogspot.com[..]/03/rich-communication-in-real-life.html How to handle tough discussion - http://www.markhneedham.com[..]iscussing-the-undiscussable-book-review/ Good message structure underlies all forms of effective workplace communication - http://jchyip.blogspot.com[..]ood-message-structure-underlies-all.html A methodology to test the feeling of the team - http://www.codinghorror.com[..]2/12/web-discussions-flat-by-design.html It is the most important skill for programmer - http://chodounsky.net[..]/the-most-important-skill-of-programmer/ and also there are pointer of how to improve your communication skill Slack is good? - https://engineering.policygenius.com[..]per-day-on-slack-29f8b08c0d82#.l27wrcft0
(google search)
(amazon search)
Mon Mar 17 17:25:31 GMT 2008
From /weblog/software_engineering/team
1. Hiring is the most important thing you do at work and always hire people smarter than you 2. A manager’s success is all about making his/her reports successful in what they do 3. You cannot move up in the company unless you train your replacement 4. It is all about “relationships” and not “products” 5. Only viewpoint that matters is that of the customer 6. There is a big difference between products that customers will “buy” vs. products customers “like” 7. Be “market driven” and not be “marketing driven”. There is a big difference 8. Have technical and business arguments with colleagues as long as none of it turns personal 9. Have meetings before the meeting 10. Trying and failing is a lot better than failing to try 11. Execution is the key to being successful http://gopalshenoy.wordpress.com[..]arnt-at-solidworks-in-the-last-11-years/
(google search)
(amazon search)
Sat Nov 17 02:03:59 GMT 2007
From /weblog/software_engineering/team
Have the idea of starting minor interest group / user group of various technology inside a company. Hope someday it happened and these information help http://egjug.org[..]ow-to-make-a-successful-java-user-group/ Fishbowl (conversation), setup a small group from large group for team discussion - http://en.wikipedia.org/wiki/Fishbowl_%28conversation%29 http://jchyip.blogspot.com/2007/11/fishbowl-standup.html
(google search)
(amazon search)
Sat Mar 03 04:43:34 GMT 2007
From /weblog/software_engineering/team
Various tools and approach to Preserving Knowledge, I think the best is to build custom webpage like what I does :-) http://discuss.joelonsoftware.com[..]iscussGroup=3&cReplies=#discussBody12480
(google search)
(amazon search)
|
