The first characteristic we’d like to discuss around projects is connected to the project itself. We've talked about the people, processes, systems, and now projects. From this perspective, one of the most important aspects or characteristics of a successful implementation has to do with the deliverables. When I say deliverables, those are the work products that are reviewed and approved formally by the project team. Those deliverables will range in design documentation, configuration documentation, test grips, and test results.
An organization can decide on which of those particular components are formal deliverables. But the quality and quantity of deliverables allowed is up to the dedication of their team to the project. I can say for myself that if I'm required to sign or approve a document, I look at it more carefully and am engaged in that document. It also helps when you have design document deliverables, which I’ll focus on later in this series.
You have the right people review, acknowledge, and approve that document, then there's a level of accountability and responsibility to making sure that deliverable is correct and represents what they're trying to accomplish. So having the right amount of deliverables, having the right approval of those deliverables for a project are very important, as are the processes all around that. That way it's very clear who is responsible for what and who is going to be signing these. Again, it leads back to the importance of that accountability.