Task Tracking - lmucs/grapevine GitHub Wiki

Example of User Story Mapping

Task Tracking Service

We needed an agile-driven, free, task tracking service that would allow our team to write user stories, manage sprints, and graph progress.

Rally

We originally started our task tracking in Rally, but we thought the UI and features were overly complicated for our team and tasks. We liked the functionality of being able to create hierarchical user tasks and epics, so we looked for that when researching other task tracking services. However, we decided we didn't need to use the business planning functionality of Rally, so we chose to go with Pivotal Tracker instead.

Pivotal Tracker

We switched to Pivotal Tracker because it kept the functionality of adding user stories within epics, but simplified the user interface so our team could immediately start using it quickly and efficiently. It also stripped the task tracking environment to just the essential fucntions we liked in other task trackers (user stories, epics, backlog, velocity graphing, release deadlines).

Agile Development Resources

Example user stories

Format: As a <type of user>, I want <some goal> so that <some reason>.

  • As a power user, I can specify files or folders to backup based on file size, date created and date modified.
  • As a user, I can indicate folders not to backup so that my backup drive isn't filled up with things I don't need saved.
  • As an author, I want the spell checker to ignore words with numbers so that only truly misspelled words are indicated.
  • As a book shopper, I can read reviews of a selected book to help me decide whether to buy it
⚠️ **GitHub.com Fallback** ⚠️