So let’s us show some new features in latest TP 2.0 Public Preview (as always, it is available online with any login and pasword)
Advanced and Saved Filters
One of the most helpful usability feature in latest release is advanced filtering and saved filters. Advanced filtering includes possibility to filter data very flexibly, while saving filters allows you to filter data, save current filter into the database and reuse it later when required. Also it is possible to set saved filter as default and it will be applied each time you visit the list. For example, you may create filters “All Not Closed Bugs” or “All Open Unassigned Bugs” and use them in all projects.
Another useful feature is multiple attachments on entity submission
They work without page reloads, so you may create a bug with five attachments if required with easy.
Drag and Drop Prioritization
The third feature is a drag and drop prioritization. In current preview this is just temporary demo, later we will combine prioritization with Plan Iterations tab to allow more actions from single place. It is very intuitive and works full on client without page reloads (very fast). This is the result of our long running “Drag and Drop Performance Optimization” activity.
Points Effort Units Support
And the next thing worth to mention is Point effort units support. In short, Points are relative abstract effort units that works great for experienced agile teams. Points are a relative measure of user story size. Usually they are used with discrete scale. For example: 1,2,3,5,8,13,20. This scale means that user story with 3 points is about two times simpler than user story with 5 points, no more. Estimation with points is easier, since you estimate-by-compare: "We'll give this story 2 points because it seems like it's twice as big as that 1-point story and about half as big as that 4-point story".
Many agile teams use Points (we are as well). The best examples and clarification of Points usage I’ve ever seen is in Mike Cohn’s book Agile Estimating and Planning. In general, it’s an exceptional book for every project manager and I highly recommend everyone to read it.
We are two iterations behind official release, so next iterations will be less feature-reach, since we should write documentation, create installer, fix some known problems and pass pre-release quality assurance activities. Keep reading us!