This gist details the decisions I made, the tests I conducted, the observations recorded, and the directions I took while building out a website for Book Squid.
Create a webpage that allows for a user to log into their personalized account, which includes adding books to their own reading lists and rating/reviewing books that they've read.
Today, our team spent time talking about roles (Program Manager, Architects, UI Owner) and the first steps of designing Book Squid's book-tracking website. I spent time with my fellow Program Manager on what the user stories would be and figuring out what features were essential vs. stretch goals.
Take the conversation with Book Squid's founder and begin fleshing it out into a concept that can be created by the end of next week.
Created a Trello ticket system for this project and began designing tickets that reflected the user stories. Each user story had 1-2 inputs that would produce a simple output.
Breaking down the features of this reading app into user stories made it much easier to picture how a user was supposed to be able to navigate from one page to another, and what they should be able to do within each page. My one concern is in making sure that the entire team is on the same page about what can be accomplished within the week that we're given, especially when we'll expect to have a feature freeze next Wednesday.
Worked with Hayden to finish user stories, connected with the UI owners to clarify on what the header would consist of, then ran it through with the architects to get a better idea of what the backend would need to be able to provide.
Adjust the user stories and create a READ.ME template to update throughout the project.
I walked through each page designed by the UI owners alongside Hayden, and we filled out the Trello tickets that would eventually create all of the user stories required by the client. For the READ.ME, I included the installation instructions created by Michael, and referenced any documents/resources that we are referencing off of.
Everyone is now on the same page with what user stories are the highest priority, as well as an easy way to select a ticket that asks for a simple function to be completed. This will make it possible to begin making unit tests!