Skip to content

How is the team's work organized?

kyle-hauber edited this page Feb 3, 2020 · 5 revisions

How is the team's work organized and tracked?

There are several levels at which our work is being of organized and tracked. We're using Issues and Milestones to complete our Project. Below is an outline:

Issues:

  • Link: https://github.com/CodeForPhilly/prevention-point/issues
  • Description: Issues are tasks that can be accomplished by an individual contributing to the project. Multiple Issues make up a Milestone
    • Issues are akin to stories or tasks for those used to working with agile development methods or other project management platforms, such as JIRA
    • Every issue will have a tag indicating which team owns it: backend, frontend, product owner, or UX

Milestones:

  • Link: https://github.com/CodeForPhilly/prevention-point/milestones
  • Description: Milestones are made of multiple Issues and represent individual components of the overall Prevention Point System. Once complete, that component should be fully functional. Each Milestone has a corresponding tag, which can be viewed in the Project Board. For example, there is a Milestone for the Login Page, as well as a pink tag called "login page" (check it out here!)
    • Milestones are akin to epics for those used to working with agile development methods or other project management platforms, such as JIRA
  • Owners: Each Milestone will have at least 4 key Issues, representing a contribution from different team functions. These are outlined below and have corresponding tags on each Issue, so the Issue owner can be easily identified
    • Product Owner: Should include the user story and acceptance criteria. This will serve as a reference for sign off on completion of the Milestone
    • UX: Should include any mocks needed to complete the milestone
    • Frontend: Front end issues will be broken out based on the user story and UX, so that an Engineer can build the front end component of the Milestone
    • Backend: Front end issues will be broken out based on the user story and UX, so that an Engineer can build the front end component of the Milestone

The Project Board: