On this page we collect all expressed opinions (from outside the Agilefant Development Teams) on where the 'Fant should go and what should be included in future versions of the 'Fant!
The easiest way to express your opinion is to email team(at)agilefant.org. Please state the user need as well, not just 'Please implemennt get a button that does X'. Generally speaking, the better you formulate the request, the better chances it has of getting a higher priority.
Volunteering to help in the implementation (by pair programming or otherwise) is a good way to get your request upwards in the to-be-implemented stack (see the Roadmap).
Misc
"Assigned work-rappari" (undefined prio)
/ 14.4.2008 Vilant Systems
What is this? The same as Daily work + Load in 1.3.6?
Iteraatioiden end date voi ulottua projektin end daten yli (low prio)
"En testannut start-datelle, mahdollisesti sama juttu. Voi tietenkin olla että tossa on taustalla jokin logiikka josta
mulla ei ole käsitystä" / 14.4.2008 Vilant Systems
This is correct, we have not seen yet as necessary to prevent it. Will most likely to be fixed at some point. If you can tell why this is a (serious) problem, it may be be prioritised higher.
Daily workissa "show x weeks ahead" ei pidä arvoaan
/ 14.4.2008 Vilant Systems
Fixed in 1.3.6 (actually removed the feature as unnecessary).
Make scope changes visible in the burndown
"2) burn down graphiin scope näkyviin (eli näkee jos estimaatit paisuu tai assainataan lisää taskeja) (hi prio)
Yes, we agree this is important and have been thinking about it for a longer time now. However, addressing it is not in the current Roadmap, perhaps it should be.
Hour reporting -related
Generic comments regarding how-to-exactly (low prio)
"1) JIRA-tyypinen log work -toiminto: eli syötetään paljonko tunteja tehty ja mahdollinen uusi estimaatti paljonko jäljellä. Näin ollen myöskään original estimatea ei pidä pystyä muuttamaan. Näin säilyy alkuperäinen estimointidata."
/ 14.4.2008 Vilant Systems
We are planning not to couple the logging of work and estimating effort left too tightly. This is something that many systems do and we do not want to go in that direction. Estimating progress (i.e. effort left) and cost accounting / billing (i.e. in the form of logging hours spent) are philosophically quite different things, and while we want to support both, we don't want to make the same mistakes that have been made in the past. But, this will be further specified as we go nearer & into the Agilefant Spider project (see Roadmap).
The possibility to reset the original estimate will stay for the foreseeable future based on the assumption that Agilefant users have no motivation to make estimates look nice compared to the actuals.
Usability and interfaces (undefined prio)
"Tuntiraportoinnissa olisi hyvä olla sekä kätevä oma käyttöliittymä (laatusana kätevä tekee tuosta ei-triviaalin haasteen) sekä valmistellut rajapinnat työkohteiden ja niihin kytkettyjen aikakirjausten synkronoinnista ulkoisesta järjestelmästä, kuten CRM tai muu organisaation keskitetty ajanhallinta." -Terho / IPSS 14.4.2008
Reporting
Tehdyt tunnit -rappari (hi prio)
and
Raportti estimaattien tarkkuudesta
/ 14.4.2008 Vilant Systems
Will most be addressed in Spider (see Roadmap).
Adding responsibles for tasks (undefined prio)
Requested by Seppo Sahi / G-Cluster 14.4.2008
A couple of points for discussion on how this should work:
1) Should you be able to mark as responsible for a task
a) any user? if so, should he be assigned to the backlog item as well?
b) only those users that have been assigned to the project?
c) only those users that have been assigned to the backlog item?
d) other?
2) Should these somehow be reflected in the Load calculations?
Currently, the effort remaining for a task is split evenly among those responsible for it. We think that this would be the way to do it also in the future, but are asking your opinion for the sake of argument.
Please comment directly here!
Development portfolio management
Users need to see whether the ongoing projects are in trouble