Glossary For Project
Páginas: 20 (4947 palabras)
Publicado: 14 de enero de 2013
Expert Reference Series of White Papers
A Business Analyst’s Glossary for Project Management Terminology
1-800-COURSES www.globalknowledge.com
A Business Analyst’s Glossary for Project Management Terminology
Introduction
Project management has been increasing in visibility both inside and outside the executive office. Now, with the emergence of business analysis as an independent field,understanding and using the correct terminology is more critical than ever. This glossary is a guide to the most commonly used business analysis and project management terms. It is designed to help you better communicate with business analysis and project management professionals.
Glossary of Terms
3-Pass approach: method of finding the critical path by working through calculations on thenetwork three times: forward; backward; and once again to calculate the activity and network flexibility (float). Acceptance: one of four possible strategies for response planning with regard to an identified risk; indicates the impact of the risk that can be tolerated at its identified level. Active/visible observation: observing in a way that interacts with those being observed (ie, askingquestions and having others describe what they are doing and why). Activity: component of work performed during the course of a project; also called a task. Activity diagram: dynamic modeling technique used to show activities and decision points, and the roles assigned to them. Administrative closure: the activities of the project team necessary to collect project records, analyze project success orfailure, gather lessons learned, and archive project information for future use; performed when a project ends, when a project is terminated before work is complete, or at the end of each project phase. Administrative closure process: includes perform product verification, complete final project performance reporting, obtain formal acceptance of project, perform lessons learned, create projectarchives, release resources, and celebrate! Application architect: responsible for reviewing the requirements for feasibility and using them as a guide in developing the system architecture.
Copyright ©2007 Global Knowledge Training LLC All rights reserved.
Page 2
Application architecture: part of the enterprise architecture that shows how the various software applications interact. Assumptions:things considered real, true, and certain for the purposes of planning; factor believed to be true but not confirmable or factor known to be true but that could change during the project. Avoidance/elimination: one of four possible strategies for response planning with regard to an identified risk; indicates that risk cannot be tolerated to any degree and must be prevented from having any impacton the project. BABOK: Abbreviation for IIBA’s Business Analysis Body Of Knowledge. Backward pass: method of determining the late start time (LST) and late finish time (LFT) for each activity. Baseline: project’s point of reference for requirements changes; established at the point of plan approval and should not be changed except in response to significant, approved change in the project scope.Black box reverse engineering: deduces the system’s requirements from its behavior, without examining its code or other technical details. BOSSCARD Framework: acronym for remembering project definition elements: Background; Objectives; Scope; Stakeholders; Constraints; Assumptions; Reporting; and Deliverables. Brainstorming: requirement elicitation method that generates creative ideas among a groupof people; success is dependent on participants’ creativity. Business Analyst (BA): a person who identifies the business needs of clients and stakeholders to determine solutions to problems; responsible for requirements development and management; acts as a bridge between the client, stakeholders, and the solution team. Business architecture: part of the enterprise architecture that shows the...
A Business Analyst’s Glossary for Project Management Terminology
1-800-COURSES www.globalknowledge.com
A Business Analyst’s Glossary for Project Management Terminology
Introduction
Project management has been increasing in visibility both inside and outside the executive office. Now, with the emergence of business analysis as an independent field,understanding and using the correct terminology is more critical than ever. This glossary is a guide to the most commonly used business analysis and project management terms. It is designed to help you better communicate with business analysis and project management professionals.
Glossary of Terms
3-Pass approach: method of finding the critical path by working through calculations on thenetwork three times: forward; backward; and once again to calculate the activity and network flexibility (float). Acceptance: one of four possible strategies for response planning with regard to an identified risk; indicates the impact of the risk that can be tolerated at its identified level. Active/visible observation: observing in a way that interacts with those being observed (ie, askingquestions and having others describe what they are doing and why). Activity: component of work performed during the course of a project; also called a task. Activity diagram: dynamic modeling technique used to show activities and decision points, and the roles assigned to them. Administrative closure: the activities of the project team necessary to collect project records, analyze project success orfailure, gather lessons learned, and archive project information for future use; performed when a project ends, when a project is terminated before work is complete, or at the end of each project phase. Administrative closure process: includes perform product verification, complete final project performance reporting, obtain formal acceptance of project, perform lessons learned, create projectarchives, release resources, and celebrate! Application architect: responsible for reviewing the requirements for feasibility and using them as a guide in developing the system architecture.
Copyright ©2007 Global Knowledge Training LLC All rights reserved.
Page 2
Application architecture: part of the enterprise architecture that shows how the various software applications interact. Assumptions:things considered real, true, and certain for the purposes of planning; factor believed to be true but not confirmable or factor known to be true but that could change during the project. Avoidance/elimination: one of four possible strategies for response planning with regard to an identified risk; indicates that risk cannot be tolerated to any degree and must be prevented from having any impacton the project. BABOK: Abbreviation for IIBA’s Business Analysis Body Of Knowledge. Backward pass: method of determining the late start time (LST) and late finish time (LFT) for each activity. Baseline: project’s point of reference for requirements changes; established at the point of plan approval and should not be changed except in response to significant, approved change in the project scope.Black box reverse engineering: deduces the system’s requirements from its behavior, without examining its code or other technical details. BOSSCARD Framework: acronym for remembering project definition elements: Background; Objectives; Scope; Stakeholders; Constraints; Assumptions; Reporting; and Deliverables. Brainstorming: requirement elicitation method that generates creative ideas among a groupof people; success is dependent on participants’ creativity. Business Analyst (BA): a person who identifies the business needs of clients and stakeholders to determine solutions to problems; responsible for requirements development and management; acts as a bridge between the client, stakeholders, and the solution team. Business architecture: part of the enterprise architecture that shows the...
Leer documento completo
Regístrate para leer el documento completo.