Add Pretty Table project: plan, accepted documents and code
Business Case, Stakeholder Analysis, Project Plan and milestone MIL-001 with review records RC-001 to RC-003, then the Python project: PrettyTable Pokemon table, constants, pytest tests, pyproject.toml, Doxyfile, CI workflow and README. Task: MIL-001#1 Task: MIL-001#2 Task: MIL-001#3 Task: MIL-001#4 Task: MIL-001#5 Task: MIL-001#6 Task: MIL-001#7 Task: MIL-001#8
This commit is contained in:
@@ -0,0 +1,60 @@
|
||||
# @TITLE@
|
||||
|
||||
## Metadata
|
||||
| Key | Value |
|
||||
| --- | --- |
|
||||
| ID | @ID@ |
|
||||
| CrossReference | @CROSSREF@ |
|
||||
|
||||
## Version History
|
||||
| Date | Status | Author | Reviewer | Change | Commit |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| @DATE@ | Proposed | @AUTHOR@ | <reviewer S-ID> | Initial version | pending |
|
||||
|
||||
---
|
||||
|
||||
## Purpose
|
||||
|
||||
<What the training achieves and the risk it mitigates.>
|
||||
|
||||
## Audience and Prerequisites
|
||||
|
||||
<Who attends, what they must have read or installed.>
|
||||
|
||||
## Learning Objectives
|
||||
|
||||
By the end, a participant can:
|
||||
|
||||
- <objective>
|
||||
|
||||
## Agenda
|
||||
|
||||
| Module | Topic | Minutes |
|
||||
| --- | --- | --- |
|
||||
| 1 | <topic> | <n> |
|
||||
|
||||
## Module Notes
|
||||
|
||||
### Module 1: <topic>
|
||||
|
||||
<Key points and what the facilitator shows.>
|
||||
|
||||
## Exercises
|
||||
|
||||
### Exercise 1: <name>
|
||||
|
||||
<Task, input and expected result.>
|
||||
|
||||
## Assessment
|
||||
|
||||
<How the facilitator checks each participant, and the pass criteria.>
|
||||
|
||||
## Session Record
|
||||
|
||||
What is recorded after each session, in the project (never in the framework):
|
||||
date, facilitator, attendees, result against the assessment, feedback and
|
||||
follow-ups.
|
||||
|
||||
---
|
||||
|
||||
@LINKS@
|
||||
Reference in New Issue
Block a user