L1 3D Modelling
~+~ Development Sprint 2 ~+~

Before you continue developing, plan what you will work on during Sprint 2.

Use your project management board to:

• move your Sprint 2 tasks into Ready / Next Up

• choose the first tasks you will begin developing

• check that your tasks are in a sensible order

• make sure testing and feedback tasks are included

• take a screenshot of your board as evidence

In your document, add a screenshot of your Sprint 2 planning

Development evidence shows your progress, testing, and improvements.

You need to collect at least one clear piece of development evidence each week. This evidence should show what you developed, what you tested, what changed, and what still needs to be improved.

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.

• 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.

At the end of Sprint 2, you need to test this working version of your outcome.

Testing checks whether your outcome, or part of your outcome, works as intended. In Sprint 1, you are mainly testing the core structure and basic functionality.

This is not about proving that your outcome is finished. It is about finding out what is working, what is not working yet, and what needs to be fixed or improved before Sprint 3.

Export, preview, render, build, present, or share your current Sprint 2 version so it can be tested.

Create a short testing checklist that focuses on your core structure and basic functionality.

Testing checks whether your outcome works. Trialling checks whether your outcome makes sense for people.

At the end of Sprint 2, share your first working version with at least one suitable person. This could be an end user, client, stakeholder, teacher, or technical expert.

Share your Sprint 2 version with at least one suitable person.

This could be:

• an end user

• a client or stakeholder

• a teacher

• a technical expert

• a peer who matches your intended audience

Ask them to trial your outcome and give feedback on.....

In your document, include:

• who gave feedback and their role

• what version or component they trialled

• the questions you asked

• what feedback they gave

• what you will change because of the feedback

• what feedback you will not use, if relevant, and why

Finish this section with:

• • From the feedback I have received, I will develop…

  • Then explain the changes, fixes, or improvements you will take into Sprint 3.

At the end of Sprint 2, review your evidence and update your project management board.

This review should show where your project is up to and what needs to happen before you begin Sprint 3.

Your project board should now show:

• tasks that were completed

• tasks that are still in progress

• tasks that were tested or reviewed

• tasks that need fixing or improving

• any new tasks added because of testing or feedback

• any Sprint 2 tasks that need to move into Sprint 3

This does not need to be long. The goal is to show how Sprint 2 has affected your plan for Sprint 3.

Update your project management board at the end of Sprint 2.

Move your cards into the correct columns, such as:

• Done - tasks completed during Sprint 2

• Testing / Review - tasks or components that still need checking

• Fix / Improve - tasks that need changes after testing or feedback

Take a screenshot of your updated board and add it to your document.

Under the screenshot, write a short review using the prompts below.

Sprint 2 review prompts

• What Sprint 2 tasks did I complete?

• What did I not complete, and why?

• What testing or feedback affected my next steps?

• What parts need to be fixed, improved, or continued in Sprint 3?

• Have any tasks changed priority?

• Are there any tasks I am moving to later, removing, or adding? Why?

Keep it brief

You only need a short paragraph or a few bullet points.

Before moving into Sprint 3, save a clear backup of your Sprint 2 work.

This helps protect your progress and gives you a version you can return to if something breaks later.

What to do

• Save or export the current Sprint 1 version of your outcome.

• Create a backup copy of your project folder.

• Rename the backup clearly, for example:
  ProjectName_EndOfSprint2

StudentName_Project_S2Backup

Game_EndOfS2_WorkingVersion 

• Store the backup in the correct folder or backup location.

• Check that important files, assets, links, media, database files, exports, or working files are included.

• Make sure your evidence screenshots/videos are also saved in the right place.

Before you move on

Back up your Sprint 2 version and file it clearly as End of S2. This creates a safe checkpoint before you begin making Sprint 3 changes.