Oticon Remote

This page supports remote sessions for Oticon.

What have we done? Is it enough?

Remote session with sites in

• Warsaw (23/04 15:00)
• Szczecin (13/05 14:00)
• Copenhagen (28/05 14:00)

Subject

Converter v2

Groupwork

1. Analyse testing done before your work.
   On arrival,
   • the code had tests as listed
   • the data had been exercised with the “pre-filled list”, and the results approved by the coders.
   In groups of 2-3 people, analyse those tests and the data, looking for what you might trust, what you might doubt, and what is missing.
   5 minutes in groups followed by 5 minutes debrief.
2. Consider the testing you did
   Summarise the testing you personally did with a list or picture.
   5 minutes individually, followed by 5 minutes debrief.
3. Are you finished?
   Is the module good enough to stop work on – and if not, what do you need?
   Draw a graph / picture to communicate your answer. If you feel that context is important, pick one from the three below. Be prepared to show at least one picture and answer.
   5 minutes in groups, followed by 10 minutes debrief.

---

Context

When you need context, pick (and stick with) one of

• The conversion module wil be immediately integrated into an educational website for children aged 7-13.
• The conversion module will be passed to specialists in security and performance, and then will be used in a game with money prizes
• The tests for the conversion module will be double-checked against JavaScript compilers in various browsers, before being deployed in a tool suite to assist engineers modelling anything from cellular dyamics to satelite re-entry.

Making Notes

Remote session with sites in

• Szczecin (20/02 14:00)
• Warsaw (05/03 15:00)
• Copenhagen (19/03 14:00)

Subject

Converter v2

Groupwork

1. 3 minutes group chat. In groups of 2-4: How do you go back to something you’ve tested before. How will you go back to this system? Share your notes, memories, ideas.
   2 minute summary – We'll summarise by hearing three ideas.
2. 5 minutes exploration In pairs or solo: Explore version 2 of the converter, guided by notes and memory.
   3 minute summary – Did you use your notes? If yes, did they help? If no, can you describe why not?
3. 10 minutes analysis, planning, exploration In groups of 2-4: Look at (one or two of) tests, release notes, configured unit boundaries, other options in config, pre-filled bulk data, console.log(workroomprds.converter.NewConverter(workroomprds.converter.metricUnits)). Explore converter v2, making great notes.
   5 minute summary tell us about your notes.

Techniques for Exploring

Remote session with sites in

• Szczecin (28/11 15:00)
• Copenhagen (5/12, 14:30)
• Warsaw (12/12, 15:00)

Subject: converter v1

Big list of naughty strings

Shared spreadsheet: record of aim and time (for Szczecin, for Copenhagen)

Value of Testing

Remote session with Szczecin site

Shared: text workspace

Contact

James Lyndsay, Workroom Productions

@workroomprds, +447904158752, LinkedIn