從進入CDC, 整個研發團隊是瀑布開發模式, 瀑布模型(Waterfall Model)瀑布模型是將軟件生存週期的各項活動規定爲按固定順序而連接的若干階段工作,形如瀑布流水,最終得到軟件產品。
說到這裏,首先要定義角色
ROLES AND RESPONSIBILITIES
- PJM(項目管理者)
- supervise schedule for work ordered to other teams (督導時間表,安排好與其他團隊的工作)
- risk and cost management (風險管理和費用(成本)管理)
- driving overall project progress for each stage(驅動在每一個階段的項目進度 )
- cross-team process creation, update and discussions (跨團隊的任務的創建、更新和討論)
- inform DVM about quality concerns (提示DVM關注項目質量)
- manage project management tools (管理項目管理工具,例如Jira,confluence)
- DVM (開發管理者)
- enforce process (實施進程)
- drive timely delivery of high-quality code (驅動及時交付高質量的代碼)
- provide estimates in order to know what to include in each release as well as to calculate ROI (提供每個發佈包含哪些內容的預估並且計算ROI)
- Engage PJM to deal with outside Ichiba team schedule, risk and issues as soon as possible. (DVM及時發現開發中的問題,並及時跟PJM溝通,以確保PJM能夠儘快地處理與外部團隊的排期,風險和問題)
- PDM (產品管理者)
- enforce process(實施進程)
- set priority for features, and bugs when needed (設定產品特徵和BUG的優先級)
- drive delivery of high-quality specifications (驅動交付高質量的式樣)
- regularly inform team members about product roadmap (定期向團隊成員公佈產品路線圖)
- provide GMS estimates in order to prioritize requirements as well as to calculate ROI (提供GMS來排定需求的優先級)
- create user manuals and release notes (創建用戶手冊和發佈說明)
- Engage PJM to deal with outside Ichiba team schedule, risk and issues as soon as possible. (PDM及時發現式樣定義中的問題,並及時跟PJM溝通,以確保PJM能夠儘快地處理與外部團隊的排期,風險和問題)
- test releases, ensure high quality (測試發佈的版本,確保高質量輸出)
Process | Time | Responsibilities | Role | Participants |
Deliverable |
comment |
---|---|---|---|---|---|---|
0. Management | ||||||
|
Budget Management | PJM |
|
Cost Model |
|
|
|
Time Management (overall) | PJM |
|
Excel Schedule and WBS |
|
|
|
Time Management (detailed) |
|
|
PJM receives estimations for Due Dates and input into Project schedule |
|
|
|
Coordination with CWD (detailed) | PDM |
|
|
|
|
|
Coordination with BU | PDM | PJM | PDM: 分享季度開發計劃 |
|
|
1. Prepare Budget Application | ||||||
|
1st week at month of prepare budget application (case by case) |
Preliminary requirements discussion (初步需求討論會) |
PDM |
Team Leader Shiwei(Option) |
7. 確定PJM |
|
2nd week at month of prepare budget application | Functional Specification (detailed) | PDM |
Team Leader PJM |
Confluence document
|
|
|
|
3rd week at month of prepare budget application (case by case) |
prototype design discussion (原型討論會) |
PDM |
Team Leader |
1.工數的預估(給出哪些無法預估) 2.評估所需資源(infra、CWD等) |
1.講解需求UI的呈現及交互方式,討論、確定交互及UI呈現的可行性、合理性 |
|
|
|
|
|
|
|
|
4th week at month of prepare budget application (case by case) |
Draft MRD (初稿MRD討論會) |
PDM |
PJM DVM ENG |
The modifying part of draft MRD | 講解MRD(MRD PPT初稿),討論、確定MRD中描述的需求及範圍的準確性、合理性; |
|
4th week at month of prepare budget application (case by case) |
MRD fixed | PDM |
PJM DVM ENG |
Fixed MRD |
講解fixed MRD,最終確認MRD; 2. 確認有其他開發團隊參與,則需準備相應的英文資料,並約相關團隊進行MRD的講解。 |
2.Budget Application |
1-Budget Application | |||||
Month of budget application |
Send MRD (English version) to CWD | PDM |
|
Notice the month of budget application , to remain the resource. |
|
|
1st weeks at month of budget application |
Estimate Development Effort | DVM | ENG | Submit human cost and schedule to DVM |
|
|
|
1st weeks at month of budget application | Adjusting human resource | DVM |
|
Submit human cost and schedule to PJM |
|
|
1st weeks at month of budget application | Meeting with Infra member for infra Estimate |
PJM |
DVM ENG |
Meeting minutes from discussions with Infra Members (PDM introduce project, DVM Submit apply content) |
|
1st weeks at month of budget application | QA Estimate | PJM | PDM |
Supply budget to Admin for update of ROS. |
|
|
1st weeks at month of budget application | Security Audit Estimate | PJM | System Security Office |
Supply budget to Admin for update of ROS. |
|
|
1st weeks at month of budget application | Create Overall Schedule | PJM |
DVM PDM |
Excel Schedule |
|
|
1st weeks at month of budget application | Create Detailed Schedule (implementation) | DVM |
|
Detailed Schedule |
|
|
|
2nd weeks at month of budget application |
Explain of Schedule and Mandays |
PJM | DVM | Approved Schedule and Mandays |
DVM to report Mandays PJM to report Schedule |
Approved on Friday of 2nd weeks at month of budget application |
Business Case Creation and Approval |
PDM/PJM |
|
Project introduction PPT Mandays, Schedule, BudgetApplication, |
Taiwan Service Decision Making MTG summit and get approval PDM : Project introduction PPT (Function, KPI) PJM: BudgetApplication,Mandays, Schedule) |
|
|
2nd weeks at month of budget application | PMO Ticket | PJM |
|
Submit PMO ticket to SSP get approval |
|
|
3rd weeks at month of budget application |
Registration in EYES |
PJM |
|
Send Email to Japan PDM to support get EYES Code in EYES system. |
|
|
3rd weeks at month of budget application | Dezi Ticket | PJM |
|
Submit DEZI ticket to apply budget |
|
3. Project Start Phase | 0_Project Start | |||||
1st week before design stage |
Process Design (development process. select tools) | PJM |
|
Confluence documentation
|
reference: |
|
1st week before design stage |
Communication Management | PJM |
|
Confluence documentation |
reference: |
|
1st week before design stage |
Project Objectives | PJM |
|
Confluence documentation |
reference: |
|
1st week before design stage |
Education (project management training) | PJM |
|
|
reference: |
|
|
1-3 days before design stage |
Project start Meeting | PJM | DVM,PDM,ENG | All project members to attend (about MRD question, Schedule .etc) |
|
|
1-3 days before design stage | Create WBS | PJM |
|
WBS | Milestone (Task of each stage) |
|
1-3 days before design stage | Create Detailed WBS | DVM |
|
WBS (Design, development,ENG test,Release) | detailed task |
|
1-3 days before design stage | Create Detailed WBS | PDM |
|
WBS (PM test) | detailed task |
|
1st week before design stage |
UI Specification Meeting | PDM | CWD | UI Specification document |
|
|
case by case | UI Design Estimate according to UI Specification | CWD |
|
Estimated man-days and cost | PDM need to confirm with Taiwan |
|
case by case | Provide the Due date according to ENG' schedule | PDM |
|
Due date for providing HTML |
|
|
case by case | Provide CWD Schedule according to ENG's due date | CWD |
|
CWD Schedule |
|
|
|
|
|
|
|
|
4. Design and design review | ||||||
Design | 3-5 Days | Overall Architecture | DVM | ENG | Confluence documentation |
|
|
DB Schema Design | DVM | ENG | Confluence documentation |
|
|
|
Hardware Design | DVM | ENG | Apply to Infra and Confluence documentation |
|
|
|
Application Design (RMS/MALL) | DVM | ENG | Confluence documentation |
|
|
Design Review | 1-2 Days | Overall Architecture | Team Manager : ZhuShiwei | DVM | Approved documentation | Architecture Design and Program Design |
|
|
DB Schema Design | Team Leader | DVM,ENG | Approved documentation |
|
|
|
Hardware Design | Infra Members | DVM,ENG | Approved documentation |
|
|
|
Application Design (RMS/MALL) | Team Leader | DVM,ENG | Approved documentation |
|
|
Case by case | Create Mock-ups | CWD | PDM |
|
|
|
Case by case | Confirm Mock-ups | PDM |
|
Confirmed Mock-ups | PDM need to confirm with Taiwan |
|
Case by case | Create Design (Image Description) | CWD | PDM |
|
|
|
Case by case | Confirm Design (Image Description) | PDM |
|
Confirmed Design (Image Description) | PDM need to confirm with Taiwan |
|
Case by case | Create HTML page | CWD | PDM |
|
|
|
case by case |
Confirmed HTML page |
DVM/PDM | ENG | Confirmed HTML source file (確定設計原型) | PDM need to confirm with Taiwan |
|
|
|
|
|
|
|
Apply support | ASAP | Apply QA | PJM |
|
Apply JIRA ticket to QA |
|
|
ASAP | Apply Appscan | DVM |
|
Apply JIRA ticket to System Security Office |
|
|
ASAP | Apply Security Audit | DVM |
|
Apply JIRA ticket to System Security Office |
|
|
The last day of design stage | Design finished MTG (CDC) | DVM |
ENG PJM PDM(Option)
|
Confluence documentation(Architecture Design Document,Program Design Dcoument)
|
All project members to attend (Judge to whether can enter the next phase ) |
5.Development & Unit test | 3-Development | |||||
|
Case by case | Programing | DVM | ENG | Coding |
|
|
Case by case | Unit Test | DVM | ENG |
(Unit Test Code Coverrage(>=80%) |
|
|
3-5 days | Code Review | DVM | ENG | Code source |
|
6.DEV Test | ||||||
|
|
Prepare test case | DVM | ENG | Test case document |
|
|
|
DEV Release | DVM | ENG | n/a |
|
|
|
Dev Test | DVM | ENG | Problem tickets |
|
|
|
Bug Fix after Test | DVM | ENG | Fixed ticket |
|
|
1-2 days before dev test finished | DEV test result Demo MTG | DVM |
ENG PJM PDM(Option) |
Demonstrable function |
ENG demonstrate their own development efforts on DEV |
7.Internal STG Test | 4-Internal STG Test | |||||
|
2-5 days | Prepare Join Test Case | PDM |
|
Created test cases |
|
|
1 day | Test case review MTG | PDM |
DVM ENG PJM(Option) |
Meeting with DVM, and review the test case |
|
|
1 week or more | Prepare Load Test Case | DVM | ENG | DVM arraign Eng prepare Load test case document |
|
|
1 days | Load test case review | DVM |
|
review Load test case |
|
|
5 days |
INFRA (JP) Review Load test case |
DVM |
|
Need to INFRA (JP) Review Load test case |
|
|
case by case | Join Test (ENG) | DVM | ENG | DVM arraign Join Test by ENG |
|
|
1-2 days before Eng stg test finished | STG test result Demo MTG | DVM |
ENG PJM PDM |
ENG demonstrate their own development efforts on STG, PDM attend. |
|
|
case by case | Join Test (PDM) | PDM | ENG | Join Test Report | STG測試結束以後發出report說明STG階段結束 |
|
3-5 days | Load Test | DVM | ENG |
Load Test report |
DVM arraign Eng to do Load Test, and submit Load Test report to INFRA (JP) |
8.External STG Test | 5-External STG Test | |||||
|
1 weeks before QA test | QA Test case review | PDM/DVM |
|
QA test case docuement |
PDM review UI part, DVM review function part and flow part. |
|
case by case | QA Test | QA Team |
PDM DVM |
Problem tickets |
|
|
3-5 days | QA Test after bugfix | DVM | ENG | Fixed ticket | DVM arraign arraign to fix these tickets |
|
1-3 days | Appscan Test |
Executed by CDC (DVM) Executed by SSO |
|
Appscan Test report |
|
|
0 or 1 day | Appscan Test after bugfix | DVM | ENG | Fixed ticket | DVM arraign arraign to fix these tickets |
|
3 ~5 days | Security Audit Test | Executed by SSO |
|
Security Audit Test report |
|
|
0 or 2 days | Audit Test after bugfix | DVM | ENG | Fixed ticket | DVM arraign ENG to fix these tickets |
|
case by case | JV Test | JV | PDM/Eng | Fixed ticket | DVM arraign ENG to fix these tickets |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
9.Release |
Release |
Reference: Service Operation [Service Transit] Release & Service Test Work Flow |
||||
|
1-2 weeks before release | Merge code and Tag and test | DVM | ENG |
Merged code |
|
|
2 weeks before release | Prepare TimeSchedule and release manual | DVM | ENG |
TimeSchedule Operation manual |
|
|
2 weeks before release | Prepare Release confirm manual | PDM |
|
Confirm manual |
|
|
2 weeks before release | Release manual Review | DVM |
|
reviewed Release manual |
|
|
2 weeks before release | TimeSchedule Review meeting | DVM |
PDM ENG PJM |
TimeSchedule | Share TimeSchedule to all please release members |
|
2 weeks before release | Release Rehearsal | DVM/PDM | ENG | Confirmed TimeSchedule/Operation manual/Confirm manual | Release Rehearsal on STG |
|
2 weeks before release | Adjuest after Release Rehearsal | DVM | ENG | Fixed function or UI | Adjuest after Release Rehearsal on STG |
|
1-2 weeks before release | Release Plan Sharing on IIPM(Option) | PDM |
|
IIPM Report | Share Release Plan |
|
1 week before release | Release Judge meeting | PJM |
DVM PDM TM (Shiwei) SSP(Fumiyama) |
Judgment Sheet |
PJM will report the whole progress DVM will report the detail (Such as load test , time schedule) |
|
1-3 days before release |
Release Announcement (Option) |
PJM |
|
Announcement JIRA ticket |
Taiwan Service Decision Making MTG summit (Stop Maintenance or affect on taiwan services need to share) |
|
1-2 days | Release | DVM | PJM/PDM |
New function on Pro |
PJM to send srart and finished email ,and to lead the release. DVM to do release operation according to operation manual PDM to do confirm operation according to confirm manual |
10.Retrospect | ||||||
|
1 week after project release | PJM |
DVM PDM ENG TL |
Meeting minutes of retrospective Meeting | All project members to attend | |
|
2nd months after project release | KPI Monitoring(Option) | PDM |
|
IIPM report |
|
|
|
|
|
|
|
|
11.Post-deploy Phase | ||||||
|
Troubleshooting | PDM/ENG |
|
|
Process | Time | Responsibilities | Role | Participants |
Deliverable |
comment |
---|---|---|---|---|---|---|
0. Management | ||||||
|
Budget Management | PJM |
|
Cost Model |
|
|
|
Time Management (overall) | PJM |
|
Excel Schedule and WBS |
|
|
|
Time Management (detailed) |
|
|
PJM receives estimations for Due Dates and input into Project schedule |
|
|
|
Coordination with CWD (detailed) | PDM |
|
|
|
|
|
Coordination with BU | PDM | PJM | PDM: 分享季度開發計劃 |
|
|
1. Prepare Budget Application | ||||||
|
1st week at month of prepare budget application (case by case) |
Preliminary requirements discussion (初步需求討論會) |
PDM |
Team Leader Shiwei(Option) |
7. 確定PJM |
|
2nd week at month of prepare budget application | Functional Specification (detailed) | PDM |
Team Leader PJM |
Confluence document
|
|
|
|
3rd week at month of prepare budget application (case by case) |
prototype design discussion (原型討論會) |
PDM |
Team Leader |
1.工數的預估(給出哪些無法預估) 2.評估所需資源(infra、CWD等) |
1.講解需求UI的呈現及交互方式,討論、確定交互及UI呈現的可行性、合理性 |
|
|
|
|
|
|
|
|
4th week at month of prepare budget application (case by case) |
Draft MRD (初稿MRD討論會) |
PDM |
PJM DVM ENG |
The modifying part of draft MRD | 講解MRD(MRD PPT初稿),討論、確定MRD中描述的需求及範圍的準確性、合理性; |
|
4th week at month of prepare budget application (case by case) |
MRD fixed | PDM |
PJM DVM ENG |
Fixed MRD |
講解fixed MRD,最終確認MRD; 2. 確認有其他開發團隊參與,則需準備相應的英文資料,並約相關團隊進行MRD的講解。 |
2.Budget Application |
1-Budget Application | |||||
Month of budget application |
Send MRD (English version) to CWD | PDM |
|
Notice the month of budget application , to remain the resource. |
|
|
1st weeks at month of budget application |
Estimate Development Effort | DVM | ENG | Submit human cost and schedule to DVM |
|
|
|
1st weeks at month of budget application | Adjusting human resource | DVM |
|
Submit human cost and schedule to PJM |
|
|
1st weeks at month of budget application | Meeting with Infra member for infra Estimate |
PJM |
DVM ENG |
Meeting minutes from discussions with Infra Members (PDM introduce project, DVM Submit apply content) |
|
1st weeks at month of budget application | QA Estimate | PJM | PDM |
Supply budget to Admin for update of ROS. |
|
|
1st weeks at month of budget application | Security Audit Estimate | PJM | System Security Office |
Supply budget to Admin for update of ROS. |
|
|
1st weeks at month of budget application | Create Overall Schedule | PJM |
DVM PDM |
Excel Schedule |
|
|
1st weeks at month of budget application | Create Detailed Schedule (implementation) | DVM |
|
Detailed Schedule |
|
|
|
2nd weeks at month of budget application |
Explain of Schedule and Mandays |
PJM | DVM | Approved Schedule and Mandays |
DVM to report Mandays PJM to report Schedule |
Approved on Friday of 2nd weeks at month of budget application |
Business Case Creation and Approval |
PDM/PJM |
|
Project introduction PPT Mandays, Schedule, BudgetApplication, |
Taiwan Service Decision Making MTG summit and get approval PDM : Project introduction PPT (Function, KPI) PJM: BudgetApplication,Mandays, Schedule) |
|
|
2nd weeks at month of budget application | PMO Ticket | PJM |
|
Submit PMO ticket to SSP get approval |
|
|
3rd weeks at month of budget application |
Registration in EYES |
PJM |
|
Send Email to Japan PDM to support get EYES Code in EYES system. |
|
|
3rd weeks at month of budget application | Dezi Ticket | PJM |
|
Submit DEZI ticket to apply budget |
|
3. Project Start Phase | 0_Project Start | |||||
1st week before design stage |
Process Design (development process. select tools) | PJM |
|
Confluence documentation
|
reference: |
|
1st week before design stage |
Communication Management | PJM |
|
Confluence documentation |
reference: |
|
1st week before design stage |
Project Objectives | PJM |
|
Confluence documentation |
reference: |
|
1st week before design stage |
Education (project management training) | PJM |
|
|
reference: |
|
|
1-3 days before design stage |
Project start Meeting | PJM | DVM,PDM,ENG | All project members to attend (about MRD question, Schedule .etc) |
|
|
1-3 days before design stage | Create WBS | PJM |
|
WBS | Milestone (Task of each stage) |
|
1-3 days before design stage | Create Detailed WBS | DVM |
|
WBS (Design, development,ENG test,Release) | detailed task |
|
1-3 days before design stage | Create Detailed WBS | PDM |
|
WBS (PM test) | detailed task |
|
1st week before design stage |
UI Specification Meeting | PDM | CWD | UI Specification document |
|
|
case by case | UI Design Estimate according to UI Specification | CWD |
|
Estimated man-days and cost | PDM need to confirm with Taiwan |
|
case by case | Provide the Due date according to ENG' schedule | PDM |
|
Due date for providing HTML |
|
|
case by case | Provide CWD Schedule according to ENG's due date | CWD |
|
CWD Schedule |
|
|
|
|
|
|
|
|
4. Design and design review | ||||||
Design | 3-5 Days | Overall Architecture | DVM | ENG | Confluence documentation |
|
|
DB Schema Design | DVM | ENG | Confluence documentation |
|
|
|
Hardware Design | DVM | ENG | Apply to Infra and Confluence documentation |
|
|
|
Application Design (RMS/MALL) | DVM | ENG | Confluence documentation |
|
|
Design Review | 1-2 Days | Overall Architecture | Team Manager : ZhuShiwei | DVM | Approved documentation | Architecture Design and Program Design |
|
|
DB Schema Design | Team Leader | DVM,ENG | Approved documentation |
|
|
|
Hardware Design | Infra Members | DVM,ENG | Approved documentation |
|
|
|
Application Design (RMS/MALL) | Team Leader | DVM,ENG | Approved documentation |
|
|
Case by case | Create Mock-ups | CWD | PDM |
|
|
|
Case by case | Confirm Mock-ups | PDM |
|
Confirmed Mock-ups | PDM need to confirm with Taiwan |
|
Case by case | Create Design (Image Description) | CWD | PDM |
|
|
|
Case by case | Confirm Design (Image Description) | PDM |
|
Confirmed Design (Image Description) | PDM need to confirm with Taiwan |
|
Case by case | Create HTML page | CWD | PDM |
|
|
|
case by case |
Confirmed HTML page |
DVM/PDM | ENG | Confirmed HTML source file (確定設計原型) | PDM need to confirm with Taiwan |
|
|
|
|
|
|
|
Apply support | ASAP | Apply QA | PJM |
|
Apply JIRA ticket to QA |
|
|
ASAP | Apply Appscan | DVM |
|
Apply JIRA ticket to System Security Office |
|
|
ASAP | Apply Security Audit | DVM |
|
Apply JIRA ticket to System Security Office |
|
|
The last day of design stage | Design finished MTG (CDC) | DVM |
ENG PJM PDM(Option)
|
Confluence documentation(Architecture Design Document,Program Design Dcoument)
|
All project members to attend (Judge to whether can enter the next phase ) |
5.Development & Unit test | 3-Development | |||||
|
Case by case | Programing | DVM | ENG | Coding |
|
|
Case by case | Unit Test | DVM | ENG |
(Unit Test Code Coverrage(>=80%) |
|
|
3-5 days | Code Review | DVM | ENG | Code source |
|
6.DEV Test | ||||||
|
|
Prepare test case | DVM | ENG | Test case document |
|
|
|
DEV Release | DVM | ENG | n/a |
|
|
|
Dev Test | DVM | ENG | Problem tickets |
|
|
|
Bug Fix after Test | DVM | ENG | Fixed ticket |
|
|
1-2 days before dev test finished | DEV test result Demo MTG | DVM |
ENG PJM PDM(Option) |
Demonstrable function |
ENG demonstrate their own development efforts on DEV |
7.Internal STG Test | 4-Internal STG Test | |||||
|
2-5 days | Prepare Join Test Case | PDM |
|
Created test cases |
|
|
1 day | Test case review MTG | PDM |
DVM ENG PJM(Option) |
Meeting with DVM, and review the test case |
|
|
1 week or more | Prepare Load Test Case | DVM | ENG | DVM arraign Eng prepare Load test case document |
|
|
1 days | Load test case review | DVM |
|
review Load test case |
|
|
5 days |
INFRA (JP) Review Load test case |
DVM |
|
Need to INFRA (JP) Review Load test case |
|
|
case by case | Join Test (ENG) | DVM | ENG | DVM arraign Join Test by ENG |
|
|
1-2 days before Eng stg test finished | STG test result Demo MTG | DVM |
ENG PJM PDM |
ENG demonstrate their own development efforts on STG, PDM attend. |
|
|
case by case | Join Test (PDM) | PDM | ENG | Join Test Report | STG測試結束以後發出report說明STG階段結束 |
|
3-5 days | Load Test | DVM | ENG |
Load Test report |
DVM arraign Eng to do Load Test, and submit Load Test report to INFRA (JP) |
8.External STG Test | 5-External STG Test | |||||
|
1 weeks before QA test | QA Test case review | PDM/DVM |
|
QA test case docuement |
PDM review UI part, DVM review function part and flow part. |
|
case by case | QA Test | QA Team |
PDM DVM |
Problem tickets |
|
|
3-5 days | QA Test after bugfix | DVM | ENG | Fixed ticket | DVM arraign arraign to fix these tickets |
|
1-3 days | Appscan Test |
Executed by CDC (DVM) Executed by SSO |
|
Appscan Test report |
|
|
0 or 1 day | Appscan Test after bugfix | DVM | ENG | Fixed ticket | DVM arraign arraign to fix these tickets |
|
3 ~5 days | Security Audit Test | Executed by SSO |
|
Security Audit Test report |
|
|
0 or 2 days | Audit Test after bugfix | DVM | ENG | Fixed ticket | DVM arraign ENG to fix these tickets |
|
case by case | JV Test | JV | PDM/Eng | Fixed ticket | DVM arraign ENG to fix these tickets |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
9.Release |
Release |
Reference: Service Operation [Service Transit] Release & Service Test Work Flow |
||||
|
1-2 weeks before release | Merge code and Tag and test | DVM | ENG |
Merged code |
|
|
2 weeks before release | Prepare TimeSchedule and release manual | DVM | ENG |
TimeSchedule Operation manual |
|
|
2 weeks before release | Prepare Release confirm manual | PDM |
|
Confirm manual |
|
|
2 weeks before release | Release manual Review | DVM |
|
reviewed Release manual |
|
|
2 weeks before release | TimeSchedule Review meeting | DVM |
PDM ENG PJM |
TimeSchedule | Share TimeSchedule to all please release members |
|
2 weeks before release | Release Rehearsal | DVM/PDM | ENG | Confirmed TimeSchedule/Operation manual/Confirm manual | Release Rehearsal on STG |
|
2 weeks before release | Adjuest after Release Rehearsal | DVM | ENG | Fixed function or UI | Adjuest after Release Rehearsal on STG |
|
1-2 weeks before release | Release Plan Sharing on IIPM(Option) | PDM |
|
IIPM Report | Share Release Plan |
|
1 week before release | Release Judge meeting | PJM |
DVM PDM TM (Shiwei) SSP(Fumiyama) |
Judgment Sheet |
PJM will report the whole progress DVM will report the detail (Such as load test , time schedule) |
|
1-3 days before release |
Release Announcement (Option) |
PJM |
|
Announcement JIRA ticket |
Taiwan Service Decision Making MTG summit (Stop Maintenance or affect on taiwan services need to share) |
|
1-2 days | Release | DVM | PJM/PDM |
New function on Pro |
PJM to send srart and finished email ,and to lead the release. DVM to do release operation according to operation manual PDM to do confirm operation according to confirm manual |
10.Retrospect | ||||||
|
1 week after project release | PJM |
DVM PDM ENG TL |
Meeting minutes of retrospective Meeting | All project members to attend | |
|
2nd months after project release | KPI Monitoring(Option) | PDM |
|
IIPM report |
|
|
|
|
|
|
|
|
11.Post-deploy Phase | ||||||
|
Troubleshooting | PDM/ENG |
|