This slide is for Ultimate Agilist Tokyo in Japan. 2012.Nov.
I want to think about agile programmer's skill set. and I want to introduce ICAgile to Japan.
I analyzed agile value, principles, practices and ICAgile.
and participant members created some mandatory skill set in this session.
See this blog entry , that will be better.
http://simple-architect.blogspot.jp/2012/11/agile-programmers-skill-set-ultimate.html
About Agile Programmer's skill sets
Ultimate Agilist Tokyo 2012
This presentation will be used tomorrow. after that session I have a plan to update this slide.
Lean Startup: It's Not Just Technology, Lives are at StakeKen Power
This is the slide deck from my keynote talk at the first Serbian ICT conference on Technology and Entrepreneurship, held Thursday November 22, 2012 in Belgrade.
For more notes, please see my corresponding Blog entry at http://systemagility.com/2012/11/22/lean-startup-and-lives/
I would love to hear your thoughts and feedback.
About Agile Programmer's skill sets
Ultimate Agilist Tokyo 2012
This presentation will be used tomorrow. after that session I have a plan to update this slide.
Lean Startup: It's Not Just Technology, Lives are at StakeKen Power
This is the slide deck from my keynote talk at the first Serbian ICT conference on Technology and Entrepreneurship, held Thursday November 22, 2012 in Belgrade.
For more notes, please see my corresponding Blog entry at http://systemagility.com/2012/11/22/lean-startup-and-lives/
I would love to hear your thoughts and feedback.
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
Facilitation Foundations - A Guide to Effective Agile MeetingsAgileDad
Facilitation Foundations is a presentation that has been given at multiple Agile Conferences. The focus of the presentation is improving the quality and effectiveness of Agile Meetings.
Many who have downloaded this deck have made it a standard for assisting organizations who are struggling with spending too much time and money on Agile Meetings.
Hundreds of organizations have now realized the benefit of Rapid Release Planning! Compared to traditional release planning, this increases your estimation and sizing accuracy from 34% to over 85%! Rapid Release Planning is one of the CORE Components for getting teams engaged early and using their Rapid Sizing to better forecast which candidates will successfully be a part of the release. The keys to making this work successfully revolve around making gut decisions about size and relative complexity of the items being estimated and validated.
Presented in November, 2008 at the LavaCon Professional Development Summit. This presentation gives an overview of agile documentation, and talks about the benefits and challenges of the Agile methodology to technical writers.
Value Stream Manager concept applied to Software Product DevelopmentKen Power
his is the slide deck from my talk at LESS 2012, the Lean Enterprise Software and Systems conference in Tallinn, Estonia.
http://SystemAgility.com/events
Skiing and boxing: coaching product and enterprise teamsSergey Prokhorenko
Successful Agile transitions depend on a coaching approach just as much as the development of a good sports team. One is not going to assign the same exercise programs to a pro skier and a boxer; the same applies to different software development teams.
In this study we summarize experiences from two Agile transformation projects, a travel website and investment bank risk management software. We discuss common points and distinctive features in requirements management, innovations, customer collaboration and team motivation.
Overselling Agile Certifications and Frameworks : Presented by Sridharan VembuoGuild .
Agile is only for smaller projects and/or startup organisations - Not Anymore. Taking my own and my organisation's experience, Agile is a proven methodology that is well suited for delivering complex, distributed, multi-year enterprise programs, for many years now.
While this is really a great thing for agile enthusiasts and practitioners, it’s a bit of worrying sign for me the increased recognition and popularity the ‘Agile Certifications’ and ‘Agile Frameworks’ are receiving among individuals and organisations who would like to adopt Agile to stay relevant in current world.
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
The Empowering Agile Teams Presentation has been presented at numerous Agile Conferences and has been VERY well received. Many teams get frustrated due to the lack of understanding of what they are expected to deliver vs what has been perceived. Gone are the days of opacity. Teams are better equipped to handle the day to day workload and are less fearful of commitment in an environment where healthy team relationships are valued.
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
Business Value of Agile Methods: Using Return on InvestmentDavid Rico
Provides a brief introduction to agile methods, an overview of popular agile methods, and a brief survey of the benefits of agile methods as reported by major industry studies. Also provides a suite of basic metrics useful for quantifying the business value of agile methods. Discusses parametric models derived from industry data, a methodology for estimating the return on investment (ROI) of agile methods, and a comparison of the costs and benefits of 11 major agile and traditional methods.
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
Facilitation Foundations - A Guide to Effective Agile MeetingsAgileDad
Facilitation Foundations is a presentation that has been given at multiple Agile Conferences. The focus of the presentation is improving the quality and effectiveness of Agile Meetings.
Many who have downloaded this deck have made it a standard for assisting organizations who are struggling with spending too much time and money on Agile Meetings.
Hundreds of organizations have now realized the benefit of Rapid Release Planning! Compared to traditional release planning, this increases your estimation and sizing accuracy from 34% to over 85%! Rapid Release Planning is one of the CORE Components for getting teams engaged early and using their Rapid Sizing to better forecast which candidates will successfully be a part of the release. The keys to making this work successfully revolve around making gut decisions about size and relative complexity of the items being estimated and validated.
Presented in November, 2008 at the LavaCon Professional Development Summit. This presentation gives an overview of agile documentation, and talks about the benefits and challenges of the Agile methodology to technical writers.
Value Stream Manager concept applied to Software Product DevelopmentKen Power
his is the slide deck from my talk at LESS 2012, the Lean Enterprise Software and Systems conference in Tallinn, Estonia.
http://SystemAgility.com/events
Skiing and boxing: coaching product and enterprise teamsSergey Prokhorenko
Successful Agile transitions depend on a coaching approach just as much as the development of a good sports team. One is not going to assign the same exercise programs to a pro skier and a boxer; the same applies to different software development teams.
In this study we summarize experiences from two Agile transformation projects, a travel website and investment bank risk management software. We discuss common points and distinctive features in requirements management, innovations, customer collaboration and team motivation.
Overselling Agile Certifications and Frameworks : Presented by Sridharan VembuoGuild .
Agile is only for smaller projects and/or startup organisations - Not Anymore. Taking my own and my organisation's experience, Agile is a proven methodology that is well suited for delivering complex, distributed, multi-year enterprise programs, for many years now.
While this is really a great thing for agile enthusiasts and practitioners, it’s a bit of worrying sign for me the increased recognition and popularity the ‘Agile Certifications’ and ‘Agile Frameworks’ are receiving among individuals and organisations who would like to adopt Agile to stay relevant in current world.
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
The Empowering Agile Teams Presentation has been presented at numerous Agile Conferences and has been VERY well received. Many teams get frustrated due to the lack of understanding of what they are expected to deliver vs what has been perceived. Gone are the days of opacity. Teams are better equipped to handle the day to day workload and are less fearful of commitment in an environment where healthy team relationships are valued.
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
Business Value of Agile Methods: Using Return on InvestmentDavid Rico
Provides a brief introduction to agile methods, an overview of popular agile methods, and a brief survey of the benefits of agile methods as reported by major industry studies. Also provides a suite of basic metrics useful for quantifying the business value of agile methods. Discusses parametric models derived from industry data, a methodology for estimating the return on investment (ROI) of agile methods, and a comparison of the costs and benefits of 11 major agile and traditional methods.
[db tech showcase Tokyo 2016] D24: データベース環境における検証結果から理解する失敗しないフラッシュ活用法 第三章 ~デ...Insight Technology, Inc.
フラッシュのGB単価はHDDと並び、オールフラッシュ導入が加速化する一方、インラインでの重複排除、圧縮機能のオーバーヘッド、メンテナンス / 障害時の影響など、気をつけなければいけない事は沢山あります。本セッションでは、オールフラッシュ製品(Pure Storage)上でOracle Databaseを稼働させた検証結果と生のデモンストレーションをベースに、DB on Pure Storageならではの活用法を考えます。
No one can predict unforeseen killer applications enabled by new wireless technologies (e.g., 5G network) beforehand. Looking back 20-year history of mobile wireless network, it has been very tough to prepare killer applications a prior to the emergence of new radio access technologies. NTT DOCOMO’s i-mode was not prepared for 2G always-on network., and invented after that. Smartphones with application markets became popular after the 3G network deployment, for which video conversation had been prepared a a killer service candidate and which didn’t make a success. 4G network brought us more capacity and low latency network, while youtube, hulu, Netflix, facebook messenger and others were natured by such a rich mobile communication environment with cloud platforms.
Everyone, nowadays, are talking about a buzz word “IoT” without having a solid idea for monetization. Such a bold discussion may mislead our radio access technology development to an unpromised land.
My recommendation is “Decide as late as possible, particularly for decisions that are irreversible.” According to software engineering terminology, it says also “late binding.” Don’t rush into a 10Gps broadband network nor a hyper low latency and 0% packet-loss assured network.
Having said that, the 5G beam forming radio technology (enabled by Massive MIMO) will bring a unique communication characteristics with a more reliable, higher capacity and 3D-positioning. My bet on 5G killer applications is “Night Golf” where you can play golf without seeing a ball which is being identified by the 5G radio. haha.
Overview of agile values
This presentation shows some core concepts that make agile software development different.
This will help your team familiar with agile concepts and start boosting your team performance.
This presentation was used in "Agile workshop for FPT Aptech Hanoi students" in December 2012.
This doc covers most of core practices of an agile developer.
A brief and visual introduction to the Agile.
Learn the Agile mindset and the big 3 (Extreme Programming, Scrum, and Kanban). Be able to whiteboard a simple view of how each one works to get things done and make things happen.
The Agile Method and AGILE ISD; how to use each to improve your training programChristopher King
The term "agile" is being used readily to express the desire organizations have to be responsive and flexible to change in their organization. The Agile development method is designed to quickly and efficiently produce software products. Recently its application has expanded to other areas including training products. AGILE ISD is a new way of thinking about education where performance is the metric that drives the development and delivery decisions in an organization’s training program. It recognizes the long tail of learning and the five moments of learning need. AGILE ISD provides strategies for creating a culture of learning at your organization.
While these two agile methods are for different purposes, they are not mutually exclusive. This session will explain how your organization can use both methods to your advantage and success. We clarify some of the different uses of the term agile within the learning and development community. In this session we will cover:
• Agile (software) movement - its history, its main tenets, different types of agile frameworks and how to incorporated into the ADDIE training methodology
• AGILE ISD – is a methodology developed by Dr. Conrad Gottfredson that aims to supplement ADDIE by expanding its scope to include informal learning design. We cover its history, its main tenants, principles of agile education, and incorporating AGILE ISD into the ADDIE training methodology
• How the two approaches can both be successfully applied in your L&D organization
Agile has become mainstream in the IT industry, since that the multiplication of Agile practices which makes Agile implementation complex and uncertain, we have started to see failure in Agile implementations.
During this presentation we will start a simplification process by going back to the source of Agile, understand what Agile is and what it is not. We will discover what is the Heart of Agile, its essence, and how it embraces management
Agile has become mainstream in the IT industry, since that the multiplication of Agile practices which makes Agile implementation complex and uncertain, we have started to see failure in Agile implementations.
During this presentation we will start a simplification process by going back to the source of Agile, understand what Agile is and what it is not. We will discover what is the Heart of Agile, its essence, and how it embraces management
A Practical Approach to Agile Adoption - Case Studies from Egypt by Amr Noama...Agile ME
Agile Adoption is a big organization transition project. A big bang approach to Agile Adoption involves real risks and may lead to failure. Instead, small, continuous, and valuable improvements are more viable for most organizations. In this interactive session, we will start with an overview of the Agile mindset, values and principles, and will highlight the major differences between Agile and traditional approaches to managing software projects. Then, we will explain our approach for adopting agile which is incremental and iterative in nature. Finally, we will present some case studies and will share some interesting observations and conclusions collected through working with more than 40 companies during the last 6 years.
A New Business Model of Custom Software Development For Agile Software Develo...Tsuyoshi Ushio
Successful business model of custom software for agile development.
22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering
November 16-21, 2014, Hong Kong
Easy to add, hard to remove. It is the case in many situations including software development, process improvements etc. How we can stay lean eliminating unnecessaries and be agile? We’ll explore the solutions with pattern mining workshop sessions. Stay Lean, Be Agile!
AgileRoots 2014
6. What is
Agile Development?
Agile software development is a group of software development methods based on iterative and
incremental development, where requirements and solutions evolve through collaboration between
self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development
and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to
change. It is a conceptual framework that promotes foreseen interactions throughout the development
cycle. The Agile Manifesto[1] introduced the term in 2001.
WIKIPEDIA http://en.wikipedia.org/wiki/Agile_software_development
12年11月18日日曜日
7. Agile Manifesto
Value Principle
1. Our highest priority is to satisfy the customer through early
and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development.
Individuals and interactions Agile processes harness change for the customer's competitive advantage.
over processes and tools
3. Deliver working software frequently, from a couple of weeks to a
couple of months, with a preference to the shorter timescale.
4. Business people and developers must work
together daily throughout the project.
Working software over
comprehensive 5. Build projects around motivated individuals. Give them the environment
documentation and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to
and within a development team is face-to-face conversation.
Customer collaboration 7. Working software is the primary measure of progress.
over contract negotiation 8. Agile processes promote sustainable development. The sponsors, developers,
and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
Responding to change over 10. Simplicity--the art of maximizing the amount of work not done--is essential.
following a plan
11. The best architectures, requirements, and designs emerge from
self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective,
hen tunes and adjusts its behavior accordingly.
12年11月18日日曜日
9. XP practices
http://ullizee.wordpress.com/2009/11/02/extreme-programming-revisited-part-i/
12年11月18日日曜日
10. five objectives for
agile programmer
Continuous Delivery of valuable software
Embrace change
Deliver Working Software frequently
Continuous attention to Technical Excellence and Good Design
Create the best architecture, requirements and design emerge
form Self-Organization-Team
Programmer related Agile Manifesto 12 principles
12年11月18日日曜日
11. Manifesto for software
craftsmanship
Not only working software, but also well-crafted software
Not only responding to change, but also steadily adding value
Not only individuals and interactions, but also a community of professionals
Not only customer collaboration, but also productive partnerships
http://manifesto.softwarecraftsmanship.org
12年11月18日日曜日
12. ICAgile
ICAgile exists to support education in the agile space.
Use ICAgile’s definitive learning roadmap to find accredited courses
that recognize students as they progress along their specialty paths.
Fundamentals of Agile
Agile Business Analysis
+Value Management
Agile Project Management
Agile Facilitation + Coaching
Agile Software Design +
Programming
Agile Testing http://www.icagile.com/index.html
12年11月18日日曜日
13. Learning Areas
Agile Software Design +Programming
1.1. Test Driven Development
1.2. Good Design
1. Designing & Programming 1.3. Technical Debt
1.4. Refactoring
1.5. Legacy Code
2.1. Acceptance Test
2. Testing
2.2. Programming the test
3.1. Collaboration
3. Teams and Behaviors 3.2. Collective Accountability
3.3. Team Activity
4.1. Function-Based Development
4. Structuring Work
4.2. Planning
5. Environment 5.1. Leveraging Tools
12年11月18日日曜日
14. five objectives and
practices
Five Objectives
Practices
Agile Programmer’s mandatory skill Map
12年11月18日日曜日
17. Golden Circle
Why is Vision
is our gut
has emotion and heart
create something bigger then your self
How is Mission
brings up guiding principle Why
What is Rules How
has practices What
is dynamic organic
Why time to market(ex)
How 12 principles
What priactices
1. Post What (Practice ex. TDD)
2. Post How (Principles ex 12 principles)
3. Post Why (Guts, Visions ex. time to market)
12年11月18日日曜日
20. We thought
This is the
Agile Programmer’s
Skill set
Workshop Results in 10 minutes
12年11月18日日曜日
21. Team Golden Circle
Rhythm
Collective Ownership Repository
Coding
Standard
Team Building Code
Review
Self Organizing Team
PairProgramming
Visualization WhiteBoard Refactoring Planning Dairy Meeting
Kaizen
Burn down Design
Working Software Retrospective
chart
Ceremony
Trust & Respect
Drink Party
War-Room
12年11月18日日曜日
22. Team Door Side
Collaboration with customer
Collaboration with team members
ability to
think realization
Identify customer’s
Power Structure
ability to think
Listening Skill
Vagrant &
chef!!!
12年11月18日日曜日
23. Team 7
Understand
Business Requirement
Embrace Change
Design Test
Stout heart
ability to read someone’s code
ambition
sincerity
Communication Skill
coarse grained design
architecture
12年11月18日日曜日
24. Team Maid
Simple Design
mix up the ideas
that written in some papers Refactoring
Simple
Design Test
Design
Recognize requirement
communication Pair Programming
Continuous Delivery
proposal
12年11月18日日曜日
25. Team
Ushio LOVE
Ability to
embrace change Frequent feedback Keep on something!
Test Driven Development
Passion
Continuous delivery
of valuable software
Object Oriented
Continuous Retrospective
Integration
Face-to-Face
Communication
Continuous
Delivery
UML
Common Language or something..
Communication Skill
12年11月18日日曜日
28. Appendix.
Technical element
of
iCAgile
Agile Software Design +
Programming
every books are referenced by Amazon.co.jp or Amazon.com
12年11月18日日曜日
29. 1. Designing & Programming
1.1. Test Driven Development
1.1.1. The value of test-driven development
1.1.2. Identifying usage patterns to define the object or function interface
1.1.3. Identifying completeness of conditions that drive usage patterns in the code
1.1.4. Avoiding duplication in the conditions
1.1.5. Red-Green-Refactor
1.1.6. Test Speed
Test Driven Development: By Example Test-Driven iOS Development Growing Object-Oriented Software, Guided by Tests
Kent Beck (2002) Graham Lee (2012) Steve Freeman, Nat Pryce (2009)
required knowledge
12年11月18日日曜日
30. 1. Designing & Programming
Architecture (1.2.1)
1.2. Good Design Beck’s 4 rules of simple design(1.2.2)
McCabe complexity (1.2.2)
DRY (1.2.3.)
SOLID (1.2.3.)
1.2.1. Role of Design-in-the-Large
1.2.2. Simple design
1.2.3. Evaluating Design and Design Principle
1.2.4. Design Patterns
1.2.5. Clean Programming
1.2.6. Listening to your tests
Agile Software Development The Art of Readable Code
Robert C. Martin (2011) Dustin Boswell, Trevor Foucher (2011)
12年11月18日日曜日
31. continue...
Beck’s 4 rules of simple design
Pass all tests
Contains no duplications
Express the intent of the programmers
Minimizes the number of classes and methods
http://theholyjava.wordpress.com/2011/02/14/clean-code-four-simple-design-rules/
Patterns of Enterprise Application Architecture
Martin Fowler (2002) SOILD
Single responsibility principle
Open/Closed Principle
Liskov substitution principle
Interface segregation principle
Dependency Inversion Principle
If you want to understand SOLID , Read Agile Software Development!
Design Patterns: Elements of 増補改訂版Java言語で学ぶ
Reusable Object-Oriented Software デザインパターン入門
Erich Helm, Richard Johnson,
Ralph Vissides, John Gamma(1994) 結城浩(2004)
Pattern-oriented software architecture
Frank Buschmann, etc (1996)
12年11月18日日曜日
32. continue...
If you can’t understand OO, try these.
Just Enough Software Architecture: A Risk-Driven Approach オブジェクト脳のつくり方
George Fairbanks (2010) 牛尾 剛 (2003)
Agile Education by Object Game
AGILE2011 session
http://enterprisezine.jp/iti/detail/3385?p=2
12年11月18日日曜日
34. 1. Designing & Programming
DB, HTML refactoring (1.4.4.
1.4. Refactoring
1.4.1. Principles of refactoring
1.4.2. Code smells
1.4.3. Common refactorings
1.4.4. The larger world of refactoring
1.4.5. Refactoring
Refactoring: Improving the Design of Existing Code Refactoring Workbook Refactoring Databases:
Martin Fowler , Kent Beck, John Brant, William C. Wake (2003) Evolutionary Database Design
William Opdyke, Don Roberts(1999) Scott W. Ambler (2006)
12年11月18日日曜日
35. 1. Designing & Programming
witout test code (1.5.2.)
1.5. Legacy code refactoring tools
statically typed langage
breaking down into steps
catch errors with compiler
dynamic language
1.5.1. Approaching legacy code breaking down into steps
1.5.2. Refactoring without test which are likely less error
1.5.3. Retrofitting test onto legacy code
「派生開発」を成功させるプロセス改善の技術と極意
Working Effectively With Legacy Code
Michael Feathers (2004) 清水吉男(2007)
12年11月18日日曜日
36. 2. Testing
2.1. Acceptance Testing
Unit Test (2.1.1.)
2.1.1. Types of tests to automate Component Test
2.1.2. Test as Specification and Documentation Acceptance Test
2.1.3. ATDD as aid to design thinking non-functional Test
2.1.4. Tester-Business-Developer Collaboration
2.1.5. ATDD Process ATDD 3 different forms (2.1.6.)
a text based form ( cucumber)
2.1.6. ATDD Styles & Tools
table (FIT)
2.1.7. Testing the system bypassing the user interface in code (xUnit)
2.1.8. Testing the system through the user interface
2.1.9. Cross-functional testing cucumber (2.1.8.)
Robot Framework
non-functional tests(2.1.9.)
capacity
response time
security
etc...
ATDD by Example: A Practical Guide to Acceptance Test-Driven Development
Markus Gartner (2012)
12年11月18日日曜日
37. 2. Testing
2.2. Programming the tests
test doubles (2.2.6.)
stub
2.2.1. Coding Tests by Intention mocks
2.2.2. Testing the tests fakes
2.2.3. Test execution time spies
2.2.4. Fixture Setup
2.2.5. Result Verification
2.2.6. Use test doubles
2.2.7. Refactoring Test
at least 3 different ways
of verifying the test code
(2.2.2.)
xUnit Test Patterns: Refactoring Test Code
Gerard Meszaros (2007)
12年11月18日日曜日
38. 3. Teams and behaviors Class Diagrams (3.1.5.)
Sequence Diagram
3.1. Collaboration Instance and Deployment diagrams
CRC cards and similar
3.1.1. Collaboration Skills
task and kanban board (3.1.6.)
3.1.2. Work allocation
story maps
3.1.3. Stakeholder Conversations burn chart
3.1.4. Pair Programming cumulative flow diagrams
3.1.5. Communication design physical and electronic radiators
3.1.6. Information Radiators
3.1.7. Working spaces
3.1.8. Distributed teams
UML Distilled: A Brief Guide to the Standard Object Modeling Language
Agile Software Development: The Cooperative Game
Martin Fowler (2003)
Alistair Cockburn (2006)
12年11月18日日曜日
39. 3. Teams and behaviors
3.1. Collaboration
Communication Skills (3.1.1.)
active listening
self- or shared facilitation
being open for suggestions & criticisms
constructive criticism
making sefe-to-be-honest
safe-to-fail
giving respect
hygiene
speaking up
staying silent
debating
yielding
recognizing defferent communication styles
http://cte.uwaterloo.ca/teaching_resources/tips/teamwork_skills.html
12年11月18日日曜日
40. 3. Teams and behaviors
3.2. Collective accountability
3.2.1. Collective accountability
3.2.2. Collective Ownership
three models (3.2.2.)
owner-only
any-pair
any-one
Extreme Programming Explained: Embrace Change
Kent Beck (1999)
12年11月18日日曜日
41. 3. Teams and behaviors
3.3. Team activity
3.3.1. Reflection workshops
3.3.2. Daily meetings
Agile Retrospectives: Making Good Teams Great
Esther Derby ,Diana Larsen (2006)
12年11月18日日曜日
42. 4. Structuring Work
4.1. Function-Based Development function units (4.1.1.)
Primary work breakdown structure
understanding the need for coarse-,
4.1.1. Developing in function units medium-, and fine-grained function
4.1.2. Slicing use case, story maps minimum-
4.1.3. Cross-functional constraints marketable features or feature lists
4.1.4. Technical risk reduction heuristic for good work unit
Risk reduction (4.1.4.)
spikes
prototypes
walking skeleton
others
Writing Effective Use Cases
Alistair Cockburn (2000)
User Stories Applied 要求開発 User Story Mapping
Mike Cohn (2004) 山岸耕二他(2006) Jeff Patton (2013)
12年11月18日日曜日
43. 4. Structuring Work
4.2. Planning
4.2.1. Sizing
4.2.2. Planning at different granularities
4.2.3. Scheduling Risk Mitigation Items
4.2.4. Sequencing work
Agile Estimating and Planning
Mike Cohn (2005)
12年11月18日日曜日
44. 5. Environment
5.1. Leveraging tools
5.1.1. Version Control
5.1.2. Build Tools
5.1.3. Continuous Integration
5.1.4. Continuous Delivery
Continuous Delivery: Reliable Software Releases through
Build, Test, and Deployment Automation Continuous Integration: Improving Software
Jez Humble, David Farley (2010) Quality and Reducing Risk
Paul M. Duvall, Steve Matyas,
Andrew Glover (2007)
Pragmatic Guide to Git
Travis Swicegood (2010)
12年11月18日日曜日
45. Sorry Japanese only
メソッド屋の日記
こんなプログラマはアジャイル出来ますって言ったらアカンやろ
http://d.hatena.ne.jp/simplearchitect/20120810/1344615415
12年11月18日日曜日