ResourceFirst is a powerful resource planning tool for aligning resource capacity with demand to ensure that your project portfolio is feasible well-staffed. It includes dynamic portfolio and scenario planning for what-if analysis and comparison to financial and FTE targets. It also works for both waterfall-based projects and team-based Agile projects.
ResourceFirst™ is available for cloud and on-premise installations, providing first-line managers, executives, PMO and EPMO functions the agility to meet fluctuating work priorities, schedules, demand, and staff capacity.
PDWare Approach - Getting Started
The PDWare philosophy is to, above all, ensure proper resource planning and allocation to generate the greatest short term impact toward portfolio and strategy execution. It's why we called our flagship solution ResourceFirstTM.
Traditionally, organizations have viewed resource planning as an afterthought, focusing primarily on project management. It's no wonder "inadequate resources" is consistently at the top of the list for reasons why projects fail.
With a feasible portfolio based on a continuous resource planning process, more detailed prioritization and execution methods can then be added based on client need.
ResourceFirstTM was designed with several different types of users in mind:
- Resource/Functional Managers
- Project Managers
- PMO/Portfolio Managers
- Financial Managers
- And more
In the application interface, the role-based functions are provided in an "area" for each function.
The main system areas include:
- Home (Team member)
- PMO/Portfolio Analysis
- Reporting (Qlik)
- Actuals (aka Timesheets)
See ResourceFirst Navigation for an overview of how to navigate around the system.
Foundational Data in ResourceFirst
Our approach is that software should be simple and practical, and not get in the way. Along those lines, while ResourceFirst is a powerful, dynamic software product, its key functions rely on a simple set of foundational data:
- Project data - including charter info, priority, budget, dates, tasks, dependencies & more
- Resource data - including skills, rate, cost centers, and working hours (i.e., capacity)
- Assignments (Labor and Financial Forecasts) - Time-phased labor FTEs or hours, by project and resource, and tIme-phased financials by project and financial item.
To learn more about each of the main areas in ResourceFirst, visit the respective sections in this site, where you'll find a wealth of how-to content, best practices, and more.
In PDWare software, a project portfolio is a grouping of projects, and a resource portfolio is a grouping of resources. These groupings are defined in terms of Organizational Breakdown Structure (OBS) "nodes." A resource OBS typically represents how resources are organized in the company (usually by a hierarchy of divisions and departments). A project OBS node can be similar or can be arranged by some other functional grouping.
An example of node hierarchy might be:
------ Division 1
------ Division 2
When projects or resources are created, they are created in the desired node and the appropriate level in the structure.
Each user of ResourceFirst sets their "portfolio" by selecting which project and resource nodes they'd like to filter on, and which date range they would like to view for their data. This setting remains set, even after they sign off and back on again. Which nodes a user has access to depends on their rights as set up by your PDWare administrator.
For more on OBS nodes and how to set them for your session, see the Filters/Get Data section in the ResourceFirst Navigation article.