Table of Contents
I attended the event “Agile × Patterns = Our Field” at the mixi meeting room.
The floor had a light brown, vinyl flooring material with a wood-like pattern. Square white four-seater tables were arranged, and in the back, there was a bar counter with various vending machines behind it. The far wall was made entirely of glass from top to bottom, providing a little attraction for those who are afraid of heights.
This event is based on the book “Agile Practice: Habits of Developers in the Field, Learned from Master Programmers“. The book, in turn, is based on the IPA’s research report “Survey on the Spread Factors and Expansion of Non-Waterfall Development“.
IPA Related Materials
Let’s thoroughly read through these materials.
Current State of Agile Practices
Agile practices are predominantly adopted for member-facing services, with only one instance in core systems.
Methodologically, Scrum is slightly more popular, but XP is also used in a similar proportion.
Notable practices in the development process include the majority conducting daily stand-up meetings, and most of them have a separate testing phase alongside the iterative process.
Agile in Small-Scale Development
In small-scale development, there are challenges such as having a small number of team members and insufficient personnel. This workshop addressed this issue, concluding that solutions could involve discarding roles with low necessity, assigning some roles to non-developer stakeholders, and having a leader figure serve as both PO and Master.
This is a kind of development pattern and often arises. “Agile Practices” describes 45 patterns, but since each development environment has its unique characteristics, some patterns may require modifications. Moreover, since IPA’s reports mostly focus on development teams with 40-100 members, significant adjustments may be needed when applying “Agile Practices.”
Agile Patterns
Hence, the recommendation of this workshop is to create patterns on-site, using the following resources. These resources were also used for pattern discussions on small-scale development mentioned earlier.
Personally, I’m interested in standardizing the testing flow as a pattern.
