Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Breakdown HUU Project Milestones to be more granular #741

Closed
5 tasks done
lasryariel opened this issue Aug 14, 2024 · 5 comments
Closed
5 tasks done

Breakdown HUU Project Milestones to be more granular #741

lasryariel opened this issue Aug 14, 2024 · 5 comments
Assignees
Labels
Complexity: Medium Issue is clearly defined and documentation is provided. Solution has room for interpretation. Feature: Administrative Administrative chores, etc... points: 0.5 Can be done in 1.5 to 3 hours Ready for: Dev Lead Issues which need review by a Dev Lead before it is ready for the Prioritized Backlog Role: PM

Comments

@lasryariel
Copy link
Member

lasryariel commented Aug 14, 2024

Overview

To enable clearer planning of issues, the PM team will work with the Engineering team to define sub-milestones for MVP.

Action Items

  • PMs meet with Engineering Leads to discover their recommendations for milestones
  • Potentially include the high level figma flow sections as sub-milestones
  • MVP phases
  • User Flow Sections
  • Engineering Milestones

Resources/Instructions

@lasryariel lasryariel added Role: PM Feature: Administrative Administrative chores, etc... Complexity: Medium Issue is clearly defined and documentation is provided. Solution has room for interpretation. points: 0.5 Can be done in 1.5 to 3 hours labels Aug 14, 2024
@lasryariel lasryariel added this to the y - Cleanup milestone Aug 14, 2024
@lasryariel
Copy link
Member Author

@erikguntner @tylerthome would it be possible for one of you to provide your thoughts on what sub-milestones we should add to the project?

It would be great if we can have your initial thoughts and then we could put it on the agenda for a team meeting.

CC: @lola3736

@erikguntner
Copy link
Collaborator

@lasryariel Definitely! We discussed two sub-milestones that we believe are attainable:

  1. When a guest is invited by a coordinator the guest and all other users currently in the system can be viewed from the dashboard along with their current status.
  2. A guest can fill out and submit their intake profile and have their status updated.

Ideally, these two milestones together will get us to a place where a coordinator can invite a guest -> that guest can accept the invite and fill out their intake profile -> A coordinator can view the guest's progress from the dashboard -> the status updates are reflected in the guest's dashboard.

How does that sound? Happy to answer any questions.

@lasryariel
Copy link
Member Author

@erikguntner to be clear for number 1: you mean that all users can be seen from the Coordinator Dashboard right?

I like these milestones, but wonder if they are too granular. I'm inclined to go this granular but let's bring it up for tomorrow's meeting.

@lola3736 please would appreciate your thoughts on adding this level of detail to our milestones.

@erikguntner
Copy link
Collaborator

erikguntner commented Aug 20, 2024

@erikguntner to be clear for number 1: you mean that all users can be seen from the Coordinator Dashboard right?

@lasryariel Right. In this case all of the Hosts and Guests.

I like these milestones, but wonder if they are too granular.

We could broaden them to larger features like the Guest Dashboard, Guest Intake Profile, and Coordinator dashboard. These have the most work in progress. Maybe we identify the most crucial features for each in order to narrow things down a bit?

@lola3736
Copy link
Member

@erikguntner @lasryariel Thanks for providing the initial milestone proposal. We are on the right track; we don't want it too granular nor to high level. Each milestone should be considered a major deliverable to be viewed with our stakeholder (Boonie) and enable us to gauge where we are in the project. The following proposal might work but we need to look at the whole flow to determine the right level of milestones. To ensure we continue to focus on work to be delivered, I will take this on as part of project management and provide a proposal for us to review:

  • Six sections to create the end-to-end workflow:
    • Section 1: Account Creation
    • Section 2: Application and Onboarding Process
    • Section 3: Matching / Relationship Creation Process
    • Section 4: Relationship Management / Monitoring
    • Section 5: Relationship Termination Process
    • Section 6: Special Cases
  • For each of these sections, we need to determine the milestone delivery, might be easy to determine if we identify the tasks.
    Welcome your thoughts.
    CC: @tylerthome

@lasryariel lasryariel self-assigned this Aug 23, 2024
@lasryariel lasryariel mentioned this issue Aug 23, 2024
38 tasks
@lasryariel lasryariel added the Ready for: Dev Lead Issues which need review by a Dev Lead before it is ready for the Prioritized Backlog label Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium Issue is clearly defined and documentation is provided. Solution has room for interpretation. Feature: Administrative Administrative chores, etc... points: 0.5 Can be done in 1.5 to 3 hours Ready for: Dev Lead Issues which need review by a Dev Lead before it is ready for the Prioritized Backlog Role: PM
Projects
Status: Done
Development

No branches or pull requests

3 participants