agile evening 22_jul_13
DESCRIPTION
Agileの夕べ発表資料 22-JUL-13TRANSCRIPT
What I got in the Agile Conference Tokyo 2013
agile evening 22-Jul-13 Hakozaki
Wednesday, July 24, 2013
Self-Introduction
• Atsushi Sano
• Senior Software Developer
• Not yet Agile
• http://k.hizasi.jp
Wednesday, July 24, 2013
Agile Conference Tokyo
• 2009 http://gihyo.jp/event/2009/agile
• 2010 http://gihyo.jp/event/2010/agile
• 2011 http://pw.tech-arts.co.jp/act2011/
• 2012 http://pw.tech-arts.co.jp/act2012/
• 2013 http://pw.tech-arts.co.jp/act2013/
Wednesday, July 24, 2013
What I got
• Kano model
• TPS
• successful case and failure case
Wednesday, July 24, 2013
Kano model
• Requirement Analyze Method
Wednesday, July 24, 2013
Kano model気に入るDysfunctional questionDysfunctional questionDysfunctional questionDysfunctional questionDysfunctional question
Like Expect Neutral Live With Dislike
Functional
questions
Like Q E E E L
Functional
questions
Expect R I I I BFunctional
questions
Neutral R I I I B
Functional
questions Live With R I I I B
Functional
questions
Dislike R R R R Q
Wednesday, July 24, 2013
Kano model
充足
顧客の満足感物理的充足状況
不充足
不満足
満足
魅力的品質
当り前品質
一元的品質
気に入らない
気に入る
顧客の声（Negative ）
顧客の声（Positive ）
当たり前
仕方ない
Wednesday, July 24, 2013
Kano model
• point of sales
• point of use
• 2011-09-20 ソフトウェアの品質はいつ決まるのか？～「Point of Sales」から「Point of Use」へ http://bit.ly/1b7dTV7
Wednesday, July 24, 2013
Kano model
充足
顧客の満足感物理的充足状況
不充足
不満足
満足
魅力的品質
当り前品質
一元的品質
気に入らない
気に入る
顧客の声（Negative ）
顧客の声（Positive ）
当たり前
仕方ない
point of salespoint of use
Wednesday, July 24, 2013
Kano model
• over commitment and hierarchical organizational structure makes bad quality
Wednesday, July 24, 2013
Kano model
• https://sites.google.com/site/techdmba/kanomodel
• http://msdn.microsoft.com/ja-jp/library/vstudio/hh765981.aspx
Wednesday, July 24, 2013
TPS
Wednesday, July 24, 2013
successful case and failure case
• not necessary to agile for productivity improvement
Wednesday, July 24, 2013
successful case and failure case
• enable to determine specification by oneself
• small project using Ruby on Rails
• confirm to user iteratively
Wednesday, July 24, 2013
successful case and failure case
• lack of agile person
• tight schedule not accepted changes
• just tried
• lack of consideration of maintenance
Wednesday, July 24, 2013
successful case and failure case
• Why Agile
• Education development team and user
• Schedule acceptable changes
• Enough test
• and more ...
Wednesday, July 24, 2013
One more thing
• 2001 Agile Alliance
• ...
• 2008 Lehman Shock
• 2009 Agile Conference Tokyo, Agile Japan
• 2013 ...
Wednesday, July 24, 2013
One more thing
• 「システム・インテグレーション崩壊」のすすめ - ベテランIT営業が教える「正しいITの使い方、営業の使い方」 -
ZDNet Japan 2013-07-20
• http://bit.ly/18uo1Gq
Wednesday, July 24, 2013
Thanks
Wednesday, July 24, 2013