Agile Project Tracking

1. LiteTracker allows teams to break work into parts that are smaller increments. It prioritizes tasks and revises plans based on feedback and progress. By visualizing work in progress, teams can identify bottlenecks, maintain transparency, and promote sustainable development.

Stories

1. Projects are broken down into smaller parts, called stories. They identify every individual piece of work that needs to be completed under a project. Each of them defines a particular feature, enhancement, or bug fix in the overall development of the software.​

Epics

1. Epics are some large work units covering multiple related stories. They help put work into larger categories and are helpful in managing long-term initiatives. Teams break epics down into smaller stories that are manageable so that the progress becomes incremental and trackable.

Backlog and Icebox

1. Backlog prioritizes a list where high-priority tasks or stories that are planned for the forthcoming iterations of work can be taken care of first, or left to themselves. It helps in conditioning planning into importance and urgency.
2. Proposed ideas for future enhancements or tasks with low priority are stored in the icebox. The team may analyze these items later and move them into the backlog when they become relevant.

Team Velocity Tracking

1. Teams can gauge how much work they get done in any iteration by using velocity tracking. The system measures velocity by looking at completed tasks and gives insight into the performance of the team. This lets us estimate future workloads and plan the next several sprints.

Iteration Report

1. Iteration reports summarize the work accomplished and the work that is still pending in each sprint or iteration. They include metrics such as velocity, completed stories, and blockers that have been faced. Teams then use these to gauge their progress and reflect on difficulties that were faced so as to make data-based judgments for planning their future work.