A | B |
Digital Convergence | integration of data, voice, graphics and video |
EDP Era | Electronic data processing era: Corporations purchased very large computers and mainframes in order to automate tasks such as accounting, inventory, and production tracking. |
PC/Micro Era | IBM's personal computer or "infomate" was created in order to give more employees access to the powerful computing skills previously only provided by mainframe computers |
Network Era | Need to integrate all data within a company to prevent redundancy |
CHAOS Study | Standish Group of 365 IT Managers that drew attention to the "software crisis" |
Information Technology Project Management (ITPM) | IT Projects require time, money, and other resources such as people, technology, facilities, etc. Organizational resources are limited, so organizations must choose between competing interests. This decision should be based on the value a potential project will bring |
A Value-Driven Approach | IT Projects must provide value to the organization |
Socio-Technical Approach | It's not just about the technology or building the better mouse trap. Clients must become stakeholders in the project. You must actively seek and encourage their participation, involvement, and vision. |
Project Management Approach | Processes and infrastructure (Methodology), Resources, Expectations, competition, efficiency and effectiveness |
Methodology | the step-by-step activities, processes, tools, quality standards, controls and deliverables that are define for the entire project. |
efficiency | Doing the thing right |
effectiveness | doing the right thing |
Knowledge Management | A systematic process for acquiring, creating, synthesizing, sharing, and using information, insights and experiences to transform ideas into business value. Uses lessons learned and best practices |
Lessons Learned | Documents both reasons for success and failure |
Best Practices | A way to do something in the most efficient and effective manner |
Project | temporary endeavor undertaken to accomplish a unique product, service or result. |
Project Management | The application of knowledge, skills, tools and techniques to project activities to meet project requirements. |
4 Parts of Managing a Project | 1. Identifying Requirements 2. Establishing clear and achievable objectives 3. Balancing the competing demands for quality, scope, time and cost 4. Adapting the specifications, plans, and approaches to the different concerns and expectations of the various stakeholders |
Attributes of a Project | Time frame, purpose, ownership, resources, roles, risk and assumptions, interdependent tasks, organizational change, and Operating in environments larger than the project itself |
3 Parts of the triple constraint or "Iron Triangle" | Scope, Schedule, Budget |
Progressive Elaboration | A term that describes something that must be completed in several steps or increments, in a certain order |
Project Life Cycle (PLC) | a collection of logical states or phases that map |
5 Parts of the Generic Project Life Cycle | 1. Define Project Goal 2. Plan Project 3. Execute Project Plan 4. Close Project 5. Evaluate Project |
baseline plan | initial plan that defines the agreed upon scope, schedule and budget and is used as a tool to gauge the project's performance throughout the life cycle. |
5 Parts of the Systems Development Life Cycle (SDLC) | 1. Planning 2. Analysis 3. Design 4. Implementation 5. Maintenance & Support |
Waterfall Method | 1. Define requirements 2. Design 3. Build 4. Test 5. Implement 6. Maintenance. Stresses sequential and logical flow between steps |
Rapid Applications Development (RAD) | a type of iterative development: A less formal way to expedite the SDLC into a series of iterations that only include 25% of the requirements at a time |
Prototyping | a type of iterative development that hurries the process of developing a system along to the point where it can be used to discover or refine system requirement specifications |
Spiral Development | a type of iterative development that focuses on breaking the project up by risk and addressing them one at a time, building on the last |
Agile Systems Development | a type of iterative development that involves eXtreme programming (XP). This allows developers to release several difference, feature limited, versions of the program called releases |
eXtreme project management | features high speed, high change, high uncertainty and high stress. Flexibility and adaptability are key |
The Project Management Body of Knowledge (PMBOK) | documents 9 project management knowledge areas. These include: integration, scope, time, cost, quality, human resource, communications, and risk management |