Embedded Files
Minimum Viable Product (MVP)
Minimum Viable Product (MVP)
Basic Framework / Functionality
Basic Framework / Functionality
During the first sprint you should finish the basic requirements of your project. The users should be able to give you feedback on how your project works and looks even if everything is not working 100%
Evidence
Evidence
You will need to show evidence of your process. You can do this a variety of ways:
A overview each week
After completing a task in your project management
Key moments
Use bullet points, screen captures, gifs, images, written info to show this evidence.
*** We do not need every single detail - just key points and a quick summary. ***
Task 1 - Sprint 1 Planning
Task 1 - Sprint 1 Planning
Get into Trello (or whatever planning tool you are using) and break this sprint down to easy manageable tasks. You have created a final design so think about what you now need to make on the software so that your outcome can become functional.
At the end of 4 weeks you should have something that can be trialled with end users and gives the basic idea of what your outcome is. Think about what the minimum features are and prioritise based on their importance and impact.
Below are some examples to help you get started.
Task 2 - Sprint 1 Develop & Test
Task 2 - Sprint 1 Develop & Test
Focus on creating all the elements / parts / components that will get your outcome up and functioning. You might have placeholder graphics at this point.
During development you need to also test:
Perform testing to ensure individual components work as expected.
Conduct integration testing to check how different components work together.
While you are developing think about:
People – the end users and also who you will use to trial and the end of this sprint
Objects – static and interactive, including other objects the people and/or prototype interact/s with
Location – where this will be used, the places and environments
Interactions – are these digital or physical, between people, objects and the location
Task 3 - Sprint 1 Trial & Feedback
Task 3 - Sprint 1 Trial & Feedback
This is very important. It allows you to see whether your idea is meeting its purpose and end user requirements.
Examples of Trialling Questions
(in a website development context), linked to relevant implications
Does this site adhere to legal requirements? (content and images meet copyright requirements)
Is the site accessible? (via multiple devices, alt tags)
Does the site function properly? (images display, image quality and resolution correct, all navigation links work)
Is the site readable (usability)? (proofing of spelling, grammar, appropriate font sizes and colour contrast)
Is the site aesthetically pleasing? (have design principles such as repetition, alignment, proximity, white space and typographical conventions been followed)
Does the site meet end user requirements? (what were they? have they been addressed?)
From the feedback I have received I will develop...
Page updated
Report abuse