Benefit: Control
Exerting the proper level and type of control is critical to the success of any project. Too little control yields chaos, whereas too much control yields unnecessary administrative overhead and can kill the throughput (and motiviation) of the project team.
We believe that teams operate best when the "right thing to do" procedurally is also the "easy thing to do" tactically. Having a set of control structures that are mated to the needs and dynamics of your project is the best way to meet this objective.
ProjectPipe ships out-of-the box with a simple and robust control mechanisms in place. All data (and RSS feeds) are password protected, and HTTPS wire encryption is available. Our Role-based Security provides a simple and robust mechanism for preventing unwanted changes to your data. Furthermore, all changes to your data are tracked and maintained in ProjectPipe's audit history
How does ProjectPipe improve project Control?
- Role-based Security: Safeguard your project assets using a security model that makes sense for your project team
- Consistency: Leverage templated content and integrated process support, both of which are customizable
- Unified Project Data Repository: Since ProjectPipe stores MS Project Plan Tasks, Requirements, Issues,and uploaded files, you can keep all of your project data in one place (and easily backup your data whenever you want), rather than keeping in a number of emails, file servers, and individuals' laptops.
- Workflow: Manage the status of data and deliverables using customizable State/Transition workflow
Who Lives for Better Project Control?
- The Project Management Office (PMO) who is looking to provide standardized templates and process guidance across the organization's project portfolio.
ProjectPipe maintains all of its templates and Process Guidance as HTML (that can be edited using ProjectPipe's integrated editor), so it is easy to leverage existing templates or other company-specific collateral in your project. - The Project Manager who needs to provide a partner organization with read-only access to the issues list and release schedule, but doesn't want to share any potentially sensitive Documents.
ProjectPipe has Role-based Security that allows the Project Manager to provide read/write access to Requirements, Issues, and the project plan tasks, but prevent any access to the Document repository. - The CIO who needs to enforce separation of duties across Customer, Development, and QA groups by enforcing role-based security as they work to build a more mature delivery organization.
ProjectPipe ships with a set of typical roles (Project Manager, Developer, QA, Business Analyst, etc.) that have the appropriate privileges for each type of data. For example, Developers cannot delete requirements. Of course, both the roles and permissions are customizable.
Control-related Features
ProjectPipe has a number of features designed to provide better control over project execution: