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.

Example for DFM Product

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

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 Electronics/Mechatronics context), linked to relevant implications

• Does the project follow basic safety rules and respect design ownership?

• Is the device physically easy to handle, plug in, and turn on?

• Does the circuit or mechanism actually work without crashing or overheating?

• Is it clear how to use it? (Are the buttons, ports, and lights easy to understand?)

• Is the construction tidy? (Are wires organized, connections tight, and components secure?)

• Does the device actually solve the problem it was built to solve?

From the feedback I have received I will develop...