Resource management is the method of balancing the distribution of work across members of the team by predicting the effort of individual tasks.
Benefits of Resource Management
Predictions represent the weight or complexity of a task and are designed to help teams estimate the amount of effort required to accomplish it. They serve multiple purposes, such as:
Comparing Task Efforts: Understand how the effort for one task stacks up against another, helping prioritize and allocate resources.
Planning Project Efforts: Estimate the total effort needed to achieve a Milestone by summing the Story Points of individual tasks.
Resource Allocation: Track the total effort assigned to a team member over a given period, ensuring that workload distribution is balanced.
Predictive Units: Estimates & Story Points
Nifty offers two key ways to predict task effort: Estimates and Story Points.
Estimates are created as a unit of time, such as one hour or 15 minutes
Story Points convert time into a point value, with typically one day of work equating one point.
Both of these predictive units represent the weight or complexity of a task and are designed to help teams estimate the amount of effort required to accomplish it.
Setting up Resource Management
Whether you're using Estimates or Story Points, you'll fundamentally be comparing the values of the predictive unit against the capped bandwidth of an individual.
In order to manage resources in Nifty, you'll need to set up the following:
The set up is small, but the benefits are massive! Let's dive in.
Selecting Between Estimates and Story Points
While you can use a mixture of both predictive units throughout Nifty, one will be set as the default across projects with the ability to override the workspace selection on a per-project basis.
Start by accessing your Workspace Control Center panel via the dropdown menu.
Choosing the Default Predictive Unit (Workspace level)
In the Planning section of the Control Center, select between Story points and Hours. If you do not plan to utilize resource management and want to disable both predictive units, select None.
Choosing the Default Predictive Unit (Project level)
Select the Projects tab of the Control Center and specify the project in which you wish to override the workspace default. From there, update the Estimation unit.
Establishing Capacity with Working Hours
Capacity is the amount of work a member of your team is determined to be able to handle.
For example, if your typical work day is an 8-hour day Monday - Friday, your capacities will be:
Estimates: 40 hours (8 hours a day x 5 days as week)
Story Points: 5 points (1 point a day x 5 days as week unless the default point value was overridden in the previous step)
Creating Workspace Working Hours
Working hours will set the default baseline for how many hours a week your team works. Note that both the time zone working hours can be adjusted on a per-user basis, as shown in the next section.
Within the Planning screen, start by selecting the default workspace time zone.
Your workspace will have default working hour blocks which can be updated when clicked. These blocks indicate the overall time your employees are available for work on a daily basis.
You can also indicate days off or Add a break if your company has a break period between working hours.
Use Copy to... to quickly apply these parameters to other days.
As you adjust the working hours on a per-day basis, the weekly total will update. This value is the hourly capacity of each team member unless otherwise specified.
Defining an Individual's Working Hours
If you want to indicate that certain members of your team have different work schedules than others, select the + Give someone their own hours option.
Once you've selected the individual, you can update their specific time zone and work schedule to define their availability and capacity.
Setting a Prediction on a Task
By assigning a prediction to tasks, your team can understand the effort of each task in relation to other tasks, as well as in relation to member's workloads.
How you create this prediction depends on the predictive unit you're using:
Estimates: Set estimates with inputs such as 1.5h (hour and a half) or 15m (15 minutes)
Story Points: Set estimates such as 1 (one day of work) or .5 (half of a day of work)
Inserting a Prediction on a Task
The workspace's default predictive unit (unless overridden on the project level) will appear inside of a task.
The efforts assigned to a Task will also be attributed in full to each assignee of the task (more on this later in the article).
Tracking Roadmap Progress Based on Efforts
Lists in your roadmap will aggregate the amount of Story Points assigned to the open and completed tasks within it. In this way, a list provides two reporting metrics:
A percentage of completed tasks by count (reflected as the milestone progress bar).
The fraction indicating the amount of open and completed prediction units assigned to Tasks within it.
Using Comparing Capacity & Availability Across Resources
Now that we've assigned predictions to tasks and tracked them on Lists, we're able to compare the bandwidth of individuals.
Tracking Capacity in Workloads
Workloads is the weekly resource tracker that will show the capacity of members of your team. These capacities were determined when workspace and individual working hours were established.
Tracking Capacity in Calendar
In the Day view of your Calendar, select Group by: Assignee. Note that the Group by icon may look like a series of columns.
You can toggle on/off which of your team members you'd like to account for in capacity planning.
Additionally, ensure that Capacity is enabled under the Show icon.
Resource FAQs
> Why is 1 point commonly used as 1 day of work?
Tasks without start dates will reflect a duration equal to their amount of points in Workloads. So a task with 3 points will appear to last 3 days assuming no start date is given. Start dates override the Story Point duration in Workloads.
> Will Nifty prevent me for assigning over capacity?
While a member's capacity will appear in red once it is exceeded, Nifty will not prevent you from assigning beyond one's capacity.
> Can I remove weekends from my Workloads?
The Workspace Owner can disable Weekends from calendar and timeline views (which will also remove them from Workloads) from the Planning tab of the Workspace Control center.
> Do predictive values split amongst assignees?
Predictive values attributed in full to all assignees of a Task, with no option to distribute these points at this time.















