nok/wms-app
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(sdlc): close training and operational actions

Browse Source
This commit is contained in:
Thanakorn
2026-08-26 13:10:06 +07:00
parent 5d93e87771
commit c4d3c6ea9e
9 changed files with 55 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files
sdlc/1-PM Process (10 Work Product)/2.Project Plan/1-Work Schedule/200-WMS-26-001-00 Work Schedule 25690817 V1.0 Final.md
+3 -3
View File
@@ -16,9 +16,9 @@
| Version | Date | Change | Prepared by |
|---|---|---|---|
| V1.0 | 17/08/26 | Initial controlled issue. Records the 05/01/26 schedule baseline and actual outcomes through product acceptance; administrative handover and training continue through project closure on 24/08/26. | Apirach Supattaratpateep |
| V1.0 | 17/08/26 | Initial controlled issue, subsequently updated with closure outcomes through 24/08/26: training, operational controls, delivery packaging, and repository-backup synchronization completed. | Apirach Supattaratpateep |
The Status, Actual/evidence date and Remarks columns below record outcomes as at 17/08/26. The Start, Finish and Duration columns retain the 05/01/26 planned baseline; where a task finished after its planned Finish date, the Remarks column states the actual finish.
The Status, Actual/evidence date and Remarks columns below record outcomes through formal closure on 24/08/26. The Start, Finish and Duration columns retain the 05/01/26 planned baseline; where a task finished after its planned Finish date, the Remarks column states the actual finish.
## Schedule basis
@@ -48,7 +48,7 @@ The Status, Actual/evidence date and Remarks columns below record outcomes as at
| 4.6 | Stabilization | Configuration and login corrections | Correct login and environment configuration issues identified after baseline. | Developer | 03/08/26 | 03/08/26 | 1 day | Configuration and login correction | Completed |
| 4.7 | Stabilization | Prepare demonstration data | Populate controlled demonstration data for validation and handover support. | Developer / Tester | 14/08/26 | 14/08/26 | 1 day | Demonstration data | Completed |
| 5.1 | Closure | Final repository and work-product review | Confirm required work products, traceability, configuration items, and unresolved actions. | Project Manager / Document Control | 10/08/26 | 24/08/26 | 15 days | Repository review and List of Evidence | Completed | Round 2 independent verification performed by Document Control on 17/08/26 |
| 5.2 | Closure | Acceptance and project closure | Obtain authorized acceptance and record project closure and follow-up actions. | Project Sponsor / Project Manager | 14/08/26 | 24/08/26 | 11 days | Acceptance Report and closure record | In progress | Product acceptance and authorization completed 17/08/26; administrative handover and training continue through 24/08/26 |
| 5.2 | Closure | Acceptance and project closure | Obtain authorized acceptance and record project closure and follow-up actions. | Project Sponsor / Project Manager | 14/08/26 | 24/08/26 | 11 days | Acceptance Report, Training Report, operational-control closure, and repository-backup record | Completed | Product accepted 17/08/26; training completed 22/08/26; operational controls closed 23/08/26; administrative and repository-backup closure completed 24/08/26 |
## Milestones
sdlc/1-PM Process (10 Work Product)/2.Project Plan/2-Software Project Plan/200-WMS-26-001-00 Software Project Plan 25690817 V1.0 Final.md
+1 -1
View File
@@ -386,7 +386,7 @@ Documents created for BRN WMS are released directly at `V1.0` once content is co
- Documents identify title, date, version, status, preparer, reviewer, and approver as applicable.
- Drafts remain distinguishable from approved baselines.
- The Project Repository contains the current controlled work products and supporting evidence (work product 9).
- The repository backup is maintained separately and checked during project closure (work product 10); the baseline and restoration checks were performed manually by the Developer (BK-001 and BK-002 closed), package completeness is recorded by BK-003, and final SDLC delivery-branch synchronization is tracked by BK-004 through 24/08/26.
- The repository backup is maintained separately and checked during project closure (work product 10); BK-001–BK-004 are closed, including restoration, complete delivery packaging, and synchronization and retrieval verification of the final `sdlc` branch and release tag on 24/08/26.
- Superseded records are retained or archived according to organizational control practices.
## 17. Acceptance and closure