The aim of this sprint is to have your functional outcome presentable to an end user or stakeholder — it should be working, understandable, and beginning to look good. The core parts should be finished so that all the parts work well together.
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. ***
Get into Trello (or whatever planning tool you are using) and break this sprint down to easy manageable tasks. You should have some sort of functional outcome so this focus is on making it presentable.
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.
What S2 focuses on:
Finalised shape/design for production
Assembly tested digitally or physically
Visual presentation (exploded view, render, or label)
Achievable steps:
Refine curves, connections, and tolerances
Test in simulation or rough prototype
Add dimensions and exploded view in CAD
Render with materials applied
Finalise materials and tools list
Prioritised features:
Design is manufacturable
Joinery and fit tested
Looks clean and realistic
Testing checklist:
Model can be assembled and printed/cut
No interference or weak points
Materials are appropriate for outcome
Final product is to scale
Instructions or documentation are clear
Refine and Enhance Features:
Improve and expand on the core features based on feedback from the MVP.
Add additional functionalities that provide value to users.
User Experience and Interface Improvements:
Enhance the UI/UX design to make the product more attractive and user-friendly. (Housing specific)
Implement more detailed and polished design elements.
Performance Optimisation:
Optimise the code to improve the product’s performance and responsiveness.
Ensure the product works smoothly across different devices and platforms.
Advanced Testing:
Conduct more thorough testing, including usability testing, performance testing, and compatibility testing.
Fix bugs and improve overall product stability.
Examples of Trialling Questions
(in a Electronics/Mechatronics context), linked to relevant implications
Does the system adhere to required safety and industry standards (e.g., CE, IPC, ISO), and have intellectual property rights or open-source hardware licenses been respected?
Is the system accessible via standard communication protocols (e.g., UART, I2C, USB), and are Human-Machine Interfaces (HMI) designed for ergonomic use and clear feedback?
Does the hardware perform reliably under load? (Verifying signal integrity, actuator response, correct power distribution, and stable firmware execution).
Is the system easy to interpret and maintain? (Clear PCB silkscreening, distinct LED status indicators, logical button layouts, and readable display data).
Is the physical build quality professional? (Adherence to design rules, clean cable management, precise component alignment, soldering quality, and proper enclosure fitting).
Does the final prototype meet the defined Technical Specifications and functional requirements? (Have all critical tolerances and input/output criteria been satisfied?)
From the feedback I have received I will develop...
Now moving onto the next sprint