Ticket #6 (closed task: fixed)

Opened 14 years ago

Last modified 14 years ago

Initial user story list

Reported by: tarmo Owned by: tarmo
Priority: major Milestone: 0.0.1 Initial design
Component: generic Version:
Keywords: Cc:
Time planned: 20h Time remaining: 0h
Time spent: 46h

Description (last modified by tarmo) (diff)

Based on the results of the design sessions (#5), a list of features is built in the form of user stories, first drafts and then as tickets (type: story) in this Trac system. These items are then prioritized and the most important ones will be chosen for Sprint 1.

Change History

comment:1 Changed 14 years ago by tarmo

  • Time planned set to 20h
  • Description modified (diff)
  • Summary changed from Initial prioritized product feature list to Initial user story list

comment:2 Changed 14 years ago by tarmo

  • Description modified (diff)

comment:3 Changed 14 years ago by tarmo

  • Owner changed from teemu to tarmo
  • Status changed from new to assigned
  • Time remaining set to 15h
  • Time spent set to 5h

Some user story -like text snippets have been appearing in the wiki. Thanks for all contributors! We still need to refine them so that they are actual user stories: most importantly we need to be able to split them into tasks that are doable in hours (not days or weeks) and each story should be completable in under a week. Some stories need to be toned down quite a bit. More extreme features can be listed as "nice to have", but aren't a priority at this point.

comment:4 Changed 14 years ago by tarmo

  • Time spent changed from 5h to 40h
  • Time remaining changed from 15h to 6h

Lots of group work completed, and many user stories are now in the ticket system: {10}. Some areas are still not covered, and the stories should be estimated and prioritized.

comment:5 Changed 14 years ago by tarmo

  • Status changed from assigned to closed
  • Time spent changed from 40h to 46h
  • Resolution set to fixed
  • Time remaining changed from 6h to 0h

Done. The list is not complete, but enough so that work can begin.

Note: See TracTickets for help on using tickets.