Glossary
This glossary explains project management terms and PROEVER-specific terminology.
Project Management Terminology
| Term | Description |
|---|---|
| Program | A unit that coordinates and manages multiple related projects collaboratively.It is established to achieve benefits and outcomes that cannot be obtained through individual project management. In PROEVER, up to 10 hierarchical levels can be configured to reflect complex organizational structures. |
| Project | A temporary endeavor with clearly defined deadlines and objectives, undertaken to create unique deliverables, services, or results.In PROEVER, you select either "Waterfall" or "Agile" as the project approach when creating a new project. |
| Waterfall | A predictive project approach that proceeds in sequential, phased stages.The next phase begins after the previous phase (stage) is completed. In PROEVER, ticket management andGantt chart featuresare provided as basic operations for this approach. |
| Agile | An adaptive project approach that continuously repeats planning, execution, and evaluation in short cycles (iterations).It emphasizes rapid response to change. In PROEVER, it is managed through dedicated features such as backlog, iterations, releases, and epics. |
| Master Schedule | A high-level schedule that aggregates key planning elements (milestones, phases, etc.) across multiple projects or programs, providing an overview of overall program/project progress and interdependencies.In PROEVER, plans and progress from all accessible programs/projects can be displayed in one consolidated view. |
| WBS | (Work Breakdown Structure) A management methodology that hierarchically decomposes, defines, and structures all work elements required to achieve project objectives, based on deliverable-oriented or process-oriented approaches.In PROEVER, it is created using the ticket structure (phases, deliverables, tasks) of waterfall projects. |
| Gantt Chart | A fundamental scheduling tool that visualizes project schedules using a timeline and task list.Task hierarchies and dependencies are displayed with connecting lines. In PROEVER, waterfall "Phase," "Deliverable," and "Task" tickets are displayed. |
| Milestone | An important checkpoint or waypoint in a project, or the target completion date for major deliverables.In PROEVER, it is set and displayed as one of the ticket classifications and used for progress management on the master schedule and Gantt chart. |
| Phase | A major division or stage of work that logically segments a project.In waterfall projects, it constitutes sequential processes with verification and validation awareness, such asrequirements definition, design, and testing. In PROEVER, it is set as a ticket classification indicating key periods and displayed on the master schedule. |
| Deliverable | Concrete, verifiable results (documents, items, etc.) produced during the project process.In PROEVER, it is one of the ticket classifications alongside WBS elements (phases, tasks) and is displayed on the Gantt chart. |
| Task | The lowest level work unit in the WBS, representing specific activities.In PROEVER, it is registered as the smallest WBS element ticket classification and displayed on the Gantt chart. |
| Subtask | An element for managing individual ticket (task) work in further hierarchical detail. In PROEVER, subtasks can only be set when the ticket classification is "Task." |
| Dependency | A logical relationship between tasks that indicates the sequence of preceding and succeeding work.In PROEVER, four types (FS, SS, FF, SF) can be set between "Phase," "Milestone," "Deliverable," and "Task" tickets. |
| FS (Finish-to-Start) | A dependency type where the successor task can start after the predecessor task finishes. |
| SS (Start-to-Start) | A dependency type where the successor task can start after the predecessor task starts. |
| FF (Finish-to-Finish) | A dependency type where the successor task can finish after the predecessor task finishes. |
| SF (Start-to-Finish) | A dependency type where the successor task can finish after the predecessor task starts. |
| Issue | An ongoing problem or obstacle that affects project goal achievement.Includes materialized risks. In PROEVER, it is registered and managed as a ticket. |
| Risk | An uncertain event that, if it occurs, has a positive or negative effect on project objectives.In PROEVER, it is registered and managed as a ticket. |
| Bug/Defect | A defect or bug that exists in a product or system.In PROEVER, it is registered and managed as a ticket. |
| Review | An evaluation activity to confirm the validity and quality of deliverables or plans.In PROEVER, corrections and findings identified through reviews are registered and managed as tickets. |
| Change | A formal modification request to an approved baseline (plan).In project management, it is controlled through the change management process. In PROEVER, it is registered and managed as a ticket and used to track change requests. |
| Test | A quality control activity that verifies whether deliverables meet requirements or function as intended.In PROEVER, verification work (test cases) is registered and managed as tickets. |
| TODO | A list of specific individual work items or action items to be executed.In PROEVER, work planned as WBS is "Task," while other work is registered and managed as "ToDo" tickets. |
| Iteration | In agile development, a time unit or sprint planning unit for repeating development cycles (planning, design, execution, testing) within a fixed period.In PROEVER, iteration plans can be created from the backlog screen and progress can be monitored in real-time. |
| Epic | A unit of large-scale features or user requirements used in agile development.It functions as a parent element containing multiple stories (tasks). In PROEVER, epics can be added and edited from the side menu. |
| Release | In agile development, a unit for publishing and delivering developed features or products to customers.In PROEVER, release tickets are displayed on the master schedule with progress rates shown as percentages. |
| Backlog | In agile development, a prioritized and managed list of all tasks, requirements, features, bugs, etc. for the product.In PROEVER, it is used for iteration planning and bulk ticket update functions. |
| Story | A unit of user-perspective requirements or feature descriptions (user stories) used in agile development.In PROEVER, it is created and operated as one of the ticket classifications in agile development. |
| Story Point | In agile development, a relative unit for estimating the size, complexity, and uncertainty of tasks or stories.In PROEVER, it can be set and customized as an input field for agile tickets. |
| Dashboard | A screen that visualizes key performance indicators (KPIs) and status as graphs and aggregated values, supporting early problem detection and decision-making.In PROEVER, program/project/team status can be displayed as a 5-level health status evaluation. |
| Priority | An indicator showing the importance or urgency of tasks or requirements. |
PROEVER Terminology
| Term | Description |
|---|---|
| Workspace | An independent work space created within an organization, serving as a unit for managing projects, users, and various resources. Only MSOL can create workspaces. |
| License | PROEVER usage rights that define the features users can access and overall resource limits based on the contract plan.Licenses define the "scope of availability." |
| Role | A unit that restricts the scope of operations.Within the scope permitted by the license, it controls which operations (add/view/edit/delete) users can perform on resources. |
| Permission Group | A unit that groups multiple users together, granting access permissions to resources by assigning roles to these groups. |
| KEY | A code value used touniquely identifyprograms or projects in PROEVER. Duplicates are not allowed within the same workspace. |
| Home Screen | The screen displayed after login, providing centralized management of your assigned ticket list and important announcements from MSOL (notification list). |
| Ticket | The basic unit for registering and centrally managing various events and tasks occurring in programs or projects. Classifications and management items based on MSOL's expertise are set by default. |
| List | A view where registered tickets are displayed in list format. Useful forunderstanding the full scopeof events occurring in a project. |
| Board | A view where registered tickets are displayed inKanban styleby status. Useful for visually understanding current work status andidentifying bottlenecks. |
| Team | A unit set in programs or projects that can be selected as the assigned team or watcher for tickets. Health scores for each configured team can be checked on the dashboard. |
| Progress Rate | A numerical value indicating the degree of task completion. |
| Start Date | The scheduled date when a task, phase, issue, etc. is to begin. In Gantt charts, ticket start dates and due dates are displayed as bars along the timeline. |
| Due Date | The target date (deadline) by which a task, phase, issue, etc. should be completed. In Gantt charts, ticket start dates and due dates are displayed as bars along the timeline. |
| PROEVER AI | An AI assistant with expertise from Management Solutions (MSOL). Provides problem-solving support in chat format and detailed review functions for project plans. |
| AI Credit | A usage limit allocated to each user monthly for utilizing AI features such as PROEVER AI within a certain range. |
| Integration | A feature for data collaboration with external tools (Jira, Backlog, etc.), aggregating, visualizing, and reporting project-specific data in PROEVER. This enables PROEVER to be used as a management platform. |