Stay on top of your projects with minware's reports for tracking project costs for R&D and cost capitalization, as well as project size, health, and completion trajectory.

Track costs, project health, and completion trajectory with minware's project and cost reports.

The project cost allocation report automatically calculates where people are spending their time based on a combination of signals from assigned tickets and coding activity linked to tickets.

The report displays the total amount of time spent on tickets aggregated by their project, as indicated by the parent ticket, which is often referred to as an epic.

You can easily customize the report to add grouping by team or person to see more detail about how to allocate costs.

The report displays time spent in developer-months to make it easy to use the output of this report for allocating development costs in accounting system journal entries by multiplying the developer-months by salary costs.


Project Cost Allocation Report Screen Shot

Project Cost Allocation

View time spent on each project to see where your development costs are being allocated.

Costs

Projects

Tickets

This report shows you key project completion trajectory metrics all in one place.

First, it displays the total scope of an epic in story points so that you can easily see scope creep over time.

It also shows the burndown and burnup of epic story points that have been completed and are still remaining as the project progresses.

Finally, and most importantly, it also shows you how much development effort has gone into the project. It displays dev effort side-by-side with story point completion so that you can easily spot changes to velocity, which may indicate technical debt or other blockers.

Together, these metrics help you assess when a project is likely to complete and identify problems early before they result in missed deadlines.

With the inclusion of dev days, you can quickly tell whether drops in project velocity are a result of estimation problems, or if developers have simply spent less time on the project, possibly due to distractions or work misallocation.

The report also lets you drill down into each metric by person so that you can tell who has the most workload, and is joining the project or being pulled away.


Project Completion Tracker

See project completion trajectory at a glance with story point burndown, scope creep, and dev effort in one place.

Estimates

The Work Batch Size report automatically calculates information about the amount of development time put into each branch, ticket, and epic.

Development time is calculated by allocating work hours between commits to the commit that follows. So, if you work 9-5 and commit at 1 PM and 5 PM, the 5 PM commit would be counted as one half day of development time.

The report shows three things:

1. The percentage of time spent on small, feature-specific branches.
2. The percentage of time spent on tickets with less than one week of development work.
3. The Dev Work Days associated with Epics.

You can easily customize the report to filter by team or person to see more detail on how well various groups perform on these metrics.

The scorecard metrics use a threshold of 5 dev days for considering a branch of ticket to be “small.” The reasoning is that with a two week sprint, a ticket or branch that takes more than one week of active development time will take up more than half the sprint and should be broken down into smaller tasks.

There is no threshold associated with epics, but you can sort the results to view the largest epics with this report.

Smaller is almost always better when it comes to batch size, and these signals provide important information about batch sizes:



1. A high number on Task Specific Branches indicates that branches have small changesets. This makes it easier to review code, have a working central branch for features/projects, and track which tasks are associated with each branch.
2. A high number on No Omnibus Tickets indicates that tickets are generally small and require less than one week of work. Small tickets are easier to understand and estimate, and have a higher chance of being delivered as expected. 
3. Epic size is important as well. Similarly to small tasks, small epics are easier for everyone to manage.

This report is useful to engineers, team leads, engineering leaders, and product managers to reason about the size of batches of work moving through the system.


Report Templates: Project and Cost

Project Cost Allocation

Work Batch Sizes

Project Completion Tracker

Didn’t find what you were looking for?