E.R.P - Enterprise Resource Planning. A business management software that allows an organization to
   use a system of integrated applications.  
Legacy Systems  – The application process currently in place or the old application that was in place.

Definition of  Terms
Waterfall Methodology – A Project Management term for executing phases of a project in
  chronological order.  Generally used in a
SDLC methodology.
Initiation Document – A document supplied representing a background of the project. Purpose,
  Objectives, Scope, Deliverables, Constraints,  and Assumptions for the Project Definition.

  Business Case with Project Benefits, Cost and Timescale and Cost/Benefit Analysis

  Risk Analysis with Risk Prevention, Risk Management and Risk Monitoring

  Roles and Responsibilities with Project Leader, Business Analyst, Product Owner,
  Scrum Master, Scrum Team, Project Organization Chart/ Structure Diagram

  Initial Project Plan with Assignments/Milestones, Schedule (Gantt Chart) and Resource
Feasibility Study - – A document supplied representing topics like
  Market Analysis with Estimate of market size, Projected market share, Analysis of the competition

  Technical Analysis consisting of As-Is Analysis, Gap Analysis, Benefit  Analysis

  Financial Analysis consisting of Capital Requirements, Start-up costs, Revenue projections,
  Gross Profit Margins, Net income

  Risk Analysis consisting of Project Size, Project Definition, Agile Structure, Project Leadership,         
  Project Staffing, Project Management and Software Vendor(s).

  Time and Resource showing Expected Implementation, Completing Projects or activity,
   Available resources

  All with a GO/NoGO decision
Analysis Phase - A fact finding mission.  Identify all the files associated with this function. Contact
   and interview the user. Fact Analysis Report, Standard Naming Conventions, prototypes
Prototype – An example of how a report or process may look
Agile Management - An iterative and incremental method of managing the design and build activities
   of a process or project.
Scrum Master - The person responsible for facilitating communication between Product Owner and the
  Scrum Team.  He/She will also make sure the team has no unexpected interruptions.
Product Backlog - Process or processes needing tp be completed.  Originally sequenced by the Product
Owner but still to be discussed in the Sprint Planning meeting.
Scrum Team -  The group of people who do the work of finishing the Product Backlog.
   Designers, Programmers, Testers,  Writers, and anyone else involved.
Sprint Planning - A commitment to what is to be or has been done.  Fulfilling the Sprint Backlog.
Product Owner -  The person responsible for bring requirements from the customer, business or
stakeholders.  He/She will bring this to the Scrum Team.  The Product Owner is a specialist on    
the product for the customer's requirements.
Stakeholder - Anyone with an interest in the project. Stakeholders will provide input and are also
   affected by the project's outcome.
Sprint - A short cycle of completed backlog processes. Sprints, can last between one and four weeks.
  Multiple Sprints will be completed before the completion of a Project or Upgrades.
Sprint Backlog - A list of tasks identified by the Scrum team to be completed during the Scrum sprint.
   A product from the list of Product backlog items.
Daily Scrum - A daily meeting held to find out what each team member has done by asking:
 What did you do yesterday, What will you do today, and what is impeding you from doing your job.
Project Manager – Project managers has the responsibility of the planning, execution and
    closing of a project.
Agile Management Project