![]() They will be updated throughout the project. These documents represent a set of continuously evolving documents. Backlog (see, agile project artifacts are relevant too).This category relates to the various project management logs and registers we have as part of the daily management of the process. Note: you’ll use these artifacts for project management across all the three performance domains. Still, in principle, this category relates to the high level strategy stuff on the project and isn’t something you’d need to update often once it’s done. Having said that, I’ve worked on projects where they have changed, because a lot depends on how the project evolves, and you know something is always going to be different. These documents are developed at the start of project and don’t normally change. ![]() The first category is documentation that relates to strategy and project initiation. OK, let’s get to it: here’s the list of project management artifacts. The authors of the Seventh Edition are keen for there to be no duplication and for the approach to be simple! For example, an estimate is the obvious output of the estimating process, so estimates aren’t mentioned again as a separate project artifact. Industry-specific artifacts are not mentioned either, so if you work in a highly regulated field then some of the standard documents you’d expect to produce might be missing.Īlso, if the artifact is the result of some other project management method or tactic, it won’t be mentioned here. You’ll see that for each category, some of the really obvious stuff is not called out because it’s generic or obviously required for management purposes. Let’s look at each of those in more detail. Other – a bucket category for anything else.And yes, agile project management artifacts get a mention. Whether you subscribe to the PMI way of thinking or use another approach based on your background, skills, experience, certification or the expectations of management, I’m pretty sure that you’ll have to create project documents.Īlthough this list draws on PMI materials, it’s still going to be useful to you even if you use a different approach. 12:03 am GMT But what if you don’t use PMI methods?ĭocuments are documents. Artifacts in the PMBOK Guide – Seventh EditionĪrtifacts are categorized in the PMBOK® Guide – Seventh edition into 9 different types and that’s what this article is going to look at. In all cases, artifacts relate to the work of managing the project, not the thing you are creating as the output of the project.įor example: a project management artifact is the project closure document. Mostly, the term refers to the project documentation you produce that defines and supports the work you are doing. In project management, artifacts relate to documents, templates, outputs or a specific deliverable. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |