Skip to content

Latest commit

 

History

History
55 lines (45 loc) · 2.86 KB

SprintTwoReport.md

File metadata and controls

55 lines (45 loc) · 2.86 KB

Sprint Two Report

Allay

Sprint Completed November 5th, 2018

Actions to Stop Doing

  • As a team we need to stop waiting so long to speak up when we are blocked because we are waiting for another member to finish their tast.

    • Sometimes it's not always clear which tasks rely on others being done, so if we find that we need another person's task to be completed to move forward we need to stop waiting so long to speak up.
  • We need to stop relying on teammates to answer all questions that we might have.

    • We are all new to this type of work, so instead of expecting our group members to fix our errors we should start researching how to fix it ourself.

Actions to Start Doing

  • We should start setting specific hours each day that we work on the project.

    • This may be difficult due to our ever changing work loads, but we should try to block out certain hours each day to always work on the project.
  • Each of us should start picking up tasks that need to be done, even if they aren't assigned to us.

    • Some people might have a lighter work load during a given sprint, and if that is the case they should pick up extra tasks even if they weren't originally assigned to them.

Actions to Keep Doing

  • We should keep up the effort that is being put forth.

    • Relative to the first sprint, there is much more effort going in to the project by most all of the members. We should keep this up in future sprints.
  • Overall communication has gotten much better, so we should keep this up.

    • Although there is always room for improvement, we should at least continue communicating at the current level.

Work Completed/Not Completed

  • Work Completed

    • Maintain login information in our database, so that the user can sign in and out.
    • Create a list of symptoms in our database to populate a list for our user to pick from what they want to track.
    • Set up base code that will be built on top of (with front end and back end communicating).
    • Build main layout of app (color scheme, background).
    • Build login UI component.
    • Design component piece for symptom cards (i.e Depression, Anxiety, Sadness).
    • Design component when user clicks on symptom to enter measurement.
    • Design component for showing previous symptom measurements.
    • Build register UI component.
  • Work Not Completed

    • Build password reset UI component.
    • Build register UI component.
    • Build symptom card UI component.
    • Build symptom measurement input card.
    • Build tracked symptom history log card.
    • Connect measurement value entered by user and current date to database to be accessible for later retrieval.
    • Resend email verifications( focus on UI component)

Work Completion Rate

  • Stories Completed
    • As someone first coming to the webapp, I want an easy way to make a profile.
  • Time Stats
    • 14 days in this sprint.
    • 42 total hours
    • .5 User Stories/ Week
    • 3 hours/day