B.3 Chapter 3 Review

 < Day Day Up > 



  1. Why is the Project Objective Statement (POS) necessary?

    The POS states what work you are going to do (the scope), by when (the schedule), with how many or how much (the resources or cost). It provides clarity and focus for the project team.

  2. What is the Project Definition Document (PDD)?

    The PDD is a high-level summary of the project. It should document information in the following order: description, purpose, strategic alignment, completion criteria, project start, customers, dependencies, and hardware/software requirements.

  3. What is the purpose of a Flexibility Matrix?

    This matrix is used to help the team decide and prioritize the tradeoff between scope, schedule, and resources.

  4. Why should a Data Risk Analysis (DRA) be completed?

    The DRA will bring important data issues to light before they arise, and it can save the Core Team much time and effort in defending decisions after the fact.

  5. List five key components of a Technical Analysis Document (TAD).

    These components are Software Reengineering Assessment, Technology Analysis, Technical Risk Assessment, In-House Contractor Analysis, and Lease-Purchase Analysis.

  6. Who is responsible for the completion of the Technical Risk Analysis (TRA)?

    It is part of the Risk Officer’s responsibilities to ensure this TRA is completed.

  7. What is the High-Level Solution Document (HLSD)?

    The HLSD is an initial response from the Project Manager to the user’s problems and needs as presented in the User Requirements Document (URD). This document is not intended to describe the end solution or final product in great detail. It is meant only to provide a 40,000-foot view (hence the name high-level solution).

  8. When is a Request for Proposal (RFP) used?

    This document, used when asking third parties to provide possible assistance, is the official request from your organization to a vendor to submit a proposal stating how the vendor would satisfy the requirements of the URD and accomplish the objectives stated in the HLS.

  9. What basic elements should a funding package contain?

    The funding documentation should contain all of the documents needed in your organization to request capital and/or expense dollars for the project, such as an explanation of the costs to sustain current operations, any savings to be realized, a calculation of the Return on Investment (ROI) or Economic Value Added (EVA). It should include any project development costs for hardware, software, data formatting and/or conversion, and programming. Project implementation costs such as training, publications, rollout costs, costs of sustaining the product after delivery, maintenance fees, and support costs are included in the funding documents. Finally, the funding documents should disclose funds that have already been budgeted for this project. An appendix should contain any copies of outstanding and/or approved Capital Equipment Requests (CERs), Purchase Orders (POs), and vendor invoices (paid and unpaid) that have been received to date.

  10. Who manages the project budget and schedule?

    The Project Manager is responsible for managing the budget and schedule.

  11. What are dependency diagrams used for?

    They are used to display a visual representation of project dependencies.

  12. When are variance reports necessary?

    The reports should be compiled upon request of the Core Team or Project Sponsor, or at minimum, at the end of each of the eight SEP project phases.



 < Day Day Up > 



Managing Software Deliverables. A Software Development Management Methodology
Managing Software Deliverables: A Software Development Management Methodology
ISBN: 155558313X
EAN: 2147483647
Year: 2003
Pages: 226

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net