Task: Update Readme end Sprint1
DeeMcCart opened this issue · comments
EPIC: #10
As a system owner I incrementally document the app's READMe to avoid huge task at end of project, and make system maintenance easier
Assumptions or Pre-Requisites:
- The project is ongoing over 4-5 weeks worth of 1-week sprints
- Completion of each sprint delivers some features and completes some user stories
Acceptance Criteria: (Must be completed before task is moved to 'Done')
- Just bloody do it at end of each week
Tasks
- Task1 Update READme with installed libraries/dependencies, credits, user stories, features, database diagrams, wireframes
Before changing task status to 'Review' or 'Done' please provide comment (and screenprints if appropriate) as documentary evidence of task completion
Mon 29/01: Done for today, 3 hours. This incremental approach makes sense, while it means that I've had a busy day with very little development done, it does make me feel like I wont be in a mad rush to align the READme with the Agile project issues, and all their detail, at the last point in the project. I left READme towards the end of PP4 and didnt capture everything I'd done in it. So this (incremental, several hours at end of every sprint, is a better approach.