Slide 01
Slide 02
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480
Spacer640x480

Walking Scrum History With Patterns

Walking Scrum History with Patterns
Regional Scrum Gathering Tokyo 2018

1. Walking Scrum History with Patterns Regional Scrum Gathering Tokyo 2018 Kiro Harada - Attractor Inc.
2. Kiro Harada (原田騎郎) ✤ Attractor Inc. Founder & CEO ✤ Agile Coach, Domain Modeler, SCM Consultant, @haradakiro
3. ✤ Provides training/consulting/coaching about product development: ✤ We focus on Agile Development, Kaizen, Autonomation, Team Building, Cloud Computing, Domain Modeling etc. ✤ https://www.attractor.co.jp/ ✤ We re hiring.
4. WE ARE HIRING!! Looking for Agile Coaches to Join Us.
6. It was not originally from software.
10. The Oregon Experiment (1975)
11. A Pattern Language (1977)
12. The Timeless Way of Building
13. "At the core... is the idea that people should design for themselves their own houses, streets and communities. This idea... comes simply from the observation that most of the wonderful places of the world were not made by architects but by the people".
14. What is a pattern? Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, In such a way that you can use this solution a million times over, without ever doing it the same way twice.
15. A pattern form ✤ ✤ ✤ ✤ ✤ ✤ Solution ✤ Example (optional) ✤ Resulting Context ✤ Rationale (optional) ✤ Known Uses ✤ Related Patterns Name Alias (optional) Problem Context Forces
18. What is a pattern language?
19. Pattern Sequence ✤ ✤ If you have cases applying patterns with the following order: ✤ A→B→D→C ✤ A→B→C→D→F ✤ A→E→F It could be written as: C B A D E F
20. Japan as No.1 (1979)
21. The New New Product Development Game (1986)
22. The New New Product Development Game (1986) ✤ Built-in instability ✤ Self-organizing project teams ✤ Overlapping development process ✤ Multilearning ✤ Subtle control ✤ Organizational transfer of learning
23. In 1989 1. Nihon Kogyo Bank (日本興業銀行) 2. Sumitomo Bank (住友銀行) 3. Fuji Bank (富士銀行) 4. Daiichi Kangyo Bank (第一勧業銀行) 5. Mitsubishi Bank (三菱銀行)
24. In 2016 1. Apple 2. Alphabet 3. Microsoft 4. Amazon 5. Facebook
25. The Machine that Changed the World (1990)
26. Wicked Problems, Righteous Solutions (1990)
27. The Sashimi Approach
28. The Scrum Approach
29. The Handcuff Approach
30. The Hillside Group (1993 -) Tries to bring the idea of patterns and pattern language to software
31. Design Patterns (1994)
32. Pattern Books
33. WikiWiki Web (1995) http://wiki.c2.com/?WelcomeVisitors
34. Borland Software Craftsmanship (1994)
35. A Development Process Generative Pattern Language (1995)
36. Organizational Patterns of Agile Software Development (2005)
37. ¥
38. ¥
40. Business Object Design and Implementation Workshop
41. SCRUM Development Process (1995)
42. Process Dynamics, Modeling and Control (1994)
45. SCRUM: An extension pattern language for hyper productive software development (2000)
47. Agile Manifesto (2001)
48. WORK QUEUE INFORMAL LABOR PLAN DEVELOPER CONTROLS PROCESS SOMEONE ALWAYS MAKES PROGRESS COMMUNITY OF TRUST INTERRUPTS UNJAM BLOCKING PROGRAMMING EPISODE NAMED STABLE BASES ENGAGE CUSTOMERS TAKE NO SMALL SLIPS SURROGATE CUSTOMER ENGAGE QUALITY ASSURANCE GROUP VALIDATION COMPLETION HEADROOM RECOMMITMENT MEETING SCENARIOS DEFINE PROBLEM TEAM PRIDE FIREWALLS SIZE THE ORGANIZATION SELF SELECTING TEAM UNITY OF PURPOSE 3 TO 7 HELPERS PER ROLE PATRON ROLE PRODUCERS IN THE MIDDLE FEW ROLES PRODUCER ROLES ORGANIZATION FOLLOWS LOCATION HOLISTIC DIVERSITY COUPLING DECREASES LATENCY DISTRIBUTE WORK EVENLY MOVE RESPONSIBILITIES RESPONSIBILITES ENGAGE SHAPING CIRCULATION REALMS
49. Scrum Agile Manifesto Pattern Community Pattern Language Borland QPW Organizational Patterns A Development Process Generative Pattern Language Scrum Guide Scrum Book New New Product Development Game OOPSLA ’95 Scrum Scrum as Org Pattern Extension Wicked Problem Process Dynamics Scrum Pattern Language ScrumPLoP
51. ScrumPLoP
53. Scrum Core as Patterns There are three roles in Scrum: • • • the Product Owner; the Developer, and the ScrumMaster . They interact with each other in five main events: • • • • • the Sprint; Sprint Planning; the Daily Scrum; the Sprint Review, and the Sprint Retrospective. Underlying the framework are three artifacts: • • • the Product Backlog; the Sprint Backlog, and the Product Increment.
54. Patterns Publicly Available
55. If a Scrum implementation becomes mature, the ScrumMaster will remove Scrum as an impediment.
56. AsianPLoP 2018 CFP Submission Due is Jan 15th.
57. A Scrum Book - will be out in 2019 (hopefully)
No comments...
Missing
アジャイルコーチ、ドメインモデラ、サプライチェーンコンサルタント。認定スクラムプロフェッショナル。 外資系消費財メーカーの研究開発を経て、2004年よりスクラムによる開発を実践。ソフトウェアのユーザーの業務、ソフトウェア開発・運用の業務の両方を、より楽に安全にする改善に取り組んでいる。