Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
Project Management
PM terms
| Term | Definition |
|---|---|
| Acceptance Management | A process to be used throughout the project to obtain approval from an authorized Customer Decision Maker for work done on the project to date.This process is defined and included in the Project Plan. |
| Accessibility | Access to information and data for Customers with disabilities comparable to that accorded Customers who do not have disabilities. |
| Activity | Is equivalent to a process and is a piece of work accomplished during a project. A process can be broken down into tasks. |
| Attribute | A data element that holds information about an object (entity). |
| Baseline | An initial measurement that can serve as the basis for future comparisons. Applies to the Project Schedule. |
| Benchmark | A standard against which measurements or comparisons can be made. |
| Best Practices | Certain procedures recognized during the course of the project by the Project Manager, Project Sponser, or Project Team, that, when exercised, improved the production of a deliverable, streamlined a process, or ways to improve standardized templates, etc. |
| Best Practices | Must be documented and shared with other Project Managers so that they can be repeated. |
| Brainstorming | A technique used to stimulate creative thinking and overcome impasses to problems. Team members gather in a room and offer ideas for solutions to a problem(s). No idea is rejected no matter how absurd or impractical. |
| Brainstorming | Often a practical solution surfaces and a decision is reached by group concensus. |
| Business Rules | Practices associated with certain business processes that are required by regulation, law, accounting controls or business practices, should be defined in as much detail as possible using techniques such as structured English. |
| Business Continuity Planning/Disaster Recovery | BCP/DR |
| Business Continuity Planning/Disaster Recovery | Develop advance arrangements and procedures that would enable an organization to respond to a disaster and resume its critical business functions within a predetermined timeframe, minimize losses, and repair or replace the damaged facilities ASAP |
| Business Process Re-engineering | BPR |
| Business Process Re-engineering | A technique used to optimize organizational processes |
| Capability Maturity Model | CMM |
| Capability Maturity Model | Describes the stages through which software organizations evolve as they define implement, measure, control, and improve their software processes. |
| Capability Maturity Model | This model provides a guide for selecting process improvement strategies by facilitating the indentification of current process capabilities and the issues most critical to software quality and process improvement. |
| Change Control | A plan for handling changes to a project aimed at minimizing the negative effect on a projects outcome. Change is defined as ANY adjustment to any aspect of the Project Plan or to any already approved deliverable(s) |
| Client-Server | A system architecture where a host computer or 'server' provides data and services to requesting or 'client' workstations |
| Computer-Aided Software Engineering | CASE |
| Computer-Aided Software Engineering | A tool that automates and improves aspects of the System Development Life Cycle |
| Configuration Management | Discipline applying tech and admin direction to ident. and doc. functional & physical characteristics of a sys. component, control changes to characteristics, record & report change processing & implementation stat. and verify compliance w/ specified reqs |
| Constraint | Something that establishes boundaries, restricts, limits or obstructs any aspect of the project |
| CSSQ | The interdependent quadruple constraints of the project (scope, cost, schedule and quality), represented by project scope, project budget, project schedule and quality management plan. |
| Consumer | Include all people that will use the product or service that the project is developing. Those internal to the Performing Organizations may also be Customers |
| Cost/Benefit Analysis | A comparison of the cost of the project to the benefits it would realize, to determine whether the project or portion of the project should be undertaken |
| Critical Success Factor | CSF |
| Critical Success Factor Interviewing | A process in which a series of strategic questions are asked to identify what objectives and goals need to be met in order for the project to demonstrate success |
| CRUD Matrices | A tool used to cross reference the Process Model to the Logical Data Model and to identify which business functions map to which data elements. |
| CRUD | Create, Replace, Update, Delete |
| Customer | Comprise the business units that identified the need for the product or service the project will develop, can be at all levels of an organization, from Commissioner to entry-level clerks |
| Customer Representatives | Subject matter experts |
| Customer Representatives | Responsible for accurately representing their business units' needs to the Project Team and to validate the deliverables that describe the product or service that the project will produce |
| Customer Representatives | Towards the end of a project, they will test the product or service the project is developing, using and evaluating it while providing feedback to the project team |
| Customer Decision-Makers | Have been designated to make project decisions on behalf of major business units that will use, or will be affected by, the product or service the project will deliver |
| Customer Decision-Makers | Member of the POM responsible for achieving consensus of their business unit on project issues and outputs, and communicating to the Project Team. |
| Database | An integrated collection of data (entities and attributes) organized to avoid duplication of data and allow for easy access |
| Database Schema | A view of the physical database detailing the specifics of the tables, fields and their relationships, and identifying keys, indexes, and triggers |
| Data Flow Diagram | A picture diagramming how data flows through a system. It depicts the external entities (which are sources or destinations of data), the processes which transform that data, and the places where the data is then stored |
| Data Dictionary | Reference material that describes and defines each piece of data used in a system. This may include entity and attribute definitions, discuss relationship characteristics and provide sizing information |
| Decision Trees | A branching chart showing the actions that occur from various combinations of conditions and decisions |
| Defect | A flaw in a system or system component that causes the system or component to fail to perform its required function |
| Defect Tracking | The process of ensuring that all test cases have been executed successfully. If cases have not executed successfully and defects have been identified, a log is generated to track the defects so that the Project Team can correct them and perform a retest |
| Deliverable(s) | A product or service satisfying one or more objectives of the project |
| Effort Estimate | An estimate of the amount of effort necessary to perform each project task |
| Encryption | The coding of data either at its source or as part of a data stream to prevent unauthorized access to the data. For example, information transmitted over a telecommunications line is scrambled at one end, and unscrambled at the other |
| Entity | A distinct object that is represented in the database containing source data or acting to collect data. An example would be a customer table. |
| Entity Relationship Diagram | ERD |
| Entity Relationship Diagram | Pictorial representation of the relationship between entities. Can be helpful in communicating information needs w/ business users & can also provide info to tech. specialists for design of physical databases, foreign keys, business views, and so forth |
| External Stakeholder | Anyone outside the Performing Org. that are in any way affected by the new product or service. Within the context of New York State Government, this group may include the Legislature, the Executive Chamber, other agencies, the media, and the citizens |
| Flowchart | A graphical representation of the flow and interaction of a process or system. |
| Functional Decomposition | The process of dividing higher-level functions into sub-functions and processes |
| Graphical User Interface | GUI |
| Graphical User Interface | The front-end of an application through which the user interacts with the system by utilizing buttons, the mouse, drop down menus, etc. The face of the application where the user will see data displayed. |
| Hosting | Service in which a provider or org. may house an application & support the software & hardware needs required to run that application. This may also include the housing and management of a networking and or telecommunications infrastructure. |
| Internal Stakeholders | People that are in any way affected by the new product or service within the Performing Organization |
| Internal Stakeholders | Include Proj. Team, POM, Customers, cust. co-workers who are affected by changes in Customer work practices;Cust. managers affected by modified workflows or logistics;Cust. correspondents affected by the quantity or quality of newly avail. info; etc. |
| Issue Management and Escalation | A process for capturing, reporting, escalating, tracking, and resolving problems that occur as a project progresses. |
| Joint Application Design | JAD |
| Joint Application Design | A process that brings the Project Team, Customers and Stakeholders together to clarify, define and gain consensus on business requirements. |
| Joint Application Design | Formal meetings involving a detailed agenda, visual aids and a facilitator who moderates the session and an analyst who records the specifications. By utilizing them, Customers become directly involved in the application design. |
| Local Area Network | LAN |
| Wide Area Network | WAN |
| Local Area Network | Provide a means to link multiple computers within a single location. May be interconnected with one another or with WANs, using interface devices such as bridges, routers and gateways. |
| Wide Area Network | Provide a link for widely seperated locations. |
| Lessons Learned | Information resulting from feedback on the project and based on the assessment of project performance, that may benefit the Project Manager as well as managers and team members of similar projects |
| Matrix Diagram | A format used to clarify or highlight the relationship between two factors. |
| Matrix Diagram | May be used during gap analysis to validate that all business requirements identified during JAD sessions have been accommodated in the process and logocal data model deliverables. |
| Matrix Diagram | Displays requirements down left side of the grid, while processes or data elements are tracked across the top of the grid. A checkbox at the intersection would indicate that the requirement has been successfully accounted for in a deliverable. |
| Multi-Tier/Client-Server | MT/CS |
| Multi-Tier/Client-Server | A client-server system architecture, where software application is decomposed into operational areas or layers (e.g., database, business objects and presentation layers), which are then physically distributed across multiple computers. |
| Normalization | Process by which complex data relationships are simplified w/ the goal being to eliminate redundancies in the database design. |
| Outsourcing | The practice of contracting out a project, a portion of a business, or an IT operation. |
| Parallel Testing | The concurrent testing of both the current and new system with identical data to compare the outputs for consistency and accuracy. |
| Peer Code Reviews | A formal repeatable review technique that gathers peers to examine a deliverable or work product for defects so they can be corrected early in the development cycle. |
| Performing Organization Management | POM |
| Performing Organization Management | All members of the organization's management team that may exert influence on Project Team members or be affected by and involved in the development and implementation of the product of the project. |
| Phase | A series of processes organized into a distinct stage of project development. The end of which usually coincides with the approval of a major deliverable. |
| Post-Implementation Report | Summary of info gathered as a result of conducting the Post-Implementation review. Documents the successes and failures of the project and provides a historical record of the planned and actual budget and schedule. |
| Post-Implementation Report | Also contains recommendations for improvement to be used by other projects of similar size and scope. |
| Process | A series of tasks performed to bring about a result. |
| Process Flow Diagram | Used to analyze the flow of a process, find problems, create solutions and measure efficiency. Symbols are used in a visual representation that can quickly point out delays, unnecessary events and other problem areas. |
| Project | A temporary endeavor undertaken to create a unique product or service. |
| Normalization | Simplifies data management and software development efforts while improving data consistency and optimizing system performance. |
| Project Audit | A process designed to ensure that the Quality Assurance activities defined in Project Planning are being implemented and to determine whether quality standards are being met. |
| Project Lifecycle | A collection of phases whose number and names are determined by the control needs of the Performing Organization. |
| Project Management | Direction and coordination of human and material resources for a project using management techniques to achieve cost, scope, schedule, quality and customer satisfaction objectives. |
| Project Manager | The person who is responsible for ensuring that the team completes the project. Develops Proj. Plan with the team and manages the team's performance of project tasks. Secures acceptance and approval of deliverables from Project Sponsor and Stakeholders. |
| Project Repository | A collection or archive of all information and documents from the project. |
| Project Sponsor | A manager with demonstrable interest in the outcome of the project who is responsible securing spending authority and resources for the project. Ideally, should be the highest-ranking manager possible, in proportion to the project size and scope. |
| Project Sponsor | Initiates the Project Proposal process, champions the project in the Performing Organization and is the ultimate decision-maker for the project. |
| Project Sponsor | Provides support for the Project Manager, approves major deliverables and signs off on approvals to proceed to each succeeding project phase. |
| Project Team | The group that is responsible for planning and executing the project. Consists of the Project Manager and a variable number of members, who are brought in to deliver their tasks according to the Project Schedule. |
| Proof-of-Concept | A technique used to confirm the feasibility of one or more components of the technical solution. This approach helps minimize cost by 'testing the waters' first on an idea or a design. |
| Prototyping | Process of building a small working version of a system design as a means of hedging risk & attaining Customer buy-in. Can provide a better understanding of Customer requirements, validate those requirements & sometimes perform as a proof-of-concept tool. |
| Pseudo Code | A tool for specifying program logic in English-like readable form, without conforming to the syntactical rules of any particular programming language. |
| Quality Assurance | Evaluation of project performance on a regular basis to ensure that the project will satisfy the established quality standards. |
| Quality Control | Monitoring of project results to ensure compliance with the appropriate established quality standards and to eliminate causes of non-compliance. |
| Quality Standards | Criteria established to ensure that each deliverable created meets a certain level of quality agreed to by the Customer and Project Manager. |
| Rapid Application Development | RAD |
| Rapid Application Development | A technique that allows users to participate in an iterative design and development process. Conceptually, the project 'loops' through the Design, Construction and Acceptance stages, followed by a re-Design, revised Construction, Acceptance and so on. |
| Regression Testing | The process of testing new software components in an environment where other existing modules (or the entire application) are also tested to ensure that the new components do not negatively impact any existing software. |
| Release Management | A process used to manage the release of software into different test environments. |
| Release Management | It is typical for projects to identify a release engineer or department to monitor versions of software and their release into the next monitor versions of software and their release into the next environment. |
| Risk | An anticipated event with the potential to positively or negatively affect the project. |
| Risk Assessment | A process to identify which risks are likely to affect a project, documenting them, and determining which require a mitigation plan. |
| Skills Inventory | A record of the skills learned and used on the project by the Project Team. |
| Software Quality Assurance | A planned and systematic pattern of all actions necessary to provide adequate confidence that a software work product conforms to established technical requirements. |
| Software Quality Assurance | A set of activities designed to evaluate the process by which software work products are developed and/or maintained. |
| Storyboarding | A technique to use during a JAD session to aide in the brainstorming process. |
| Storyboarding | Ideas are written down on cards and posted immediately on a wall by the participants. Once all the ideas are posted, several passes of categorization take place. Some ideas may be dropped via group consensus; others may be enlarged or improved. |
| Strategic Plan | A formal document produced by the Performing Organization outlining organizational goals and direction over a designated period of time. This drives the proposed solution developed during Project Organization. |
| Structured English | A precise form of English that uses the logical structures of structured coding to represent policies and procedures. |
| System Context Diagram | A graphical representative of how the system fits into the current environment. It shows all interfaces to and from the system and allows the Project Team to visualize how the new system will interact with other systems, outside entities and Consumers. |
| System Load Analysis | A process to ensure that the application or system developed will operate under peak usage conditions. |
| Task | A single piece of work itemized in the Project Schedule to which effort and resources must be applied. |
| Test Cases | Individual test scenarios that may be executed singularly or in combination to test modules or strings of modules. Test cases should be developed by the Project Team to test what is expected, as well as what should not be expected. |
| Test Plan | A series of test cases that when compiled into a whole constitute a plan for the Proj. team to follow. If well-formulated, it should ensure that internal components and sys. interfaces operate correctly according to Functional & Technical Specifications. |
| Test Scripts | Pieces of code which when executed for a test case or a test plan are automatic. Helps save time when testing components on a regular basis with large amounts of data or if planning to execute a test plan on a recurring basis, such as regression testing. |
| Total Quality Management | TQM |
| Total Quality Management | Both a philosophy and a set of guiding principles that represent the foundation of a continously improving organization. |
| Total Quality Management | The application of quantitative methods and human resources to improve the materials and services supplied to an organization and the degree to which the needs of the Customer are met, now and in the future. |
| Unified Modeling Language | UML |
| Unified Modeling Language | A modeling language used to define a system prior to construction, much like a blueprint is used prior to building a house. |
| Unified Modeling Language | Allows the Project Team to specify, visualize and document an application, including its structure and design, in a way that meets all of the user business requirements. There are several tools on the market that use this methodology. |
| Use Cases | Modeling technique within UML, used to define business reqs from the point of view of the user. Help provide an understanding of the functionality of the system and interactions among objects and form the basis of both sys. construction and sys. testing. |
| Use Cases | A sequence of actions that an actor (usually a person), but perhaps an external entity, (such as another system) performs within a system to achieve a particular goal. |
| Walkthroughs | A technique for performing a formal review which takes place at review and inspection points throughout the lifecycle being utilized, to observe and verify what has been accomplished. |
| Work Breakdown Schedule | WBS |
| Work Breakdown Schedule | A grouping of project elements or components which defines the total project scope. Is deliverable-oriented and each descending level represents an increasingly detailed definition of a component. |
| Work Flow Diagram | A graphical representation of the organization's workflow. Which is helpful when documenting the current working model and when looking for opportunities to improve a process. |
Created by:
rainldy21
Popular Computers sets