Organizing all of your Project Artifacts or Work Items can be a very time consuming and frustrating task, especially when your Project or Program is large and you have millions of individual Project or Work Items to manage and track. At Proceve, we have built a number of mechanisms into our software specifically to make this task easier, based on our decades of experience trying to manage large scale programs where the number of artifacts is literally measured in millions.
One thing we have learned from 4 decades of experience managing large-scale projects, is that no matter how large or even how small the project, you will never get all of the requirements right the first time, nor list all the tasks or other artifacts in the project on your first pass.
Every project always starts with a vague, high-level view of what needs to be done, you then write those down and then over time, and through iteration, the details get fleshed out and elaborated until you hopefully reach a point where you have accounted for everything. This is true whether you use a Waterfall method, Agile or any other project management approach.
Proceve has designed everything in our software to acknowledge that fact and allow you to explicitly enter and track everything in a way that directly reflects how this information develops over time.
Every artifact in Proceve is capable of having an unlimited number of sub or child artifacts. Each of those sub-artifacts is a primary artifact in its own right. They are not limited in any way, unlike in other applications.
Used correctly, this allows you to know exactly which requirements are necessary to implement a specific piece of functionality or which tasks still need to be completed to get that piece of functionality done, all without the need to use weird naming conventions or tags, which always end up out of control and useless if you have more than two people working on your project.
Proceve allows you to define a complete Taxonomies and optionally associate them with every aspect of your Project.
This could represent:
Taxonomies allow for highly nested Hierarchies so you can enrich them and identify the finest details over time as needed.
All Artifacts can be associated with an Item from your Taxonomy, allowing you to quickly find every Artifact associated with assembling the cockpit of a plane or completing a particular screen in a software project.
All artifacts can be assigned to Categories.
All Artifacts can be assigned to predefined Groups.
Artifacts can optionally be assigned Tags. Unlike Categories or Groups, Tags can be made up on the fly and assigned to any artifact.
There are two main types of Tags which can be used.
Topic Tags: These are what we typically think of as a Tag. They start with a # and are separated by commas. For example:
#UIRequirement, #SignUpForm
Directed Tags: These are tags used to get the attention of another user. They start with an @ sign and can also be separated by commas. Here is an example:
@Paul, @Todd, @Daniel