From: https://www.csfieldguide.org.nz/en/chapters/software-engineering/software-processes/
Communicating clearly with other software engineers and customers is essential for software engineers. In this activity, you get to practice communicating as precisely as possible!
SPRINT A
Divide up into pairs, with one creator and one builder in each pair. Each person needs a set of at least 10 coloured building blocks (e.g. Lego blocks). Make sure that each pair has a matching set of blocks or this activity won’t work! Take one of a pair of matching AGILE LEGO bags, e.g. a 1A / 1B.
The two people in each pair should not be able to see each other but need to be able to hear each other to communicate. Put up a screen between the people in each pair or make them face in opposite directions. Now, the creator builds something with their blocks. The more creative you are the more interesting this activity will be!
When the creator has finished building, it’s the builder's turn. His or her aim is to build an exact replica of the creator's structure (but obviously without knowing what it looks like). The creator should describe exactly what they need to do with the blocks. For example, the creator could say "Put the small red block on the big blue block" or "Stand two long blue blocks up vertically with a one block spacing between them, and then balance a red block on top of them". But the creator should not describe the building as a whole (i.e. don't say "make a doorframe.").
When the builder thinks they are done, compare what you built! How precise was your communication? Which parts were difficult to describe for the creator / unclear for the builder? Switch roles so that you get to experience both sides!
SPRINT B
Try the activity again (swap bags with another team, e.g. AGILE LEGO 2A / 2B), but with this time only communicate with written instructions, you can use text and/or images. Compare what was made. Which modes of communication helped most?
List all of the activities you do & Sort them into an Eisenhower Matrix to group them into 4 quadrants: High / Low Urgent vs Important.
Merit / Excellence. Q) How did this help you to realise which are activities that should be cut-out because they are Not Important / Not Urgent?
Keep a diary of how you spend your time.
Merit / Excellence
Q) What are your Top Priorities and When can you Make time to focus on them? What's next? What needs doing next? How will it be tested?
Create a tick list of jobs and track them. Add reminders & link to Google Calendar.
Q) What are the pros/cons of using Google Keep tick list versus an agile Kanban using Trello.com?
Manual Version Control
If you are using CoSpaces.io/edu rather than Aframe.io on Glitch.com, then you can manually make and share Google Drive folders for saved versions of your project's assets.
Use version control to name the copies / versions of your CoSpaces projects, e.g. "WHS VR Tour - version 2c".
Version Control Software - Glitch.com can automatically link your Aframe code to Github.
- Use advanced processes to develop a digital technologies outcome involves:
● using appropriate project management tools and techniques to plan the development of a digital technologies outcome
● decomposing the outcome into smaller components
● trialling the components of the digital technologies outcome
● testing that the digital technologies outcome functions as intended
● explaining relevant implications.
###################################
Examples of Project Management and Version Control tools and techniques include:
● saving backup copies with a logical file naming system
● using collaboration tools
● using simple version control software applications
● using tools or systems to plan tasks and milestones
● adjusting key actions and tasks where appropriate
● trialling multiple components and/or techniques and selecting those which are most suitable
● using information appropriately from testing and trialling to improve the functionality of the digital technologies outcome
● addressing relevant implications.
● discussing how the information from planning, testing and trialling of components assisted in the development of a high-quality outcome.