We are pleased to present you with the latest release of the Project TimeLine. In recent months our team worked hard to improve the usability and allow managers to take full advantage of forecasting and reports that Project TimeLine offers.
To make sure you and your team deliver on every goal, Project TimeLine allows for easy and convenient planning of Jira Epics. You can now schedule your Epics on the TimeLine and get automatic predictions of completion date plus early warnings of possible delays.
Until this release planning was only available for Releases. Now managers can set start and end dates for Epics and track elapsed time vs work completion. Teams that estimate issues and know their velocity - can also get a prediction of when an Epic will be completed with the given speed of work.
Handling unestimated issues
Configure how you treat unestimated issues
With the extended configuration options and improved UI - now managers can know better the impact of unestimated issues on their plan. Project TimeLine offers two options for unestimated issues:
Leave issues unestimated and get an indicator about the count of unestimated issues (e.g. Epic is 24% but there is 1 unestimated open issue)
Configure a default estimate and get a better preview of the volume of work (e.g. set a default of 8h for any issue that does not have estimate - will provide better estimate of the volume of work than leaving the tasks not estimated)
The last option is to not use estimates at all. If your tasks are relatively the same size and your teams do not estimate them, now you can also track progress by monitoring the count of resolved vs not resolved issues
Number of unestimated issues
The clear indication of the number of unestimated issues helps you understand how reliable the progress indicator is.
For example: if only a few issues are not estimated, then 90% looks good; if most of the issues are not estimated and just one issue is resolved: 100% doesn't mean that most of the work is done.
Whole New User Experience
Project TimeLine user experience keeps getting better.
Better overview of the schedule
For every Release/Epic you see:
% of elapsed time: this makes it easy to compare elapsed time with work done and get an indicator for delay
Working days passed: how many days have elapsed since the scheduled start
Working days left: how many days the team has to complete the work in time
Apply different colors to visualize your elements and reduce the time to insight
You can configure different colors to quickly distinguish Epics or Projects on the timeline.
On our roadmap, we strive for making Project TimeLine a great value for both Product and Service teams.
For Product Teams - extended support in Sprint and Release planning:
Resources available to participate in the next Sprint/workload
Vacation's impact on the velocity and on the Release date
For Service Teams (e.g. consulting companies) - better overview of resource utilization:
How are resources distributed among multiple projects
Which resources are over/under utilized
When is the best time to start a new project
Support of Business/JIRA Core projects
Tracking of checklists on Release level (Definition of Done)
If you know what your needs are and would like to share them with us - feel free to contact us!
A tree view of issues in Release/Epic
Support of Server Hosting
Scope Filtering by Status Category
How many Stories can be added to a Release so that it is feasible?
Stories are below the line and don't fit in a release?
Forecasting the calculated end date
Early warnings if the implementation is going slower than planned
Is the velocity slowdown a trend that may lead to delays?
Is there scope creep?
Sprints on timeline
Change of scale - weeks, months, quarters
Ability to change schedule - drag & drop Releases and Epics on the timeline