スクラムのスケールとチームトポロジー / Scaled Scrum and Team Topo...
Sponsored
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
Share
Embed
スクラムのスケールとチームトポロジー / Scaled Scrum and Team Topologies
"ちいとぽ with Scrum - Techmee vol.1"の発表資料
https://timeedev.connpass.com/event/249303/
KASUYA, Daisuke
June 22, 2022
Transcript
63 slides
-
νʔϜτϙϩδʔ ͭͷνʔϜλΠϓ ͭͷΠϯλϥΫγϣϯϞʔυ దͳνʔϜڥք ίϯΣΠͷ๏ଇ
અཧ໘ ೝෛՙ FUDʜ -
νʔϜτϙϩδʔ ͭͷνʔϜλΠϓ ͭͷΠϯλϥΫγϣϯϞʔυ దͳνʔϜڥք ίϯΣΠͷ๏ଇ
અཧ໘ ೝෛՙ FUDʜ ࣮ࡍʹ͜ΕΛͲ͏ݱͷνʔϜʹͯΊΔʁ -
QRC Team Topologies Based on Team Topologies, QRC by Henny
Portman, May 2020 Stream-Aligned Team Enabling Team Platform team Stream-Aligned Team Complicated- Subsystem Team Interaction mode: X-as-a-Service Interaction mode: X-as-a-Service Interaction mode: Facilitating Interaction mode: Collaborating Primary interaction modes for the 4 fundamental team topologies: Collaboration: working closely together with another team X-as-a Service: consuming or providing something with minimal collaboration Facilitating: helping (or being helped by) another team to clear impediments Evolution of team topologies Discover Establish Use Stream-Aligned Team: a team aligned to the main flow of business change, with cross-functional skills mix and the ability to deliver significant increments without waiting on another team. Platform team: a team that works on the underlying platform supporting stream-aligned teams in delivery. The platform simplifies otherwise complex technology and reduces cognitive load for teams that use it. Enabling team: a team that assists other teams in adopting and modifying software as part of a transition or learning period. Complicated-Subsystem Team: a team with a special remit for a subsystem that is too complicated to be dealt with by a normal stream-aligned team or platform team. Optional and only used when really necessary. Conway’s law: “Organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.” Cognitive load: “The total amount of mental effort being used in the working memory.” Restrict team responsibilities to match the maximum team cognitive load. • Intrinsic cognitive load – relates to aspects of the task fundamental to the problem space • Extraneous cognitive load – relates to the environment in which the task is being done • Germane cognitive load – relates to aspects of the task that need special attention for learning or high performance Scaling teams: Organizational groupings should follow Dunbar’s number, beginning with around 5- 8 people, then increasing to around 15 people, then 50, then 150, then 500, and so on. Brook’s law: “Adding new people to a team doesn’t immediately increase its capacity.: Live Rapid feedback Team first approach: start with the team for effective software delivery. There are multiple aspects to consider and nurture: team size, team lifespan, team relationships, and team cognition. Organizational sensing: expect to adapt and evolve your organization structure. ίϯΣΠͷ๏ଇ: “γεςϜΛઃܭ͢Δ৫… ͦͷ ৫ͷίϛϡχέʔγϣϯߏΛίϐʔͨ͠ߏͷઃ ܭΛੜΈग़͢͜ͱʹͳΔ” νʔϜϑΝʔετͷऔΓΈ: ιϑτΣΞσϦόϦʔͷ ޮՌΛߴΊΔͨΊͷνʔϜ͔Β࢝ΊΔɻצҊ͖͢؍ ෳ͋Δ: νʔϜαΠζɺଘଓظؒɺؔੑɺೝෛՙ ৫తηϯγϯά(Organizational Sensing): ৫ߏΛదԠɾൃలͤ͞ Δ͜ͱΛΉ νʔϜͷεέʔϧ: ৫ߏͷάϧʔϐϯάμϯόʔʹै ͏ɻ·ͣ5-8໊͔Β࢝ΊΔɻ࣍ʹ15໊ఔɺͦΕ͔Β50 ໊ɺ150໊ɺ500໊ɺͱ͢Δ ϒϧοΫεͷ๏ଇ: “ਓһΛՃͯ͠ɺνʔϜͷΩϟύγςΟ ͙͢ʹ૿Ճ͢ΔΘ͚Ͱͳ͍” ετϦʔϜΞϥΠϯυνʔϜ: Ϗδ ωεతมߋͷओཁͳʮྲྀΕ(Flow)ʯ ʹ͚ͯฤ͞ΕΔνʔϜɻ৬ೳ ԣஅεΩϧͷ༥߹ମͰ͋ΔͨΊɺ ଞνʔϜͷ࡞ۀΛͭ͜ͱͳ͘ҙ ٛͷ͋ΔΠϯΫϦϝϯτΛσϦό ϦʔͰ͖Δೳྗ͕උΘ͍ͬͯΔ ϓϥοτϑΥʔϜνʔϜ: ετϦʔϜΞϥΠϯυ νʔϜͷσϦόϦʔΛαϙʔτ͢Δج൫ͱͳΔϓ ϥοτϑΥʔϜΛࣄͷྖҬͱ͢ΔνʔϜɻϓϥο τϑΥʔϜෳࡶͳٕज़Λγϯϓϧʹ͢Δ͜ͱͰɺ ͦΕΛར༻͢ΔνʔϜͷೝෛՙΛܰݮ͢Δ ίϯϓϦέΠςΟουɾαϒγεςϜνʔϜ: ෳ ࡶ͗ͯ͢௨ৗͷετϦʔϜΞϥΠϯυνʔϜϓ ϥοτϑΥʔϜνʔϜͰରॲͰ͖ͳ͍αϒγε ςϜʹಛԽͯ͠औΓΉνʔϜɻຊʹඞཁͳ ߹ɺͦΕ͕࠷ળͰ͋Δ߹ʹͷΈฤ͞ΕΔ ΠωΠϒϦϯάνʔϜ: ҠߦֶशظؒͷҰͱ ͯ͠ɺଞͷνʔϜ͕ιϑτΣΞΛ࠾༻͢Δ͜ͱ มߋ͢Δ͜ͱΛΞγετ͢ΔνʔϜ ΠϯλϥΫγϣϯϞʔυ: ΠϯλϥΫγϣϯϞʔυ: ΠϯλϥΫγϣϯϞʔυ: ΠϯλϥΫγϣϯϞʔυ: ຊ൪ ਝͳ ϑΟʔυόοΫ νʔϜτϙϩδʔͷൃల ൃݟ ཱ֬ ར༻ ೝෛՙ: “ϫʔΩϯάϝϞϦʹׂΓͯΒΕΔϝϯλϧ ΤϑΥʔτͷ૯ྔ”ɻνʔϜͷνʔϜͷೝෛՙͷ ্ݶ੍͕ͱͳΔɻ ɾࡏੑ(intrinsic)ೝෛՙ ʔ ྖҬͷຊ࣭ʹؔ࿈͢Δ λεΫʹ·ͭΘΔෛՙ ɾ֎ࡏੑ(extraneous)ೝෛՙ ʔ औΓΉλεΫͷڥ ʹ·ͭΘΔෛՙ ɾదͳ(germane)ೝෛՙ ʔ ֶशϋΠύϑΥʔϚϯ εΛൃش͢ΔͨΊʹऔΓΘ͚ҙྗΛཁ͢ΔλεΫʹ·ͭ ΘΔෛՙ جૅͱͳΔνʔϜτϙϩδʔ(4छྨ)ͷؒͷΠϯ λϥΫγϣϯϞʔυ: ίϥϘϨʔγϣϯ: ଞͷνʔϜͱີʹ࿈ܞ͢ Δ X-as-a Servie: ࠷খݶͷίϥϘϨʔγϣϯͰ ʮԿ͔ʯΛఏڙ/ར༻͢Δ ϑΝγϦςΠςΟϯά: ΛऔΓআͨ͘Ί ʹଞͷνʔϜΛԉॿ͢Δ(ԉॿ͞ΕΔ) νʔϜ τϙϩδʔ Quick Reference Card Japanese translation by @kakutani, Oct 2021 - v1.0.1 IUUQTTDSBQCPYJPJLJJLJ23$@5FBN@5PQPMPHJFTKB -
w νʔϜτϙϩδʔ w 4DSVN!4DBMF w ೃછΈͷਂ͍εΫϥϜͷݱʹ ͍ͪͱΆΛద༻͢ΔҰྫΛߟ͑ ͯΈΔ ͍ͪͱΆͷద༻ QRC
Team Topologies Based on Team Topologies, QRC by Henny Portman, May 2020 Stream-Aligned Team Enabling Team Platform team Stream-Aligned Team Complicated- Subsystem Team Interaction mode: X-as-a-Service Interaction mode: X-as-a-Service Interaction mode: Facilitating Interaction mode: Collaborating Primary interaction modes for the 4 fundamental team topologies: Collaboration: working closely together with another team X-as-a Service: consuming or providing something with minimal collaboration Facilitating: helping (or being helped by) another team to clear impediments Evolution of team topologies Discover Establish Use Stream-Aligned Team: a team aligned to the main flow of business change, with cross-functional skills mix and the ability to deliver significant increments without waiting on another team. Platform team: a team that works on the underlying platform supporting stream-aligned teams in delivery. The platform simplifies otherwise complex technology and reduces cognitive load for teams that use it. Enabling team: a team that assists other teams in adopting and modifying software as part of a transition or learning period. Complicated-Subsystem Team: a team with a special remit for a subsystem that is too complicated to be dealt with by a normal stream-aligned team or platform team. Optional and only used when really necessary. Conway’s law: “Organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.” Cognitive load: “The total amount of mental effort being used in the working memory.” Restrict team responsibilities to match the maximum team cognitive load. • Intrinsic cognitive load – relates to aspects of the task fundamental to the problem space • Extraneous cognitive load – relates to the environment in which the task is being done • Germane cognitive load – relates to aspects of the task that need special attention for learning or high performance Scaling teams: Organizational groupings should follow Dunbar’s number, beginning with around 5- 8 people, then increasing to around 15 people, then 50, then 150, then 500, and so on. Brook’s law: “Adding new people to a team doesn’t immediately increase its capacity.: Live Rapid feedback Team first approach: start with the team for effective software delivery. There are multiple aspects to consider and nurture: team size, team lifespan, team relationships, and team cognition. Organizational sensing: expect to adapt and evolve your organization structure. ίϯΣΠͷ๏ଇ: “γεςϜΛઃܭ͢Δ৫… ͦͷ ৫ͷίϛϡχέʔγϣϯߏΛίϐʔͨ͠ߏͷઃ ܭΛੜΈग़͢͜ͱʹͳΔ” νʔϜϑΝʔετͷऔΓΈ: ιϑτΣΞσϦόϦʔͷ ޮՌΛߴΊΔͨΊͷνʔϜ͔Β࢝ΊΔɻצҊ͖͢؍ ෳ͋Δ: νʔϜαΠζɺଘଓظؒɺؔੑɺೝෛՙ ৫తηϯγϯά(Organizational Sensing): ৫ߏΛదԠɾൃలͤ͞ Δ͜ͱΛΉ νʔϜͷεέʔϧ: ৫ߏͷάϧʔϐϯάμϯόʔʹै ͏ɻ·ͣ5-8໊͔Β࢝ΊΔɻ࣍ʹ15໊ఔɺͦΕ͔Β50 ໊ɺ150໊ɺ500໊ɺͱ͢Δ ϒϧοΫεͷ๏ଇ: “ਓһΛՃͯ͠ɺνʔϜͷΩϟύγςΟ ͙͢ʹ૿Ճ͢ΔΘ͚Ͱͳ͍” ετϦʔϜΞϥΠϯυνʔϜ: Ϗδ ωεతมߋͷओཁͳʮྲྀΕ(Flow)ʯ ʹ͚ͯฤ͞ΕΔνʔϜɻ৬ೳ ԣஅεΩϧͷ༥߹ମͰ͋ΔͨΊɺ ଞνʔϜͷ࡞ۀΛͭ͜ͱͳ͘ҙ ٛͷ͋ΔΠϯΫϦϝϯτΛσϦό ϦʔͰ͖Δೳྗ͕උΘ͍ͬͯΔ ϓϥοτϑΥʔϜνʔϜ: ετϦʔϜΞϥΠϯυ νʔϜͷσϦόϦʔΛαϙʔτ͢Δج൫ͱͳΔϓ ϥοτϑΥʔϜΛࣄͷྖҬͱ͢ΔνʔϜɻϓϥο τϑΥʔϜෳࡶͳٕज़Λγϯϓϧʹ͢Δ͜ͱͰɺ ͦΕΛར༻͢ΔνʔϜͷೝෛՙΛܰݮ͢Δ ίϯϓϦέΠςΟουɾαϒγεςϜνʔϜ: ෳ ࡶ͗ͯ͢௨ৗͷετϦʔϜΞϥΠϯυνʔϜϓ ϥοτϑΥʔϜνʔϜͰରॲͰ͖ͳ͍αϒγε ςϜʹಛԽͯ͠औΓΉνʔϜɻຊʹඞཁͳ ߹ɺͦΕ͕࠷ળͰ͋Δ߹ʹͷΈฤ͞ΕΔ ΠωΠϒϦϯάνʔϜ: ҠߦֶशظؒͷҰͱ ͯ͠ɺଞͷνʔϜ͕ιϑτΣΞΛ࠾༻͢Δ͜ͱ มߋ͢Δ͜ͱΛΞγετ͢ΔνʔϜ ΠϯλϥΫγϣϯϞʔυ: ΠϯλϥΫγϣϯϞʔυ: ΠϯλϥΫγϣϯϞʔυ: ΠϯλϥΫγϣϯϞʔυ: ຊ൪ ਝͳ ϑΟʔυόοΫ νʔϜτϙϩδʔͷൃల ൃݟ ཱ֬ ར༻ ೝෛՙ: “ϫʔΩϯάϝϞϦʹׂΓͯΒΕΔϝϯλϧ ΤϑΥʔτͷ૯ྔ”ɻνʔϜͷνʔϜͷೝෛՙͷ ্ݶ੍͕ͱͳΔɻ ɾࡏੑ(intrinsic)ೝෛՙ ʔ ྖҬͷຊ࣭ʹؔ࿈͢Δ λεΫʹ·ͭΘΔෛՙ ɾ֎ࡏੑ(extraneous)ೝෛՙ ʔ औΓΉλεΫͷڥ ʹ·ͭΘΔෛՙ ɾదͳ(germane)ೝෛՙ ʔ ֶशϋΠύϑΥʔϚϯ εΛൃش͢ΔͨΊʹऔΓΘ͚ҙྗΛཁ͢ΔλεΫʹ·ͭ ΘΔෛՙ جૅͱͳΔνʔϜτϙϩδʔ(4छྨ)ͷؒͷΠϯ λϥΫγϣϯϞʔυ: ίϥϘϨʔγϣϯ: ଞͷνʔϜͱີʹ࿈ܞ͢ Δ X-as-a Servie: ࠷খݶͷίϥϘϨʔγϣϯͰ ʮԿ͔ʯΛఏڙ/ར༻͢Δ ϑΝγϦςΠςΟϯά: ΛऔΓআͨ͘Ί ʹଞͷνʔϜΛԉॿ͢Δ(ԉॿ͞ΕΔ) νʔϜ τϙϩδʔ Quick Reference Card Japanese translation by @kakutani, Oct 2021 - v1.0.1 -
4DSVN!4DBMFͱʁ w εΫϥϜͷڞಉߟҊऀͷਓͰ͋Δ+F ff 4VUIFSMBOEത࢜Λத৺ʹཱ֬ w ෳͷεΫϥϜνʔϜʹΑΔϑϥΫλϧߏ w ࣮༻࠷খݶͷ྅ػߏ w
)PXͱ8IBUͦΕͧΕͷऔΓΈ͕ఆٛ͞Ε͍ͯΔʢεΫϥϜϚελʔαΠΫ ϧͱϓϩμΫτΦʔφʔαΠΫϧʣ w ݸਓతʹϓϩμΫτΦʔφʔͷ׆ಈʹ͍ͭͯͷఆ͕ٛ͋Δͷ͕ؾʹೖ͍ͬͯ ·͢ -
εΫϥϜϚελʔαΠΫϧ w νʔϜϓϩηε w ϝτϦΫεͱಁ໌ੑ w ϓϩμΫτϦϦʔεͱϑΟʔυόοΫαΠΫϧ w ܧଓతվળͱোͷআڈ w
νʔϜԣஅͷௐ w σϦόϦʔ w ΤάθΫςΟϒΞΫγϣϯνʔϜ -
ϓϩμΫτΦʔφʔαΠΫϧ w νʔϜϓϩηε w ϝτϦΫεͱಁ໌ੑ w ϓϩμΫτϦϦʔεͱϑΟʔυόοΫαΠΫϧ w ઓུతϏδϣϯ w
όοΫϩάͷ༏ઌॱҐ͚ w όοΫϩάͷׂͱϦϑΝΠϯϝϯτ w ϦϦʔεϓϥϯχϯά w ΤάθΫςΟϒϝλεΫϥϜ -
εΫϥϜϚελʔαΠΫϧ w νʔϜϓϩηε w ϝτϦΫεͱಁ໌ੑ w ϓϩμΫτϦϦʔεͱϑΟʔυόοΫαΠΫϧ w ܧଓతվળͱোͷআڈ w
νʔϜԣஅͷௐ w σϦόϦʔ w ΤάθΫςΟϒΞΫγϣϯνʔϜ -
νʔϜϓϩηε w εΫϥϜΨΠυͰنఆ͞Ε͍ͯΔεΫϥϜΛߦ͏͜ͱ w εΫϥϜϚελʔαΠΫϧͱϓϩμΫτΦʔφʔαΠΫϧͷ࠷ॳͷަࠩ w νʔϜϓϩηεͷΰʔϧ w ͷఆٛΛຬͨ͢࡞ۀͷϑϩʔΛ࠷େԽ͢Δ w
νʔϜͷύϑΥʔϚϯεΛ࣌ؒͷܦաͱͱʹ্ͤ͞Δ w ࣋ଓՄೳͰɺνʔϜΛΑΓ๛͔ʹ͢Δํ๏ͰӡӦ͢Δ w ސ٬ϑΟʔυόοΫϧʔϓΛՃͤ͞Δ -
4DSVNPG4DSVN 4P4 w ֤εΫϥϜνʔϜΛଓ͢ΔόʔνϟϧͳνʔϜ w ͭͷ4P4dνʔϜ·Ͱ͕࠷దͳ w ֤νʔϜ͔Βͷදऀ͕ू·ΓɺεΫϥϜΠϕϯτΛ࣮ࢪ͍ͯ͘͠ w εέʔϧυσΠϦʔεΫϥϜ
4%4 w εέʔϧυϨτϩεϖΫςΟϒ w 4P4ͷεΫϥϜϚελʔεΫϥϜΦϒεΫϥϜϚελʔͱݺͿ -
&YFDVUJWF"DUJPO5FBN &"5 w εΫϥϜϚελʔαΠΫϧʹ͓͚Δ࠷্Ґͷܾఆػؔ w εΫϥϜΦϒεΫϥϜͰऔΓআ͚ͳ͍োΛऔΓআͨ͘ΊʹඞཁͳݖݶΛͬͨ ϝϯόʔ͕ࢀը͢Δඞཁ͕͋Δ w $&0 $50
ਓࣄͷऀ ܾࡋݖऀͳͲ w ϝϯόʔͷબఆ݅ɺʮϓϩμΫτͷ࠷ऴతͳͯ͢Λ&"5ͰղܾͰ͖Δ͜ͱʯ w &"5ͷू·ΓͰʮ͋ɻͦΕ˓˓͞Μʹฉ͔ͳ͍ͱʯͱͳΕɺ˓˓͞ΜΜΛ &"5ʹೖΕΔ͖ w ΤάθΫςΟϒͳϝϯόʔΛεΫϥϜͷϑϩʔͷதʹΈࠐΉ -
ϓϩμΫτΦʔφʔαΠΫϧ w νʔϜϓϩηε w ϝτϦΫεͱಁ໌ੑ w ϓϩμΫτϦϦʔεͱϑΟʔυόοΫαΠΫϧ w ઓུతϏδϣϯ w
όοΫϩάͷ༏ઌॱҐ͚ w όοΫϩάͷׂͱϦϑΝΠϯϝϯτ w ϦϦʔεϓϥϯχϯά w ΤάθΫςΟϒϝλεΫϥϜ -
νʔϑϓϩμΫτΦʔφʔ $10 w ϓϩμΫτΦʔφʔνʔϜͱҰॹʹ༏ઌॱҐΛௐ͢Δ w $10ɺ͜ͷׂΛ݉͢ΔݸผνʔϜͷϓϩμΫτΦʔφʔͰ͋Δ߹ ͋Εɺ͜ͷׂʹઐͨ͠ݸਓͷ߹͋Δ w ϓϩμΫτશମͷઓུతϏδϣϯΛઃఆ͢Δ w
શνʔϜʹ͞ΕΔɺ༏ઌॱҐ͚͞Εͨ୯ҰͷόοΫϩάΛ࡞͢Δ w ϓϩμΫτΦʔφʔνʔϜ͕ଌఆ͢ΔϝτϦΫεΛܾఆ͢Δ w ސ٬͔ΒͷϓϩμΫτͷϑΟʔυόοΫΛධՁ͠ɺͦΕʹԠͯ͡ڞ௨όοΫϩ άΛௐ͢Δ -
&YFDVUJWF.FUB4DSVN &.4 w ΞδϟΠϧ৫શମʹରͯ͠ϓϩμΫτΦʔφʔͷׂΛՌͨͨ͢Ίʹɺ$10 ɺ&.4ΠϕϯτͰΤάθΫςΟϒओཁͳεςʔΫϗϧμʔͱձ߹͢Δɻ w ϓϩμΫτΦʔφʔαΠΫϧͷҎԼͷίϯϙʔωϯτͷཁٻΛຬͨͨ͢Ίʹ׆ ಈ͢Δ w ઓུతϏδϣϯ
w όοΫϩάͷ༏ઌॱҐ͚ w όοΫϩάͷׂͱϦϑΝΠϯϝϯτ w ϦϦʔεϓϥϯχϯά -
QRC Team Topologies Based on Team Topologies, QRC by Henny
Portman, May 2020 Stream-Aligned Team Enabling Team Platform team Stream-Aligned Team Complicated- Subsystem Team Interaction mode: X-as-a-Service Interaction mode: X-as-a-Service Interaction mode: Facilitating Interaction mode: Collaborating Primary interaction modes for the 4 fundamental team topologies: Collaboration: working closely together with another team X-as-a Service: consuming or providing something with minimal collaboration Facilitating: helping (or being helped by) another team to clear impediments Evolution of team topologies Discover Establish Use Stream-Aligned Team: a team aligned to the main flow of business change, with cross-functional skills mix and the ability to deliver significant increments without waiting on another team. Platform team: a team that works on the underlying platform supporting stream-aligned teams in delivery. The platform simplifies otherwise complex technology and reduces cognitive load for teams that use it. Enabling team: a team that assists other teams in adopting and modifying software as part of a transition or learning period. Complicated-Subsystem Team: a team with a special remit for a subsystem that is too complicated to be dealt with by a normal stream-aligned team or platform team. Optional and only used when really necessary. Conway’s law: “Organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.” Cognitive load: “The total amount of mental effort being used in the working memory.” Restrict team responsibilities to match the maximum team cognitive load. • Intrinsic cognitive load – relates to aspects of the task fundamental to the problem space • Extraneous cognitive load – relates to the environment in which the task is being done • Germane cognitive load – relates to aspects of the task that need special attention for learning or high performance Scaling teams: Organizational groupings should follow Dunbar’s number, beginning with around 5- 8 people, then increasing to around 15 people, then 50, then 150, then 500, and so on. Brook’s law: “Adding new people to a team doesn’t immediately increase its capacity.: Live Rapid feedback Team first approach: start with the team for effective software delivery. There are multiple aspects to consider and nurture: team size, team lifespan, team relationships, and team cognition. Organizational sensing: expect to adapt and evolve your organization structure. ίϯΣΠͷ๏ଇ: “γεςϜΛઃܭ͢Δ৫… ͦͷ ৫ͷίϛϡχέʔγϣϯߏΛίϐʔͨ͠ߏͷઃ ܭΛੜΈग़͢͜ͱʹͳΔ” νʔϜϑΝʔετͷऔΓΈ: ιϑτΣΞσϦόϦʔͷ ޮՌΛߴΊΔͨΊͷνʔϜ͔Β࢝ΊΔɻצҊ͖͢؍ ෳ͋Δ: νʔϜαΠζɺଘଓظؒɺؔੑɺೝෛՙ ৫తηϯγϯά(Organizational Sensing): ৫ߏΛదԠɾൃలͤ͞ Δ͜ͱΛΉ νʔϜͷεέʔϧ: ৫ߏͷάϧʔϐϯάμϯόʔʹै ͏ɻ·ͣ5-8໊͔Β࢝ΊΔɻ࣍ʹ15໊ఔɺͦΕ͔Β50 ໊ɺ150໊ɺ500໊ɺͱ͢Δ ϒϧοΫεͷ๏ଇ: “ਓһΛՃͯ͠ɺνʔϜͷΩϟύγςΟ ͙͢ʹ૿Ճ͢ΔΘ͚Ͱͳ͍” ετϦʔϜΞϥΠϯυνʔϜ: Ϗδ ωεతมߋͷओཁͳʮྲྀΕ(Flow)ʯ ʹ͚ͯฤ͞ΕΔνʔϜɻ৬ೳ ԣஅεΩϧͷ༥߹ମͰ͋ΔͨΊɺ ଞνʔϜͷ࡞ۀΛͭ͜ͱͳ͘ҙ ٛͷ͋ΔΠϯΫϦϝϯτΛσϦό ϦʔͰ͖Δೳྗ͕උΘ͍ͬͯΔ ϓϥοτϑΥʔϜνʔϜ: ετϦʔϜΞϥΠϯυ νʔϜͷσϦόϦʔΛαϙʔτ͢Δج൫ͱͳΔϓ ϥοτϑΥʔϜΛࣄͷྖҬͱ͢ΔνʔϜɻϓϥο τϑΥʔϜෳࡶͳٕज़Λγϯϓϧʹ͢Δ͜ͱͰɺ ͦΕΛར༻͢ΔνʔϜͷೝෛՙΛܰݮ͢Δ ίϯϓϦέΠςΟουɾαϒγεςϜνʔϜ: ෳ ࡶ͗ͯ͢௨ৗͷετϦʔϜΞϥΠϯυνʔϜϓ ϥοτϑΥʔϜνʔϜͰରॲͰ͖ͳ͍αϒγε ςϜʹಛԽͯ͠औΓΉνʔϜɻຊʹඞཁͳ ߹ɺͦΕ͕࠷ળͰ͋Δ߹ʹͷΈฤ͞ΕΔ ΠωΠϒϦϯάνʔϜ: ҠߦֶशظؒͷҰͱ ͯ͠ɺଞͷνʔϜ͕ιϑτΣΞΛ࠾༻͢Δ͜ͱ มߋ͢Δ͜ͱΛΞγετ͢ΔνʔϜ ΠϯλϥΫγϣϯϞʔυ: ΠϯλϥΫγϣϯϞʔυ: ΠϯλϥΫγϣϯϞʔυ: ΠϯλϥΫγϣϯϞʔυ: ຊ൪ ਝͳ ϑΟʔυόοΫ νʔϜτϙϩδʔͷൃల ൃݟ ཱ֬ ར༻ ೝෛՙ: “ϫʔΩϯάϝϞϦʹׂΓͯΒΕΔϝϯλϧ ΤϑΥʔτͷ૯ྔ”ɻνʔϜͷνʔϜͷೝෛՙͷ ্ݶ੍͕ͱͳΔɻ ɾࡏੑ(intrinsic)ೝෛՙ ʔ ྖҬͷຊ࣭ʹؔ࿈͢Δ λεΫʹ·ͭΘΔෛՙ ɾ֎ࡏੑ(extraneous)ೝෛՙ ʔ औΓΉλεΫͷڥ ʹ·ͭΘΔෛՙ ɾదͳ(germane)ೝෛՙ ʔ ֶशϋΠύϑΥʔϚϯ εΛൃش͢ΔͨΊʹऔΓΘ͚ҙྗΛཁ͢ΔλεΫʹ·ͭ ΘΔෛՙ جૅͱͳΔνʔϜτϙϩδʔ(4छྨ)ͷؒͷΠϯ λϥΫγϣϯϞʔυ: ίϥϘϨʔγϣϯ: ଞͷνʔϜͱີʹ࿈ܞ͢ Δ X-as-a Servie: ࠷খݶͷίϥϘϨʔγϣϯͰ ʮԿ͔ʯΛఏڙ/ར༻͢Δ ϑΝγϦςΠςΟϯά: ΛऔΓআͨ͘Ί ʹଞͷνʔϜΛԉॿ͢Δ(ԉॿ͞ΕΔ) νʔϜ τϙϩδʔ Quick Reference Card Japanese translation by @kakutani, Oct 2021 - v1.0.1 IUUQTTDSBQCPYJPJLJJLJ23$@5FBN@5PQPMPHJFTKB -
ϓϥοτϑΥʔϜνʔϜ ଞͷνʔϜͱ 9BTB4FSWJDF ετϦʔϜ ΞϥΠϯυνʔϜ ίϯϓϦέΠςου αϒγεςϜ νʔϜ ΠωΠϒϦϯά νʔϜ
ඞཁͰ͋ΕεΫϥϜνʔϜͷ ଆʹ͕ͬͭΓೖΓࠐΉ -
νʔϜτϙϩδʔಡॻձ w ຖि݄༵ʹ࣌ؒ w ࣄલ४උಡΈࠐΈෆཁ w લಡॻλΠϜޙσΟεΧογϣϯλΠϜ w લͷಡॻλΠϜͰؾʹͳΔϙΠϯτΛ.JSPɻޙͦΕΛ͕͔ͯΓʹٞ
w ճͷ༷ࢠը͓͖ͯ͠ɺ్தͰٳΜͰ෮ؼՄೳ -
νʔϜτϙϩδʔಡॻձ ײ w ʰνʔϜτϙϩδʔʱͷͭͷνʔϜλΠϓ ͭͷΠϯλϥΫγϣϯϞʔυ ͕ొ͢Δ w ͜ΕΒͷʮ༻ޠʯʹ͍͍͍ͭͯͪͪઆ໌͠ͳ͕Β৫σβΠϯͷઆ໌Λಉ྅ ʹͨ͘͠ͳ͍ w
ϝϯόʔಉ͕࢜ಉ͡ʮݴ༿ʯΛͬͯͤΔͷͰɺ͕ૣ͍
daiksy
inariku
.png){kind=avatar}
masspeaks
pospome
tnir
.jpg){kind=avatar}
ryouto715
sergicalsix
raksulrecruiting
comi190327
tkazuaki0820
sh_fk2
aemeredith
marktimemedia
inesmontani
mfonobong
tamaranovitovic
mongodb
mojombo
marcelosomers
tonyrice
axbom
geoffreycrofte
