initial commit

This commit is contained in:
mlot
2026-01-15 10:27:39 -05:00
commit aa0d8c4df7
13 changed files with 269 additions and 0 deletions

7
Eisenhower_Matrix.md Normal file
View File

@@ -0,0 +1,7 @@
# Eisenhower Priority Matrix
Ref: [https://todoist.com/productivity-methods/eisenhower-matrix](https://todoist.com/productivity-methods/eisenhower-matrix)
| |URGENT |NOT URGENT |
|:---|---:|---:|
**IMPORTANT**|DO IT :`Immediate Deadlines`|SCHEDULE IT :`Future Deadlines` |
**NOT IMPORTANT**|DELEGATE IT :`You Are Not Required` |DELETE IT :`Distraction, No Real Value` |

9
LICENSE Normal file
View File

@@ -0,0 +1,9 @@
MIT License
Copyright (c) 2025 mlot
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

5
Milestone_Chart.md Normal file
View File

@@ -0,0 +1,5 @@
# Milestone Chart
| Milestone | Scheduled Completion | Actual Completion |
|-----------|----------------------|-------------------|
| | | |

View File

@@ -0,0 +1,13 @@
# Project Budget (Projected and Actual)
| Item | Projected Budget | Actual Expenditure |
|---------------------|----------------------|--------------------|
| Equipment | | |
| Consumables | | |
| External Staff | | |
| Internal Staff | | |
| Taxes | | |
| Expenses | | |
| Contingency/Risk | | |
| Management Reserves | | |
| **TOTALS** | | |

32
Project_Overview.md Normal file
View File

@@ -0,0 +1,32 @@
# Project Overview
## Defining the Project
- [ ] Study discuss and analyze
- [ ] Write a project definition/summary (*Project Summary*)
- [ ] Set an end-results objective
- [ ] List imperatives and deliverables
- [ ] Generate alternative strategies
- [ ] Evaluate alternatives
- [ ] Choose a course of action
## Planning the Project
- [ ] The Three Project Parameters: **Quality, Time, Cost** (*Risk Identification Chart*)
- [ ] Breakdown the project into logical steps or sub-units (*Project Planning Summary*)
- [ ] Determine the proper sequence for each step
- [ ] Determine time and cost for each step
- [ ] Determine standards for each step
- [ ] Determine resources needed, training required, staffing, and any policies or procedures
## Implementing the Project Plan
- [ ] Control the work in progress by monitoring and reviewing performance (*Milestone Chart*)
- [ ] Provide feedback
- [ ] Negotiate materials, supplies, and services
- [ ] Resolve differences and changes
## Completing the Project
- [ ] Check that the quality specifications of the project were met
- [ ] Evaluation review

View File

@@ -0,0 +1,5 @@
# Project Planning Summary
| Component or Step | Budget | Schedule | Responsibility |
|-------------------|--------|----------|----------------|
| | | | |

73
Project_Summary.md Normal file
View File

@@ -0,0 +1,73 @@
# Project Summary
**Customer:** [insert]
**Project name:** [insert]
**Project goal:** Define the high level goal of the project.
## Objectives:
- Break out the project goal into more specific objectives
- [insert]
- [insert]
## Constraints:
- Define contraints like budget, time, abilities, regulations, etc.
- [insert]
- [insert]
- [insert]
- [insert]
- [insert]
## Risks:
- Equipment delays [**SIGNIFICANT RISK**]
- Over budget [MODEST RISK]
- Use Significant or Modest as risk levels and bold Significant risks.
## Assumptions:
- List of assumptions outside the scope of the project.
- Example: Contractor will provide tools and materials
- [insert]
## Project Scope
## In Scope:
- Define actions within the scope of the project.
- [insert]
- [insert]
## Out of Scope:
- Define actions outside the scope of the project.
- [insert]
- [insert]
## Deliverables:
- Define specific completed deliverables by the end of the project.
- [insert]
- [insert]
## Tasks and Estimated Costs
| Task | Estimated Costs | Notes |
|------|-----------------|-------|
|ex. Furniture|$1,000| |
|Decorations|$250|*wall art*|
|**TOTAL**|**$1,250**|*estimated*|
## Closing Checklist
- [ ] All Deliverables Checked and Tested for Quality Requirements
- [ ] Deliver Documentation and/or Training (*If Required*)
- [ ] Get Customer/Management/Stakeholder Sign-Off
- [ ] Reassign Personnel, Dispose of Surplus Equipment/Materials, and Release Facilities
- [ ] Document Project (*Problems, Lessons Learned, Etc.*)
- [ ] Report Final Project Status and Outcome to Customer/Management/Stakeholders
- [ ] Declare Project Completed

21
README.md Normal file
View File

@@ -0,0 +1,21 @@
# "Barely Sufficient" Templates
Simple templates mainly written in Markdown for use in project management and documentation.
## Small to Medium Project Management Documents
* [Project Summary](https://tildeforge.dev/mlot/docTemplates/src/branch/main/Project_Summary.md) - Template for a project summary including goals, risks, estimated costs, and closing checklist.
* [Project Planning Summary](https://tildeforge.dev/mlot/docTemplates/src/branch/main/Project_Planning_Summary.md) - Plan each project component's budget, schedule, and responsibility.
* [Project Budget Template](https://tildeforge.dev/mlot/docTemplates/src/branch/main/Project_Budget_Template.md) - Project budget template for comparing projected and actual expenditures.
* [Milestone Chart](https://tildeforge.dev/mlot/docTemplates/src/branch/main/Milestone_Chart.md) - Keep track of project progress by monitoring each project milestone.
* [Risk Identification Chart](https://tildeforge.dev/mlot/docTemplates/src/branch/main/Risk_Identification_Chart.md) - Identify project risks and document possible mitigations to the project's quality, cost, and schedule.
* [Example Gantt Chart](https://tildeforge.dev/mlot/docTemplates/src/branch/main/gantt_chart.md) - Plan each project component based on a time schedule and dependency. (_Requires [Mermaid](https://mermaid.js.org/)_)
* [Eisenhower Priority Matrix](https://tildeforge.dev/mlot/docTemplates/src/branch/main/Eisenhower_Matrix.md) - Simple matrix for determining task priority.
## Small to Medium Agile Project Management Documents
* [Kanban Template](https://tildeforge.dev/mlot/docTemplates/src/branch/main/kanbanTemplate.md) - Basic 4 column [Kanban](https://kanbanblog.com/explained/) style template for light project and to-do list managment.
## Documentation
* [Instructions Template](https://tildeforge.dev/mlot/docTemplates/src/branch/main/instructDocTemp.md) - Simple step-by-step or checklist based instructions template. (_Optional [Mermaid](https://mermaid.js.org/)_)
* [Standard Operating Procedure Template](https://tildeforge.dev/mlot/docTemplates/src/branch/main/SOP_Template.md) - Multiuse standard operating procedure (SOP) template for documenting organizational processes.
## Checklists
* [Project Overview](https://tildeforge.dev/mlot/docTemplates/src/branch/main/Project_Overview.md) - High level project overview checklist.

View File

@@ -0,0 +1,7 @@
# Risk Identification Chart
| Control Element | What is likely to go wrong? | How and when will I know? | What will I do about it? |
|-----------------|-----------------------------|---------------------------|--------------------------|
| Quality | | | |
| Cost | | | |
| Timeliness | | | |

35
SOP_Template.md Normal file
View File

@@ -0,0 +1,35 @@
# **How to SOP Template**
# **Purpose**
---
Insert the high level specific purpose (*or outcome*) of this SOP (*standard operating procedure*) here.
# **Procedure**
---
Note: Place the sequenced high-level steps for the procedure. Focus on the outcome. Keep the steps to eight (8) or less. Add brief notes, links, or FAQs for more details. Bold the step number text.
- [ ] **Step 1:** This is step 1
- [ ] **Step 2:** This is step 2
- [ ] **Step 3:** This is step 3
- [ ] **Step 4:** This is step 4
- [ ] **Step 5:** This is step 5
- [ ] **Step 6:** This is step 6
- [ ] **Step 7:** This is step 7
- [ ] **Step 8**: This is step 8
# **FAQs**
---
Note: Place frequently asked questions about the procedure with answers here for additional information. Bold the question portion.
**Q: Why do we need FAQs?**
A: Because they are helpful.
**Q: Is there credit due for this template?**
A: Team ProcessDriven. 2024. “SOP Examples - ProcessDriven.” ProcessDriven. August 30, 2024. [https://processdriven.co/sops/](https://processdriven.co/sops/).

19
gantt_chart.md Normal file
View File

@@ -0,0 +1,19 @@
```mermaid
gantt
dateFormat MM-DD
title Example Gantt Chart
section Office Furniture
Research New Furniture :done, 05-09, 3d
Order and Purchase Furniture :crit, 05-18, 1d
Furniture Delivered to Office : a1, 06-06, 2d
Distribute Furniture :a2, after a1, 5d
Treat Furniture with Scotchgard :after a2, 3d
section Computer Upgrades
Research New Computers :done, 05-09, 3d
Order and Purchase Computers :crit, 05-18, 1d
Computers Delivered to Office : a1, 06-06, 2d
Install Computers :a2, after a1, 3d
Image and Update Computers :after a2, 5d
```

38
instructDocTemp.md Normal file
View File

@@ -0,0 +1,38 @@
# Document Title
The document title should focus on the general content of the document. For example: "Creating User Accounts in LDAP". Provide a summary of the overall document content just after the title.
## Document Section
The document should be broken up into logical sections. Each section should then contain step-by-step or checklist instructions.
For example, one section may be called "Adding a New User"
### Step-By-Step or Checklist Subsection
Each section should contain step-by-step instructions and/or a checklist of how to perform each action under the appropriate section. Include examples and images as needed.
1. Verify user names meet convention requirements *(1)*.
2. From the command prompt, add the user to Ubuntu OpenLDAP Server:
`sudo ldapadduser eggsham domainname`
* [ ] User added to Ubuntu OpenLDAP Server
Add visual aids if necessary.
```mermaid
flowchart LR
A["Nightly Scheduled Task at 5:30am"] --> B{Test for New Input Files};
B ---->|"Input Files Do NOT Exist"| E[End];
B -->|"Input Files Exist"| C{"Import Data from Files"};
C ---->|"No New Data"| D["Email and End"];
C ---->|"New Data"| F["Create Accounts and Email"];
```
## Reference
The reference area should be used to add any additional information or instructions on how to deal with more specific circumstances, and/or to reference any external sources of information.
(1) **Section Title: Subtitle** - Do not include hyphens (-) in user account names.
“LDAP Workstation Authentication.” n.d. Ubuntu. Accessed March 16, 2023. https://ubuntu.com/server/docs/service-ldap-usage.

5
kanbanTemplate.md Normal file
View File

@@ -0,0 +1,5 @@
|BACKLOG |TO-DO |IN-PROGRESS |COMPLETED |
|---------|---------|-------------------|----------------|
|backlog | | |completed |
| | |in-progress | |
| |to-do | | |