Open Oliversw opened 5 years ago
No issues today! Worked on Figma in the morning and in the afternoon we had a London workshop.
Continuing on developing the Figma, and potentially doing user testing in the evening.
Not really, just need to get our ideas down on the page. One potential blocker is not knowing what comes after the priority / timeline table.
prototype issue, In the morning, check the docs and then worked on the prototype by using the Figma platform.
continue work on the prototype and check everything to be ready for user testing on Friday.
I still need to know the end of the flow of prototype, what will happen after the table!
Checked the newly updated docs and then worked on Figma.
continue to work on Figma.
Still not knowing the end flow of the app.
Communicated with David and got him set up on Github Scrum research to better communicate his responsibilities Afternoon workshop took up a lot of our other time!
Prototyping, making sure that we have all of the information that we need from David Introducing him to user journeys and stories
Clarity of information about the app - but working on it!
Continued to work on Figma. After we sent the initial prototype, I created draft pages for the hamburger menu, 404 & 500 error pages, as well as an alert page for when you haven't 'spent' all your resources. An interim placeholder page was also created to provide information between the 'choose' and 'prioritize' sections.
Tomorrow, I will look into what's the best way to display the information after prioritising and timelining (perhaps one line graph and one circle graph?)
Also need to figure out system for including more documentation. (A-Z, etc).
Just the regular, time and energy 🤙
worked with Hannen on Figma
on Sunday, Planning to view the feedback from David on Figma and make some improvement, also prepare the setup of the project (DevOps) so, we can start coding on Monday
My lack of Design eye :)
Worked on Figma Communicated with David
Assess feedback from David and begin to draft user journeys and stories Begin to write issues for basic setup of repo
Having a final design and user journey defined
Worked on Figma
waiting for feedback from David and solve the requested change.
nothing until now.
Made updates to style guide issue to represent the figma better. Still not totally complete (some font tags are not yet defined) #5
Created a new summary page with potential graph of method selections
Had a meeting with David concerning testing. Please see issue #8 for synopsis
Created user journeys / stories. This needs to be reviewed and turned into issues for the kanban. #6
Went through prototype feedback from David Meeting with Kristina and David to talk about the feedback. See #8 Created draft user stories and Journeys. See #6 Created issues for To Dos on Figma #9 and basic project DevOps setup #10 Added some Quip docs to project repo for documentation #11
Creating issues from the agreed upon user stories so that we can start coding!!
Having the user stories converted into issues
Went through the new doc and feedback that David provided us after the user testing. worked on To Dos on Figma #9. start basic project setup (create-react-app, eslint, travis) #12
add codecov and try to deploy on Heroku. review the user stories with the team to start coding
none :))
check the hackdmd that @teenie-quaggard @Oliversw sent to us worked on the issue 'To Dos on Figma' #9. help @ali-7 to create the setup for project #12
checking user stories and start coding after Ali finish from configurations.
none :))
Help Ali to finish from configurations check user stories and figma for last time.
start coding. maybe start with a landing page and error pages (404, 500)
deploying on Heroku without server
Reviewing and closing old issues Reviewing all the documents that David has provided
Potentially breaking up the journeys more into issues Setting up kanban Picking up an issue and working on it
I am feeling a bit lost in how the user stories / journeys are developing...
continue to set up the project, code coverage and heroku
checking user stories issues, and see if they need more splitting, and pick one and start coding
deployment problems
Re-evaluating user journeys and stories Making issues Set up automated Kanban
Continue working on issues after getting feedback from team Some kind of component issue
Figuring out the best way to break everything down into issues
read about styled-component, testing react component, deploy the app on heroku, upload some file structure
work on header component for now
none :)
draw key terms page on the figma, set up the basic style for the app., create a folder for assets we will need it. check styled component docs.
work on footer
none.
finished setting up some issues read through documents from PO and asked for clarifications banner components #31
fix npm start bug #38 finish banner components #31 try and design more clear indication of what copy we need from PO, e.g. exactly what is on cards
npm start bug
finished Header component
work on linking header component and menu. put Header on all views, pick up a new task
still learning styled Component
Footer component
put Header and footer on all views and finish about page.
none
put Header and footer on all views and finish about page.
finish all views in the menu as static data, I will start with 'Choose your gameplay:'
none.
linking menu to header
views and pick up a new task
didn't refer to react-burger-menu documentation from the start
Capitalization issues with Github Code review Banner component, landing and 404 pages
Reprioritize issues
Refactoring footer Connecting existing pages Some review of issues
Break methods page and prioritization page into smaller, achievable issues Try to have a static version of every page up and connected Work on section of methods page
No
-Created a reusable card component -Started on finishing initial version of methods page which renders one card -Found https://www.npmjs.com/package/nuka-carousel which I will try and implement tomorrow
Trying to pass the resource cost of each individual card to the methods page so that it can be subtracted from the resources in state
Scenario selection page #18
start work on #19 Scenario/Persona/Challenge page
none
code review, BannerFooter component, Error404 route
see what left of the static page, and move to the dynamics
No
Implementing carousel and working on methods page
working on updating resources when checkbox is checked on individual methodcards
yes, this resource function is driving me mad!!!
Creating summary page #24 Working on summary timeline #68
Finish summary timeline (Hopefully!!)
No
working on methods page -updates state in methods when cards are checked -implement error page when resources are overspent
-implementing error page when resources are underspent and user presses next -implementing mini carousel showing selected methods
finding out how to target an onclick event on next button in methods
Scenario selection page #18
Scenario/Persona/Challenge page #19
none
finished from the scenario and challenge views.
work on the same issue -create persona selection
none
work on the same issue -create persona selection
key terms page.
if we need to filter methods depends on the method that the player select !!
The Summary page and timeline ... almost finished!
Finish off timeline!! Maybe begin on responsivity?
Summary page will depend slightly on how it is passed state
In this issue, at the end of each working day, please add a comment answering the following questions. These will form the basis of the standup meeting each day:
Date:
What issue(s) did I work on today?
What issue do I plan to work on tomorrow?
Am I facing any blockers?