3/29/2021 0 Comments Ssis Standards Documentation
Discover everything Scribd has to offer, including books and audiobooks from major publishers.
Ssis Standards Documentation Full Description SaveSSIS Standards Uploaded by manjunathalg 100 (4) 100 found this document useful (4 votes) 1K views 11 pages Document Information click to expand document information Date uploaded Dec 05, 2010 Copyright Attribution Non-Commercial (BY-NC) Available Formats PDF, TXT or read online from Scribd Share this document Share or Embed Document Sharing Options Share on Facebook, opens a new window Facebook Share on Twitter, opens a new window Twitter Share on LinkedIn, opens a new window LinkedIn Share with Email, opens mail client Email Copy Text Copy Link Did you find this document useful 100 100 found this document useful, Mark this document as useful 0 0 found this document not useful, Mark this document as not useful Is this content inappropriate Report this Document Download Now Save Save SSIS Standards For Later 100 (4) 100 found this document useful (4 votes) 1K views 11 pages SSIS Standards Uploaded by manjunathalg Description: Full description Save Save SSIS Standards For Later 100 100 found this document useful, Mark this document as useful 0 0 found this document not useful, Mark this document as not useful Embed Share Print Download Now Jump to Page You are on page 1 of 11 Search inside document.Browse Books Site Directory Site Language: English Change Language English Change Language.Figure 1 shows that even though documentation of Risk, for example, is more critical during the Initiation and Execution Phases, each knowledge area has a 1:1 mapping to critical documentation during the three project phases. Pop Quiz. Lets see if you remember anything from my little treatise.
How to cite this article: Petko, M. G. (1996). Documentation, documentation, documentation. Petko, PMP The Three Most Important Requirements of Good Project Management As an executive, you realize the importance of tracking and monitoring your work and the work of your subordinates. ![]() How does one ensure a smooth process in dealing with these changes Michael Petko provides an insightful solution. As he makes his case for documentation and its fundamental import, pay special attention to his mapping to A Guide to the Project Management Body of Knowledge. Then, see for yourself if you cant figure out a simple and time-honored solution to those seemingly never-ending client changes. Joan Knutson, Feature Editor It has often been said that the three most important considerations in selecting a good place to live are location, location, and location. Based on my experience, an analogy in project management is that to complete a successful project, the most important requirements are documentation, documentation, and documentation. Lets walk through a typical project to see how critical is this need for careful and effective documentation by the project manager and also see the relationship of documentation to the PMBOK Guides nine knowledge areas. Initiation Phase Most projects are organized around an initial scope, budget, and schedule. Depending on such variables as size of project, client relationship, and commercial terms, the degree of documentation of these initial parameters may vary from a few paragraphs to several volumes of text. Even on the smallest or simplest project, however, it is critical to take the time to write down and communicate what the planned deliverables are, when they will be delivered and what their cost will be. Ssis Standards Documentation Professional Situation OfHearing a client say, Thats not what I expected not only violates the basic guidelines of good quality management, but also puts you in the unpleasant professional situation of explaining this serious misunderstanding to your client. In this litigious world we live in, careful documentation of the agreement or contract will also pay dividends later if the dreaded dispute should arise. Execution Phase After the euphoria and newness has worn off, and during the execution phase of the project, its time for the project manager to earn those high dollars that were all paid Here is where it is absolutely critical to project success to document to the client, in a timely fashion, any changes to scope, budget, schedule, or quality requirements. This documentation takes many forms, from the construction field change order to a simple letter or note, but it must be written (electronic communication with reliable delivery is fine) and it must be timely. The change notification should also include the capacity to document the clients response to your communication. Figure 1. Project Phases and the Nine Knowledge Areas of the PMBOK This documentation process during the heat of battle is sometimes postponed or forgotten because of schedule pressures to just move ahead and to postpone dealing with confirmation of the change. The concept of advising the client that a change is taking place and the potential impact of that change, all in a timely and appropriate manner, is fundamental to successful project management. Completion Phase Completion of the paperwork required to gain closure on project issues and determine outstanding problems that can delay close-out is difficult for some project managers. However, if not dealt with in an organized fashion, completing the project can be both costlyif final payments are withheldand time consuming. Close-out activities are usually included in the project schedule, but one technique of documentation used most effectively at this time is a close-out checklist or punchlist. Preparation of this punch-list and buy-in from all interested parties will give needed organization to these often diverse and unrelated activities. Once in place, this close-out documentation will allow the project manager to manage the final activities on the old project and move on to the excitement and allure of the next project. ![]() Figure 1 shows that even though documentation of Risk, for example, is more critical during the Initiation and Execution Phases, each knowledge area has a 1:1 mapping to critical documentation during the three project phases. Pop Quiz. Lets see if you remember anything from my little treatise.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |