PIXNET Logo登入

David Ko的學習之旅

跳到主文

歡迎光臨 David Ko 在痞客邦的小天地

部落格全站分類:不設分類

  • 相簿
  • 部落格
  • 留言
  • 名片
  • 12月 18 週四 200809:09
  • Microsoft 對QA人員的策略


Microsoft 對QA人員的策略

最近我們和Microsoft有密切的合作, 最主要是想增進我們公司整體軟體開發的能力. 在昨天的會議中, 提到了Microsoft對QA人員的策略, 它讓我想到之前看過的一篇文章. 第一次瞄到時, 還不是很注意. 現在看起來, Microsoft很早就打定這樣的主意.

Test Automation - Takes toll of Microsoft Testers ....
http://shrinik.blogspot.com/2006/08/test-automation-takes-toll-of.html

這篇blog文是在2006年寫的, 作者(他以前也是微軟員工)說他看到Seattle times在 2004 Jan報導, 提到Microsoft lay off了Windows group 中62個testers

http://seattletimes.nwsource.com/html/microsoft/2002155249_mslayoffs20.html

報導中寫著, lay off的原因如下
1. They had automation so testers not required.
2. They need to cut cost - either send jobs to India (low cost option) or aggressively automate...

作者第一時間覺得很可悲, Microsoft居然走到這地步, 居然相信automation可以取代人腦. 不過因為沒有任何官方回應, 或是內部小道消息. 作者也無法確認Microsoft真正的目的為何. 因此作者post這篇文章, 希望內部知情人士能透露一二.

於是就有一些人回應如下:
====================================
  Anonymous said...

    No testers were laid off because they were replaced by automation. Testers, were, however laid off because they were among a group who:
    a) had little or no coding skills
    b) had no potential to learn those skills
    c) weren't very good testers either
    There's a difference, as you know, between button pushers and testers. MS laid off button pushers.

    Anonymous because I've probably said too much.
    3:41 AM, August 11, 2006

這和我昨天聽到的基調大致相同, Microsoft認為tester要能做manual testing, 也要能做 automatic testing, 不能只是會其中一樣. 所以藉由這樣的理由, 一方面把一些舊的tester轉型, 或是lay off掉, 以提升tester整體的能力.

不過他也再三強調人還是最重要的, 這和這篇文章的作者觀點是一致的. 若是人無法思考, 快速應變, 你有再多automation或是tool, 還是無法解決問題的.

--------------------------------------------------------------
Shrini Kulkarni said...

    Thanks anonymous for clarifying about firing of button pushers.

    I am not sure about designations of those - were they SDETs or STEs?
    Going by what you explained it appears that they were laid off for performance reasons.

    I am surprised as why Microsoft did not do a good PR work at clarifying this? Can you point to any official clarification this - article, blog post or some thing like that?

    Some statements/views mentioned in the quoted news post point to a story that seem to justify layoff and link them with automation/cost cutting

    1. spokeswoman Tami Begasse said there is no correlation between the tester layoffs and the company's growing use of workers abroad. She said the group was restructured because it's automating some testing tasks.

    2. In September, the server group said it was cutting 93 positions as part of its move toward automated testing.

    3. One factor is the push by executives to cut costs and adjust to the slower growth in the technology industry.

    4. The 62 work in the core operating system division, headed by Brian Valentine, a senior vice president. In the past, Valentine has called on managers to consider outsourcing work to India as a way to get more done for less cost.

    other thing I would like to know is - will you fire a tester for not having skills for coding?
    Having gone through microsoft interview process (at india) - I know that mediocre tester can not make it to Microsoft Job. No coding skills, no aptitude or potential for learning and no good testing skills - Did MS make those 62 hiring mistakes and attempted to correct by firing them at once?

    I would encourage you to me write to me to discuss more about this...

    Shrini
    11:01 AM, August 11, 2006

====================================
這裡是那篇Seattle times新聞的全文

Microsoft lays off 62 testers
By Brier Dudley

Seattle Times technology reporter


Microsoft is laying off 62 test engineers in the second round of cuts hitting Windows testers in the past five months.

The company has recently sent test work overseas, but a spokeswoman denied that's a factor. She said automation, not globalization, led to the cuts.

Microsoft notified the employees Tuesday and Wednesday last week, and the layoffs took effect Friday. The testers were given the option of staying, with pay, for six weeks while they look for other jobs in the company.

But finding other test jobs in the company may be a challenge.

The 62 work in the core operating system division, headed by Brian Valentine, a senior vice president. In the past, Valentine has called on managers to consider outsourcing work to India as a way to get more done for less cost.

Microsoft is outsourcing some test work to overseas companies such as Wipro, Infosys and Tata Consultancy in India. It's also expanding its overseas research and development facilities with a new campus opening this month in Hyderabad, India.

But spokeswoman Tami Begasse said there is no correlation between the tester layoffs and the company's growing use of workers abroad. She said the group was restructured because it's automating some testing tasks.

"It's not outsourcing related, offshoring related," she said. "It's simply they no longer meet the needs of this position."

The company initially told employees that 64 people were being laid off, but the number was later reduced to 62.

In September, the server group said it was cutting 93 positions as part of its move toward automated testing.

Separately, the company in August announced that it was laying off 76 employees in its Xbox division.

Layoffs used to be a rarity at Microsoft, but the company has become more aggressive about pruning its ranks. One factor is the push by executives to cut costs and adjust to the slower growth in the technology industry.

The Windows division has also embraced automated testing systems, including tools developed by the company's research group to check for software bugs.

Begasse said the move to automate some testing ultimately benefits customers.

"These changes are designed to improve the quality of our products and efficiencies in delivering them to customers, so the realignment demonstrates commitment to improving test-engineer efficiencies within that group," she said.
(繼續閱讀...)
文章標籤

kojenchieh 發表在 痞客邦 留言(3) 人氣(153)

  • 個人分類:測試管理
▲top
  • 12月 17 週三 200809:58
  • 讓QA還會繼續想做QA


讓QA還會繼續想做QA

keeping testers in test
http://blogs.msdn.com/james_whittaker/archive/2008/11/20/keeping-testers-in-test.aspx

這個問題, 我想是大多數公司或是QA manager的夢靨. 一方面找不到好人才, 一方面人才也不易留住. 很容易地, QA不是離職就是換跑道到RD去. 讓我們來看看Microsoft資深的QA manager如何看待這個問題.

在某一場合, 作者被問到一個問題: 你如何保持在QA這條路上, 而不會想轉換到RD去呢?

他說他已經聽過很多次這樣的問題. 許多人把QA視為是RD的一個跳板, 一個先期訓練中心. 他說如果是這樣也不錯, 因為那將會有許多RD知道QA在做什麼, 會比較注重品質, 也會比較容易和QA溝通.

作者也認為並不是因為RD要寫code, 所以QA想過去. 其實QA自己也是需要寫code, 去做automation或是幫助測試更方面. 他認為QA會想離開是因為太多QA manager無法求新, 只考慮shipment和 schedule, 缺乏有求新求變的環境和心態.

而至於願意留下來的QA, 則是因為在team裡面, 他們有機會去做invent, investigate and discover, 使得他們有成就感.

所以如何讓你的QA願意留下來呢? 讓他們有機會去創新. 如果他們都只是focus 在test cases execution和ship schedule, 那大家都會想跑的

以下是一些讀者的回應
===============================
calkelpdiver said:

他提到QA會想換工作的原因
(1)  lack of credibility & respect, lack of pay, lack of support, insane work schedules, finger pointing
(2) getting the opportunity to do new and innovate things in this line of work doesn't come often for the average tester in the average company (Microsoft, and other large shops may be different).
(3) Want to earn more money (RD's pay is higher)

(繼續閱讀...)
文章標籤

kojenchieh 發表在 痞客邦 留言(4) 人氣(308)

  • 個人分類:測試管理
▲top
  • 12月 12 週五 200809:17
  • 在面試QA時, 50 個常問的問題


在面試QA時, 50 個常問的問題

Top 50 Software Testing/SQA FAQs you may be asked in an interview
http://software-testing-zone.blogspot.com/2007/01/top-50-sofware-testingsqa-faqs-you-may.html

在面試QA時, 你會苦於不知道要問什麼問題, 來確認是否有testing的經驗嗎? 這裡作者提供了50個Q & A, 讓你可以徹底了解candidate會些什麼. 雖然答案部分我不是很滿意, 但是還是可以參考一下.

當然這些問題, 不只在interview時可以問, 你也可以以試卷的方式, 來檢驗candidate的程度.

不過這好像只能問問QA lead 或QA manager, 在台灣基本上是不容易適用. 因為台灣軟體業重視品質的程度, 是乎還有待改進. 從公共工程的品質, 應該可略窺一二.

(繼續閱讀...)
文章標籤

kojenchieh 發表在 痞客邦 留言(2) 人氣(1,523)

  • 個人分類:測試管理
▲top
  • 12月 04 週四 200809:41
  • 什麼時候測試可以停止?


什麼時候測試可以停止?


什麼時候已經測夠了, 可以停止了,  這個問題是QA常常會被問到的, 也是其中一個不容易回答的問題. 可是這也是你無法逃避的問題, 因為每次product 要release時, 你就要面對一次, 即使沒有人問你, 你自己也會問自己是不是可以出貨了.


以下是常見的的criteria
1. All the high priority bugs are fixed.
- 這通常是最重要的, 如果重要的bug沒解, 是不敢出貨的
- 不過通常僅限於重要的bug, 至於所有bug都要解掉這件事, 好像不是每個人都願意買單的. 所以這裡會有些落差存在, 需要事先和manager and RD溝通, 否則最後會沒有共識.

2. The rate at which bugs are found is too small.
- 通常這是要看是否bug submission ratio是否下降, 也就是看是否有收斂的跡象. 如果還是在向上發展, 當然是無法結束.
- 即使現在bug已經解完, 並且目前沒有發現新bug, 但是若是目前submission ratio值是很高, 也不可能瞬間忽然降成0. 所以這通常意味著, 其實受測系統裡面還有很多潛藏的bug,  只是目前還沒被抓出來. 所以還是要降低到某個程度才是比較save的狀況.

3. The testing budget is exhausted.
沒錢自然就沒什麼好說的, 當然就停止測試啦!!

4. The project duration is completed.
時間了也是個無可奈何的指標, 這有可能時當初schedule就有問題, 或是測試規劃的有問題. 導致時間不夠使用.

5. The risk in the project is under acceptable limit.
如果risk很低, 是project可以接受的範圍當然是無所謂啦!! Manager說了算!! 呵呵~~~

其實測試是否可以停止,是否足夠, 這要看你是否收及足夠的information. 畢竟測試是個information-gethering的流程, 如果你有足夠的資訊, 讓你可以掌握目前project品質的狀態, 你自然可以很清楚知道目前測試是否已經夠了, 可以結束了.

所以當你不知道是否測試可以結束時, 先問問自己你是否掌握專案的狀況. 如果不知道, 當然是回答不了啦!!

    
Reference
1. When should Testing stop?
http://creativetesters678.blogspot.com/2008/07/when-should-testing-stop.html

2. Chapter 8 Manaing the Testing Project, Lesson Learned in Software Testing.
Lesson 185 "Enough testing" mean "enough informaiton for my clients to make good decisions"
(繼續閱讀...)
文章標籤

kojenchieh 發表在 痞客邦 留言(0) 人氣(101)

  • 個人分類:測試管理
▲top
  • 11月 22 週六 200821:44
  • QA的薪水到底有多少



QA的薪水到底有多少
http://www.itjobswatch.co.uk/jobs/uk/software%20testing.do
(繼續閱讀...)
文章標籤

kojenchieh 發表在 痞客邦 留言(0) 人氣(1,902)

  • 個人分類:測試管理
▲top
  • 10月 21 週二 200813:56
  • Why counting is a bad idea


Why counting is a bad idea
by Shrini Kulkarni
http://shrinik.blogspot.com/2006/12/why-counting-is-bad-idea.html
(繼續閱讀...)
文章標籤

kojenchieh 發表在 痞客邦 留言(0) 人氣(65)

  • 個人分類:測試管理
▲top
  • 10月 13 週一 200822:59
  • 如何評量是否是一個好的QA


如何評量是否是一個好的QA
measuring testers
http://blogs.msdn.com/james_whittaker/archive/2008/07/22/measuring-testers.aspx
(繼續閱讀...)
文章標籤

kojenchieh 發表在 痞客邦 留言(0) 人氣(452)

  • 個人分類:測試管理
▲top
  • 9月 24 週三 200812:58
  • 有關test management 相關的書籍


有關test management 相關的書籍
目前最有名的是這兩本書, Rex Blacky在這方面真的十分有經驗, 他可以寫一堆想都想不到的東西, 你不得不佩服他經驗真的是很豐富. 我想若是有志成為QA manager的人, 這兩本是一定要看的
1. Critical Testing Processes: Plan, Prepare, Perform, Perfect
by Rex Black
http://www.amazon.com/Critical-Testing-Processes-Prepare-Perform/dp/0201748681/ref=pd_sim_b_2
(繼續閱讀...)
文章標籤

kojenchieh 發表在 痞客邦 留言(0) 人氣(230)

  • 個人分類:測試管理
▲top
  • 7月 15 週二 200818:22
  • 什麼是QA 經理要做的事


最近公司在討論QA manager到底要做些什麼?有哪些挑戰是我們目前大家所共同遭遇的?一開始大家討論就很熱烈,但是很快地,答案就收斂下來,因為大家的心中的痛都一樣。
首先,在工作項目方面我們認為QA manager有以下項目:
1. 人員的管理:包含指導(coach)、發展(develop)、生涯規劃(career planning)等等。
(繼續閱讀...)
文章標籤

kojenchieh 發表在 痞客邦 留言(0) 人氣(2,541)

  • 個人分類:測試管理
▲top
«12

文章搜尋

熱門文章

  • (81,341)焦點討論法 (ORID)
  • (19,192)KJ 親和圖法二三事
  • (13,554)設計觀點 (POV, Point of View) 和使用者故事的比較
  • (11,141)Test Case所涵蓋的範圍足夠了嗎?
  • (9,384)測試計劃該寫什麼?
  • (5,917)什麼是Definition of Done (DoD)?
  • (5,540)什麼是精實創業?
  • (3,970)Cyclomatic Complexity
  • (3,099)你所應該知道的BVT
  • (1,637)Feature Driven Development 簡介

最新留言

  • [24/06/28] 訪客 於文章「你吃的藥或營養品,真的有被吸收了嗎?...」留言:
    改善便秘有很健康的方式 平常水分充足之外,纖維素也得要有 ...
  • [24/04/24] 訪客 於文章「(轉載) 為什麼會造成便秘呢?...」留言:
    謝謝分享資訊~ 改善便秘除了平常水分充足之外,纖維素也得要...
  • [23/11/16] 訪客 於文章「過敏的中醫療法...」留言:
    過敏症狀跟免疫力息息相關 除了平常良好的飲食生活習慣及規律...
  • [23/11/06] 訪客 於文章「視力保健...」留言:
    謝謝分享資訊~ 保護眼睛除了減少使用3C產品之外 幫助眼...
  • [23/09/06] 訪客 於文章「QA的迷失: "沒有spec我們無法進行...」留言:
    不就是PM把自己該做好的工作扔給RD QA做嗎? 專案越大牽...
  • [23/04/20] Mina 於文章「如何以探索性作法高效測試...」留言:
    好喔那再麻煩老師到時候提供時間謝謝您...
  • [23/04/18] Mina 於文章「如何以探索性作法高效測試...」留言:
    老師您好~不好意思這堂課除了5/20還會有規畫其他的日期上課...
  • [22/04/21] Max 於文章「如何寫出人人有共識的需求 - 範例描述...」留言:
    第一梯沒跟到,第二梯有計劃哪時開嗎? 謝謝...
  • [22/04/06] 訪客 於文章「谷歌創新寶劍: 設計衝刺體驗營...」留言:
    回饋您這方面資訊,我是從 PTT搜尋引擎的排名,看...
  • [21/08/10] jwang0189 於文章「如何寫出人人有共識的需求 - 範例描述...」留言:
    非常實用的文章,謝謝提供,已點廣告表示支持 https://...

個人資訊

kojenchieh
暱稱:
kojenchieh
分類:
不設分類
好友:
累積中
地區:

動態訂閱

文章分類

  • 正念 (2)
  • DevOps (13)
  • Agile HR (1)
  • 課程介紹 (26)
  • retrospective (15)
  • 敏捷需求探索 (22)
  • 自媒體 (2)
  • TOC (4)
  • Google Sprint (31)
  • 敏捷轉型 (68)
  • LeSS (5)
  • Kanban Experience Report (20)
  • 引導/教練 (29)
  • Spotify (4)
  • Pretotyping (7)
  • Lean Startup (22)
  • Impact Mapping (4)
  • Agile UX (35)
  • Kanban (115)
  • Lean from the Trenches (11)
  • Estimation (7)
  • Scaling & Distributed Agile (9)
  • Standup Meeting (18)
  • Feature Team (10)
  • scrum教學 (5)
  • 過敏 (9)
  • 魚油 (3)
  • Hadoop (1)
  • Scrum入門手冊 (4)
  • Kanban and Scrum (44)
  • 健康 (46)
  • TDD (41)
  • Cloud Computing (1)
  • 我的Scrum新體驗 (4)
  • Innovation (14)
  • Testing Books/Magazine/WebSite (12)
  • Regression Test (6)
  • 測試管理 (19)
  • 讀書心得 (27)
  • User Story (19)
  • Continuous Integration (16)
  • Scrum (126)
  • 勵志 (46)
  • Agile Concept (204)
  • MS Server (3)
  • Scrum and XP的實戰經驗 (65)
  • Performance Testing (38)
  • Agile Testing (41)
  • 投資理財 (25)
  • Exploratory Testing (22)
  • C# (1)
  • 專案管理 (25)
  • 測試自動化 (62)
  • 測試基本知識 (108)
  • 未分類文章 (1)

文章精選

參觀人氣

  • 本日人氣:
  • 累積人氣: