Features?
malclocke
So, what features do people want to see, and in what priority?
The features that are under active development at the time of writing
are:
- Backlog iterations
- Comments
Malc
roovo
> Hi,
>
> So, what features do people want to see, and in what priority?
export seeing as there's an import...
I've got fulcrum up and running in dev mode on my mac at home but I
may want to set up a production instance where I can get at it when
I'm not at home so when the time comes to be able to export the
stories from my dev setup so I can import them into the production
instance.
I don't see this as hugely high priority ....although if this was in
place I guess it would mean that story information could be imported
elsewhere for analysis so if peeps wanted to make charts or do some
crunching to work out stats on progress they could.
Cheers
roovo
malclocke
Fulcrum currently looks like this (minus bugs and sundry bits and
pieces):
- Project velocity is displayed prominently
- A user should be able to set the starting velocity for a project
- A user can add comments to a story
- A user can export a CSV
And currently unprioritised in the chilly bin, but definitely to be
implemented:
- A user can add labels to a story
- A user can view story change history
- A user can add attachments to a story
- Full story details are visible in a pop-up
- A user can show and hide individual columns
- A user can search for stories
- A user can perform common actions with shortcut keys
I'd like to make this publicly visible, but for that I'd need to
implement 'An unauthenticated user can view a project in read-only
mode' first :)
I'll have a think about it and maybe bump CSV export up the list,
Malc
Fer Martin
config/initializers/devise.rb: config.email_regexp = /^([\w\.%\+\-]+)@heypal.com/i
Gabriel Fonseca Engel
User roles would be useful:
- an unprivileged customer cannot create projects
- the project creator cannot be removed from the project
- the project creator should be the only who can add members
On Sep 8, 11:30 am, Fer Martin <fernandomartinsant...@gmail.com>
wrote:
>
> At Heypal.com we've been using Fulcrum for a good 2 weeks now (deployed in
> Heroku) and we really love it. Congrats!
>
> I also modified the source so that only emails from our domain could
> register... in case someone finds it useful:
>
Edwin Cruz
- More than one owner per story (we're still trying to figure how to work with this out, we do pair programming)
- Add ability to change velocity
- Add autocomplete for members and labels
- Add filters to project stories (search)
- Limit users to certain domain(s)
- Add attachments to stories
- shortcut keys
- Labels
- Hide/Show columns
- Time tracking
- Bulk stories update(specially when assigning labels)
--
Edwin
Gabriel Engel
Edwin Cruz
Cheers!
--
Edwin Cruz
CrowdInt.com
Malcolm Locke
> Interesting points, here's our current wishlist, it looks like
> this(unprioritized):
> - More than one owner per story (we're still trying to figure how to work
> with this out, we do pair programming)
That's an interesting one. How do you manage your commit messages?
Will have a think about this, multiple owners may be a valid option.
You'll still need to log in as a single user, but maybe an option
somewhere to select "I'm pairing with ...". Or perhaps the ability to
create 'virtual users', which are a composite of two developers on a
project.
> - Add ability to change velocity
> - Add autocomplete for members and labels
Labels yes, members I don't think so. It exposes the whole apps user db
to potential scraping, which won't be favourable for multi tenanted
installs.
> - Add filters to project stories (search)
> - Add attachments to stories
> - shortcut keys
> - Labels
> - Hide/Show columns
> - Bulk stories update(specially when assigning labels)
Yup, all of these will be going in over time.
> - Limit users to certain domain(s)
What about product owners? Customers?
> - Time tracking
This one keeps coming up. I'll think some more about it. My main worry
is still that different people like different styles of time tracker,
and they always need to integrate with invoicing. I think it's far
better to implement an API in Fulcrum that people can integrate with
their preferred time tracking tool.
Malc
Malcolm Locke
> Hey Edwin, What about burndown charts?
Hi Gabriel,
Yeh, I'd like to eventually add the full gamut of agile charts, burn
down, burn up, story type breakdown, etc.
If we do end up implementing time tracking then some other interesting
options for reports come up. Deviation between estimate / work, stories
with the highest deviation. I think this would be really helpful
retrospectively for teams to improve their estimation.
Malc
Gabriel Engel
Malcolm Locke
> Hi Malc!
>
> 1 - Couldn't the burn down/up charts be based on activities points? I know
> time is also key factor, but it can be done apart or even applied over the
> estimated points.
Yup, burn down/up is always done against story points.
Having time tracking allows you to pull out some interesting metrics
that aren't otherwise available.
For example, you could calculate how much work the average story point
actually took to complete. Then you could retrospectively look at the
real vs estimated times for all the stories, and see which stories had
wildly incorrect estimates, and then work on improving your estimate
process. "Hey, look, all the stories related to facebook integration
were grossly underestimated because we didn't realise we needed to do
x".
> 2 - About the time tracking, it should certainly get an API. Yet the most
> basic (manual) form of it should be made available (inserting & editing
> start and end times).
This is what I mean about peoples different expectations for time
tracking, because for me the simplest system is to enter "2 hours on
story xxxx on Sep 13th" :)
People tend to have a preference for 1 of 3 different styles:
- A start / stop timer that records in realtime
- A start time / end time system
- An 'I spent x hours today on y' style system, without explicit start
and end times.
So personally, I'd rather spend that effort on implementing Pivotal
Tracker API compatibility, and a separate tool to track time which is
compatible with that API. Then that tool will have exposure to all the
PT users as well.
> 3 - Also, I don't know about you guys, but as I work on a portfolio that has
> interdependent projects, I have to open each project to see what tasks are
> assigned to me. How about having "your tasks" in the portfolio (index)
> screen?
Personally I block time out to work on no more than one project per day.
But a 'my tasks' overview could be useful.
> By the way... is there a Fulcrum to manage Fulcrums development?!
There is! And once we have public read only view implemented it will be
visible to all.
Malc
malclocke
> Having time tracking allows you to pull out some interesting metrics
> that aren't otherwise available.
>
> For example, you could calculate how much work the average story point
> actually took to complete. Then you could retrospectively look at the
> real vs estimated times for all the stories, and see which stories had
> wildly incorrect estimates, and then work on improving your estimate
> process.
with an
example of the kind of graph we could include if we had time tracking:
http://blog.mountaingoatsoftware.com/seeing-how-well-a-teams-story-points-align-from-one-to-eight
Malc
Edwin Cruz
we manage our commit messages using git pair (pivotal git scripts)
Yes, we've been thinking how it could be managed, specially when rotation comes before the current task is done
Can I get an invitation to the main fulcrum project?? We'd love to put some efforts and we dont want to overlap work.
Thanks!
--
edwin
Malcolm Locke
> Hi Malcolm
>
> Can I get an invitation to the main fulcrum project?? We'd love to put some
> efforts and we dont want to overlap work.
Hi Edwin,
I don't think I'm going to be giving invitations to the main project any
time soon. Fulcrum is really optimised for small private projects at
the moment. We will get to the point where you can run an OSS project
with it I'm sure, but we're not there yet.
Here are the current major work points in the backlog:
- A user can add comments to a story (this is in progress)
- A user can export a CSV
- Full story details are visible in a pop-up
- Anonymous users can see a read only view of a project
- A user can add labels to a story
- A user can add attachments to a story
- A user can view story change history
- Invalid fields should be disabled when editing a bug
- Invalid fields should be disabled when editing a chore
- Invalid fields should be disabled when editing a release
- A user can set a deadline date on a release
- A user can search for stories
- A user can use shortcut key A to add a story
- A user can change project velocity (display only)
If you want to take on one of these features, please do the following
(I'll add these instructions to the README):
- Add an issue to the github issue queue with the title of the feature
you're working on. Make sure you check there first before working on
something. I'll start adding issues for the major features I'm
working on.
- Optionally announce your feature on the fulcrum-devel mailing list.
- Feel free to send pull requests of your work in progress on a feature
for review by other developers.
- Send a pull request when you're done.
If anyone wants to implement 'Anonymous users can see a read only view
of a project' then I can make the project backlog publicly visible.
I await the flood of beautifully coded, fully test-covered pull requests
with baited breath :)
Malc