Here’s an overview of artifact types and how to manage them within the Proceve software. This video is designed to help you understand artifacts and how they work within Proceve software for both simple and complex organizational needs.
Artifacts are the backbone of everything in our software. An artifact can be a requirement, task, test, issue, document, milestone, objective, or result. We also have special types of artifacts, which include feature requests, roadmap items, and tracking projects.
Artifacts can have parent-child relationships, allowing for sub-artifacts within sub-artifacts, and so on. All sub-tasks have the same properties, behaviours, management capabilities, and organizational capabilities of the respective original task.
This unlimited hierarchical structure ensures of artifacts share the same properties and management capabilities.
All artifacts inherit basic details such as name, summary, and description. Additional properties include stage, status, planning details, estimation, scheduling, dependencies, organization, and tracking.
Our Artifacts include planning details like sprint assignments and deadlines. This helps in tracking the scheduling and progress of each artifact.
Proceve offers extensive estimation capabilities for all types of artifacts, allowing for detailed effort estimates for requirements, tasks, etc. Users can also apply estimates of resource allocation, costing, and more to all artifact types.
Our robust scheduling tool allows for users to not only schedule tasks and set deadlines, but also track the actual completion dates and durations, allowing for a comparison between planned vs actual progress.
Proceve’s dependencies can be tracked between different artifact types. For example, a dependency can be between a requirement and task or test and a task, not only a task and a task.
These dependencies are tracked as well and can be displayed in multiple views, including Gantt Diagrams.
As mentioned above, Artifacts can be organized hierarchically. This includes the ability to add unlimited subtasks and sub-artifacts, each maintaining full properties and capabilities.
Artifacts can be organized using tags and categories, with hierarchical categorization allowing for detailed organization, such as differentiating between mobile UI tasks and web UI tasks.
These tags can include:
Proceve allows any artifact to be associated with multiple tracking projects (eg. You can link projects A, B, and E simultaneously).
This feature allows for aggregation and monitoring of items across various projects.
Artifacts support threaded conversations, similar to communication tools like Teams or Slack, allowing for integrated and detailed discussions within the software.
Artifacts can have attachments and support both manual and automatic time tracking, with detailed time entries and comprehensive timesheet capabilities.
Proceve supports both manual and automatic time tracking for any artifact. Users can track time spent on writing requirements or documents, performing tasks, tests, etc. Each entry will record who entered it, when the entry was entered, who it was assigned to, and how long they worked on it.
The entries are displayed individually, but they can be aggregated up as well, and they can be displayed in timesheets for extensive time tracking capabilities.
Every artifact includes a complete version history, with each change archived and given a new version. We also built data retention policies that can be defined for managing historical records.
While we have set a default policy, companies will be able to define their own policies in the future, dependent to the respective rules and regulations.
Proceve offers extensive traceability features, enabling the tracking of relationships between different artifact types and supporting complex relationship management. For example, users can link a requirement to a conversation.
Proceve software provides a robust and flexible structure for managing artifacts, ensuring that even the most complex organizational needs are met efficiently.