Here’s a non-exhaustive list of the types of visual data you might have on your projects: This is a catch-all category for anything that’s not a written document in the traditional sense. Here are some examples:īaselines will be created and updated as the project progresses and as major changes happen. They represent approved versions of whatever plan they relate to. We create baselines throughout the project. Typically, these are progressively elaborated as you go through the project, so you can come back to them and edit/update as required. The upper levels encompass all the information covered by the lower levels. You might not need all of these and you might have various versions of each of them.īasically, they show high level info that is decomposed into detailed sections. These describe the relationships between various parts of the project. I can see that being particularly relevant for things like a release plan. a bunch of words, but you could have visual plans if it makes sense to use diagrams to show the flow of work. Typically, they are written out documents i.e. They are developed to help you work out how to run the project and can either be all in one document or separate documents. The third category of project artifact relates to the different types of plans produced. Who cares? As long as you know what you are talking about, you can use either, or both interchangeably. 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. 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.
0 Comments
Leave a Reply. |