Term
| As organizations’ reliance on software grows, so do the business-related consequences of software successes and failures including |
|
Definition
Increase or decrease revenue
Repair or damage to brand reputation
Prevent or incur liabilities
Increase or decrease productivity |
|
|
Term
| Systems development life cycle (SDLC) |
|
Definition
| The overall process for developing information systems from planning and analysis through implementation and maintenance |
|
|
Term
| SDLC composed of 7 phases: |
|
Definition
planning
analysis
design
development
testing
implementation
maintenance |
|
|
Term
| There are a number of different software development methodologies including |
|
Definition
Waterfall (a sequence of phases in which the output of each phase becomes the input for the next)
Agile
Rapid application development (RAD)
Extreme programming-breaks project into 4 phases; cant continue to next phase until previous has been completed.
Rational unified process (RUP)-breaks down development into gates and either moves or gets cancelled
Scrum-produces small pieces of software using sprints to achieve a goal |
|
|
Term
|
Definition
| Consists of a series of tiny projects |
|
|
Term
|
Definition
| Agile methodology – Aims for customer satisfaction through early and continuous delivery of useful software components developed by an iterative process using the bare minimum requirements |
|
|
Term
| Rapid application development methodology |
|
Definition
| Emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process |
|
|
Term
|
Definition
| A smaller-scale representation or working model of the users’ requirements or a proposed design for an information system.The prototype is an essential part of the analysis phase when using a RAD methodology |
|
|
Term
| primary reasons for project failure |
|
Definition
Unclear or missing business requirements
Skipping SDLC phases
Failure to manage project scope
-Scope creep
-Feature creep
Failure to manage project plan
Changing technology |
|
|
Term
| consequences of failed projects include |
|
Definition
Damaged brand
Lost goodwill
Dissolution of partnerships
Lost investment opportunities
Low morale |
|
|
Term
|
Definition
| Temporary activities undertaken to create a unique product or service |
|
|
Term
|
Definition
| The application of knowledge, skills, tools, and techniques to project activities to meet project requirements |
|
|
Term
|
Definition
| An individual who is an expert in project planning and management, defines and develops the project plan, and tracks the plan to ensure the project is completed on time and on budget |
|
|
Term
|
Definition
| Any measurable, tangible, verifiable outcome, result, or item that is produced to complete a project or part of a project |
|
|
Term
|
Definition
| Represents key dates when a certain group of activities must be performed |
|
|
Term
| the three primary and interdependent variables in any project (triple constraint) |
|
Definition
|
|
Term
|
Definition
| Individuals and organizations actively involved in the project or whose interests might be affected as a result of project execution or project completion |
|
|
Term
|
Definition
| The person or group who provides the financial resources for the project |
|
|
Term
| building a project plan involves two key components: |
|
Definition
| project charter-a doc't issued that someone has stepped up to pay for and support the project. project plan-a formal approved doc't that manages and controls project execution |
|
|
Term
| SMART criteria used for project objectives |
|
Definition
| specific, measurable, agreed upon, realistic, time frame |
|
|
Term
| a well-defined project plan should be: |
|
Definition
Easy to understand and read
Communicated to all key participants
Appropriate to the project’s size, complexity, and criticality
Prepared by the team, rather than by the individual project manager |
|
|
Term
| Two primary diagrams used in project planning include |
|
Definition
|
|
Term
| program evaluation and review technique (PERT) |
|
Definition
a graphical network model that depicts a project's tasks and the relationships between them.
-dependency-logical relationship that exists b/w project tasks and a milestone
-critical path-shortest path ensuring all critical tasks are completed |
|
|
Term
|
Definition
| a simple bar chart that lists project tasks vertically agains the project's time frame, listed horizontally. |
|
|
Term
| A project manager must focus on managing three primary areas to ensure success |
|
Definition
| people, communications, change |
|
|
