Other

项目介绍

jerzydziewierz/PMBOK-doc-templates 是一个托管在 GitHub 上的开源项目,主要使用 CSS 编写,采用 Other 许可证,目前获得 25 个 Star、5 次 Fork。

仓库全名
jerzydziewierz/PMBOK-doc-templates
开源许可证
Other
Star 数
25
Fork 数
5

README 摘要

Migrated to: https://codeberg.org/greycodes/PMBOK-doc-templates PMBOK document templates Linked document structure for project management as described in the PMI PMBOK Guide 6th ed. Plans, Documents, Processes, Tools and Techniques e.t.c - in markdown. About This repository provides easy to edit templates for starting a project documentation using the project management method from the PMI PMBOK Guide 6.0…

完整内容见 GitHub 原始 README 或本页 。

常见问题

PMBOK-doc-templates 用什么语言开发?

主要使用 CSS 编写,采用 Other 许可证,目前有 25 个 Star。

PMBOK-doc-templates 可以免费商用吗?

仓库标注的许可证为 Other,商用前请先阅读仓库 LICENSE 文件确认授权范围。

如何获取 PMBOK-doc-templates 的源码?

可以直接克隆仓库:git clone https://github.com/jerzydziewierz/PMBOK-doc-templates.git;安装与运行步骤见仓库 README。

PMBOK-doc-templates 最近还在维护吗?

仓库最近一次更新为 3月12日,当前没有未关闭的 Issue;Star 数为 25,可作为社区活跃度的参考。

关于

Linked document structure for PMBOK 6th ed. documents, plans, processes, e.t.c in in markdown

描述取自 GitHub 官方 API,中文内容由 GitRead 中文社区 编辑团队整理。

简要分析

热度分
60
价值分
19
活跃状态
归档

语言占比

CSS

Release

README

Migrated to: https://codeberg.org/greycodes/PMBOK-doc-templates

PMBOK document templates

Linked document structure for project management as described in the PMI PMBOK Guide 6th ed.
Plans, Documents, Processes, Tools and Techniques e.t.c - in markdown.


About

This repository provides easy to edit templates for starting a project documentation using the project management method from the PMI PMBOK Guide 6.0.

Importantly, the documents are organized by linking to them from their respective processes. Hence, you can go to a process and see and jump to project documents that are relevant to that process. This way, you will not miss the documents that one should consult or update while going through the project life cycle.

Obviously, for any specific project, it is not neccessary to use all of the documents.

There are separate folders with:

  • Business Documents - 2 templates. These serve mostly as placeholders for documents that should come from outside.
  • Processes - list of all the processes in Integration, Scope, Schedule, Cost, Quality, Resources, Communications, Risk, Procurement and stakeholder management. These serve as navigation aid.
  • Project management plans - 14+6 templates. These are documents that you edit to do method tailoring.
  • Project Documents (in the PMBOK sense) - 36 templates. These are the documents to edit during your project, that serve as the project documentation.

The root folder contains the the super-documents:

To start off the navigation, I include:

  • Linear list of processes sorted by knowledge area (Integration, scope, e.t.c.)
  • Linear list of processes listed by process group (Initiation, planning, execution, monitoring, closing)

You will find that most (editable) documents are nearly empty or a bare stub. This is intended - these documents are supposed to be starting points for project instance notes, and not a recreation of the PMBOK Guide. Some documents include references to the PMBOK for further explanation.

Depending on the project size, you might find that merging some documents into one bigger file is appropriate (tailoring). Likewise, if your project is bigger, you might need additional folders, or that a specialized tool might be better for you.


How to use this

  1. Copy the files to your own machine (download as a zip file or use git clone [email protected]:jerzydziewierz/PMBOK-doc-templates.git )
  2. Make a new folder, “project document templates” folder in your project documents repository, and copy these templates again
  3. Edit and fill the documents as needed. Remove everything that is not needed. Going with the spirit of PMBOK Guide, you can and should choose which headlines to use, and also rename them as needed. The only thing that PMBOK stipulates is that, when starting a new project, you should at least review & consider all these categories of problems. See the Tailoring explainer , or Tailoring whitepaper
  4. (obsolete) If desired, use typobs to move between Typora or Obsidian linking styles.

You can use e.g. https://obsidian.md/ to keep these as a common, linked system.


Here’s a link to the Change log


Created using https://obsidian.md/ - and https://typora.io/ where applicable.

I have used typobs to convert between typora and obsidian link styles.

The intention is to keep it compatible with https://spec.commonmark.org/current/

Disclamer:

This is not a part of the PMBOK guide, nor a reproduction. These document stubs are an original freeware side material.

License: Modified Apache 2.0, see the full text license here

评论

暂无评论