Meeting Minutes of PROMCODE TC call of August 19, 2022

[Tsutomu Kamimura <tomkamimura@icloud.com>]

telecon August 19, 2022 

Scribe nomination 

Roll Call 

Next meeting: September 9, 2022 

Voting Rights Held by: 

• Kazuo Yabuta 
• Masaki Wakao 
• Tom Kamimura 
• Shigeaki Matsumoto 
• Hiroyuki Yoshida 
• Yoshio Horiuchi 
• Shigenori Kobayashi 

Chair: Tom Kamimura 

Scribe: Tom Kamimura 

Attendees: 

• Tom Kamimura 
• Masaki Wakao 
• Shigeaki Matsumoto 
• Shigenori Kobayashi 
• Hiroyuki Yoshida 
• Yoshio Horiuchi 

Discussions 

1. Communicating PROMCODE to NEC's System Integration Group 

Matsumoto-san explained his current effort in communicating PROMCODE to NEC's System Integration Group for possible use of PROMCODE to their existing projects. One question he got asked is if it is possible to have ScopeItems with two different metrics. In the current specification, metricOfScopeItemSize is defined at the project level, and therefore, all ScopeItems in the project have the same metric. With that answer to the Group, Matsumoto-san will continue communication with them. 

2. Adoption of Agile at NEC 

Kobayashi-san shared NEC's recent two presentations with the TC, one on successful use of agile project for SMBC and another their effort to create integration of popular tools to be used for agile projects. 

The first presentation explains how NEC started agile project at a major bank which has been developing software in typical waterfall style. They applied agile to a project that does not have clear requirements and priorities in the beginning. Also, the project was focused on creating applications that will be used by SMBC's sales groups. A platform to run the applications was built using waterfall model. The project was successful even though it has various challenges due to that fact that it was the first attempt to use agile for production, and testing had to be done with the platform that is developed in waterfall style in parallel. In particular, it created a monitoring feature to monitor activities of the bank's sales people that shows information such as what activities are performed more by successful sale people. Such value focused on business appealed to the bank very much. 

The presentation was on the tool integration of Miro, Jira and GitHub at AWS as the recommended tool chain for early stage of projects such as concept creation, analysis and information sharing with repository. In addition to the integration, it also includes templates of typical artifacts in each of these tools that are also integrated. Integrated tool chain and templates are expected to accelerate project start time and skill ramp up. 

accelerate 

Matsumoto-san was finally able to succeed in creating a PROMCODE server using instruction given by Wakao-san. According to Matsumoto-san, it was far easier than building a server from scratch, but a lot of laborious manual work was needed. Wakao-san suggested that maybe a better approach is to make a PROMCODE server created by using the model defined by the specification available and to create a guide to customize the server by adding attributes and properties easily. 

4. TC for the next steps 

Kamimura explained the remaining work, membership status and possible TC closure. From now to the year end, the following things can happen. 

• Another Errata as voted at the last TC to process. A next Errata process cannot start until late November. 
• Three individual members will expire by mid November. 
• If we do another Errata, TC should be active until early next year. 
• Finishing a guidance on the creation of PROMCODE server with Lyo Designer. 

Actions: 

• Wakao-san to talk to Nikami-san to get IBM's view on the use of PROMCODE to their benefit. Wakao-san to present the result at the next TC. 
• Wakao-san to create a guild to customize an existing PROMCODE server to build a server that meets the user's need. 
• Kamimura will talk to TC Admin on another Errata date and possible TC closure. 

---

Minutes created by T. Kamimura