Day to day terminology:

• Triple Constraint: a four-component group represented by a triangle
  • Time, Scope, and Cost are the corners
  • Quality is the center
  • A change in one will impact the others
    • Balance
• Gantt Chart: a bar chart that displays the scheduled information graphically
  • Useful in planning, scheduling, and managing the relationship between tasks
  • Used to keep project team and sponsors informed about project progress
• Active Directory: Microsoft-based app used to manage user credentials (accounts, roles, and permissions)
  • An application account = a machine running with user capabilities
• Scrum: an Agile process framework for managing work (software development)
  • Designed for teams of about 9
  • Work is broken into goals that can be completed in timebox iterations called Sprints
• Agile: various approaches to software development in which requirements and solutions evolve through collaborative effort and self-organizing and cross-functional teams
  • Advocated adaptive planning, evolutionary development, early delivery, and encourages rapid and flexible responses to change
• Sprint: also known as “iteration” or “timebox”
  • An agreed upon timeframe; one week to one month - usually two weeks - within which planned activity takes place
• Critical Path Method (CPM): an algorithm for scheduling a set of project activities
  • A step-by-step approach for analyzing critical and non-critical tasks and the amount of time required to complete them
• Earned Value Management (EVM): a process where one can schedule, measure, and check the scope of performances
• Milestone: significant points in time or and event that marks important moments in a project timeline
  • When his development goal is reached, we present to the client for review
• Deployment: the act of transferring the project (complete or in part) over to a hosting platform
• Database: a collection of information that is organized so it can be easily accessed, managed, and updated
• Bugs: an error, flaw, failure, or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways
  • Bugs are a normal part of software development
• Features: the way an application tells the container what capabilities it needs to function
  • Our are detailed in scopes
• Staging: a pre-release version which is available to testers
  • One of two instances
    • Having two instances allows us to test new versions or fixes on staging without causing outages on the user-facing production environment
• Production: the version which is business-ready and available to end users
  • One of two instances
• Sandbox: a private test-copy of the project where users can test and interact with the project without fear of breaking anything
• Change Order/Request: any changes, additions, or deletions to the contracted scope of work will be documented with a change order
  • AKA Contract Amendment
• Deep Dive: an in-depth examination or analysis of a topic
• Due Diligence: the investigation or exercise of care that a reasonable person or business is expected to take before entering into an agreement or contract with another party