Proposal: Adding user stories for building up the roadmap

[carlomigueldy]

As per feedback from @with-heart during the call from last Friday, to build out an MVP we need to setup a clear goal on what we want to achieve, what certain functionalities should be shipped, and know what exactly are we building.

I had a slight conversation with @angeljgomezc and I proposed that we'll use of "User Stories" for defining a set of functionalities that we want to ship for the MVP.

We basically just create a bullet list of single sentences/phrases on what we want to expect or what certain functionalities we want to have in the app

e.g.

• As a developer I want to browse jobs/gigs that I am interested in
• As a developer I want to setup my profile, upload photo, update my description, username
• As a developer I want to send job applications to job postings
• As a developer I want to create gig postings
• As a company recruiter I want to create job postings
• As a company recruiter I want to receive job applications from developers

Personally I think these would helpful for someone that wants to contribute into the project.

But if there would be any other suggestions than this, please share it with us we would be happy to learn more about it :)

[with-heart]

Yes yes yes yes yes yes yes! I love this issue!

I do want to emphasize the importance of the "[so that]" part of the user story though. It's important to understand why the user wants a feature as much as what the feature is because it helps us make sure the features we build actually accomplish the user's intent.

An example:

As a company recruiter, I want to receive job applications from developers

Solution: Let's create a page that lists every submitted developer application

As a company recruiter, I want to receive job applications from developers, so that I can hire the most qualified developers with skills relevant to the position

Solution: Let's create a page that lists every submitted developer application. We should order the list so that applications from developers with skills relevant to the position they're applying for are at the top.

Both solutions technically implement the requested feature, but because we've thought about user intent, the second solution is likely better for fulfilling the user's needs.

[carlomigueldy]

Yes yes yes yes yes yes yes! I love this issue!

I do want to emphasize the importance of the "[so that]" part of the user story though. It's important to understand why the user wants a feature as much as what the feature is because it helps us make sure the features we build actually accomplish the user's intent.

An example:

As a company recruiter, I want to receive job applications from developers

Solution: Let's create a page that lists every submitted developer application

As a company recruiter, I want to receive job applications from developers, so that I can hire the most qualified developers with skills relevant to the position

Solution: Let's create a page that lists every submitted developer application. We should order the list so that applications from developers with skills relevant to the position they're applying for are at the top.

Both solutions technically implement the requested feature, but because we've thought about user intent, the second solution is likely better for fulfilling the user's needs.

Thank you so much for the suggestion we've been referring on this when writing up & finalizing the RFC!

[carlomigueldy]

Closing this issue now since the RFC has been created.

https://forum.developerdao.com/t/rfc-user-stories-for-dao-job-board/507