Learn the key terms and concepts used in OryoNex and modern project management
Units that measure AI feature usage in OryoNex. Each AI operation (task generation, suggestions, etc.) consumes credits.
Example: Generating 5 tasks from a note uses 1 AI credit
OryoNex's AI feature that automatically creates structured tasks from unstructured notes, meeting summaries, or ideas.
Example: Converting meeting notes into actionable tasks with priorities and assignees
A user with full permissions in a workspace. Can manage members, change settings, and access all features including billing.
Example: The project manager is set as workspace admin
A set of protocols that allows external applications to interact with OryoNex programmatically.
Example: Using the API to automatically create tasks from customer support tickets
A prioritized list of tasks, features, and requirements that need to be completed. Items are typically ordered by priority or business value.
Example: Adding new feature requests to the product backlog
A graphical representation of work remaining versus time. Shows the rate at which tasks are being completed.
Example: The burndown chart shows we're on track to complete all sprint tasks
OryoNex's collaborative space where teams can capture ideas, notes, and thoughts that can be transformed into tasks using AI.
Example: Recording project ideas in the Brainstorming Hub before sprint planning
A restricted role that allows users to view tasks and add comments, but not create or edit tasks. Useful for stakeholders.
Example: Giving the client comment-only access to review progress
A large body of work that can be broken down into smaller tasks or user stories. Epics typically span multiple sprints.
Example: An epic for 'User Dashboard Redesign' containing 15 smaller tasks
Security measure that ensures data is encrypted during transmission and storage, protecting sensitive information.
Example: All task data is encrypted with AES-256 encryption
A visual project management method that uses boards and cards to represent work items. Tasks move through columns (like To Do, In Progress, Done) as they progress.
Example: Moving a task card from 'In Progress' to 'Review' column
A user with standard permissions in a workspace. Can create, edit, and complete tasks, but cannot modify workspace settings.
Example: Adding a new developer as a member to the project workspace
A way to notify specific team members in comments or descriptions by typing @ followed by their name.
Example: Typing @sarah to notify Sarah about a task update
AI technology that understands and processes human language, enabling features like task extraction from plain text.
Example: Writing 'Schedule meeting with John next Tuesday' and having it create a calendar event
A secure authorization framework used for third-party integrations like Zoom, Google Calendar, etc.
Example: Connecting your Zoom account to schedule meetings directly from tasks
Instant synchronization of changes across all team members. When someone updates a task, others see it immediately.
Example: Two team members editing the same task simultaneously
A fixed time period (usually 1-4 weeks) during which specific work must be completed. Commonly used in Agile and Scrum methodologies.
Example: A 2-week sprint to complete the user authentication feature
AI-powered recommendations for task improvements, such as better descriptions, estimated time, or related tasks.
Example: AI suggests adding a deadline based on task complexity
Authentication method that allows users to access OryoNex using their existing corporate credentials.
Example: Logging into OryoNex with your Google Workspace account
A short, simple description of a feature from the end user's perspective. Format: 'As a [user], I want [goal] so that [benefit]'.
Example: As a team lead, I want to see task progress so that I can track team performance
A measure of the amount of work a team can complete in a sprint. Used for planning and predicting future sprints.
Example: Our team's average velocity is 45 story points per sprint
Tasks that are currently being worked on. WIP limits help prevent overload and improve flow.
Example: Setting a WIP limit of 3 tasks per developer
A separate environment in OryoNex containing its own boards, tasks, and team members. Ideal for organizing different projects or departments.
Example: Creating separate workspaces for 'Marketing' and 'Development' teams
Automated messages sent from OryoNex to other applications when specific events occur.
Example: Sending a Slack notification when a high-priority task is created