Your company spends millions on purchasing, installing, implementing, and upgrading a PeopleSoft ERP package, yet when the people involved in the project leave the company or the project and move on, does all of the information and knowledge walk out the door with them? I can't tell you how many times I have walked onto a client's site to work on a specific project or even a single program that needs to be enhanced, just to discover that no one knows what it does, or why it was created. So, I do the next thing that any good PeopleSoft pro would do. I ask for the associated documentation such as the requirements, functional specs, technical specs, etc.. Like a deer in headlights, they look at me then tell me they don't have any documentation. As a result, the developer has to spend a lot of time researching and analyzing the program, and having discussions and meetings with many of the functional users. We all know this happens too often. Let's face it, a written PeopleSoft technical document leaves much less to chance than an over- the-shoulder conversation between two people in a |
| A document can be saved, retrieved, published, circulated, discussed, consulted, and archived. Documents can take the form of specifications, procedures, memoranda, histories, or letters of complaint.
Well, here is a great resource where you can get a ton of docment templates that will help you prepare your PeopleSoft technical documents faster, save time on formatting, provide a consistent standard across your publications, and ensure that your company delivers professionally looking documents. Here are the types of document templates you can instantly download. |
© 2012 Created by PSoftPros.

You need to be a member of PSoftPros to add comments!
Join PSoftPros