Looking at the lifecycle of a project, is there a industry standard (not specific to only project management) or a set of best practices of the artifacts that should be created as part of a project?

I am looking at this from the perspective of key stakeholders e.g. business analysts, architects, project managers, operations, support, etc.

For example, from an architectural perspective, this could include conceptual design, high level designs, detailed designs as well as technical designs such as infrastructure, networks, software and the like. These would move through the stages of inception, feasibility, build, deploy and support.

I am hoping to create a checklist of sorts. Since the organization i work is still in the infancy stages from a maturity perspective (although it is an entity that has been around 20 years), there isn't either the skill, the ownership or incentive, i am taking to take this on myself.

As for my role, i sit across the enterprise architecture practice and am looking at ways to elevate core practices that drive standards and improved practices & processes.


To add to Tobias' question, this is for the purposes of the transportation vertical

  • There are a lot of standards out there, depending on national law, industry, profession, and customer. E.g. PMBOK for PM or DO-178 for aerospace SW development. Could you add those details? – Tob May 9 '15 at 4:35
  • @Tobias - Thanks Tobias. I have added the details for the industry this is relevant to. Do these standards encompass stakeholders such as business analysts, architects, etc? – Motivated May 9 '15 at 6:36
  • The PMBOK is not for technical documents but for PM artifacts. The DO-178 describes the development process and the required artifacts. I guess most standards describe artifacts but not the responsibility within the organization to create them. Nevertheless, it shouldn't be so hard to perform a matching, for e.g. Requirements Management Plan, System Architecture or Test Procedure... – Tob May 9 '15 at 11:21
  • @Tobias - Thanks Tobias. I am attempting to look for something that is cross functional i.e. across project management, architecture, business analysis, etc. Is there a standard or set of practices that cover these? – Motivated May 10 '15 at 6:38
  • Have a look on the V-Modell, I posted in my answer. It is cross functional and tries to cover all system engineering aspects incl. PM. – Tob May 10 '15 at 6:49

I know nothing from transportation vertical industry, but regarding something industry independent and applicable for HW, SW, and embedded systems, the V-Model could be something to start with: http://en.m.wikipedia.org/wiki/V-Model.

Here is a link to the complete description in English: ftp://ftp.heise.de/pub/ix/ix_listings/projektmanagement/vmodell/V-Modell-XT-Gesamt-Englisch-V1.3.pdf

Be aware that as more general you are searching, as more general will be the described processes or artifacts. If you continue to focus, you'll find more concrete answers.

E.g. Regarding software development, you'll find really nice templates when you look for MIL-STD 498 (which is outdated).

  • Do you have any information about the use of v-models in architecture? The examples i have come across are predominantly software development led as well as testing. – Motivated May 14 '15 at 7:58
  • Sorry, nothing I know about. It's main propose is for systems and software engineering. But I would bet the principles can be adopted to all engineering related professions. – Tob May 14 '15 at 9:24
  • Thanks Tobias. When i meant architecture, i was referring to enterprise and solution architecture. – Motivated May 14 '15 at 17:46
  • Within the above linked document it is statet, that the V-Model is independent of the organizational structure due to the introduction of roles. I would say, you have to tailor the V-Model to your requirements / projects. Doing this, you'll find some roles more important than others. Finally you might be able to derive an enterprise architecture supporting the surving roles best. – Tob May 14 '15 at 18:50
  • v-modell.iabg.de/dmdocuments/… : this link is not valid anymore. Can you please share an updated one? Secondly, what are the artefacts expected as an output in each phase? – raikumardipak Sep 15 '18 at 6:16

Maybe these links would be of some help:

The below link is an excellent place to decide what documents you would need for an agile process or a quick prototype development:

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.