PI® is very good at traditional water fall (sequential) work management, measurement, and analysis. Over the years, it has also managed to lead in blended methodologies such as Agile, Scrum, Kanban and others by level-setting the various management techniques into a reportable, common format that managers and C-level people understand about their businesses.
Since PI has integrations with Jira, Trello, Azure DevOps, Excel, MS Project, Zendesk and a host of others... it's a good idea to understand how PI classifies items in its hierarchy for integrations.
Projects are the top-most "container" for work being done. Besides tracking the overall status and progress, PI allows you to set/measure overall metadata about the work being performed:
- Rate Cards
- Target Schedules
- Target Budgets
- Target Billable
PI Projects are mirrors of the Projects of the app being integrated with.
Summary Tasks in PI are a group of Tasks that roll up under one "container" for the purpose of organization, role, or measurement. In PI, tasks automatically roll-up their work data under this line item in the project, and can be expanded or collapsed to make it clear for bigger projects.
PI Summary Tasks normally mirror Epics in Agile apps being integrated with.
PI Tasks are the individual "line items" of a given Project. They capture:
- Work performed
- Timesheet entries
- Expense codes
- Related Items
PI Tasks normally mirror the Line Items of the app being integrated with. They could be called "tasks", "issues", "tickets", "cards" or a host of other singular work records.
It's important to understand how differing hierarchies map into Project Insight as PI provides a great deal of flexibility in its integrations. If you have any questions about our integrations and how things (can) map, please contact me at firstname.lastname@example.org.
Please sign in to leave a comment.