Guide for Technical Peer review of a webpage

Peer review (2 person)

    1. Person A:   Describes the overall structure of the page/site (requirements, wireframes, notes, file structure)
      – Question from person B
    2. Person A:   Goes through the code behind the page (Use terms like: elements, tags, attributes, Css rules, js elements)
      -Question from person B
    3. Person A:  Discuss bugs (that have been solved and learned from), possible improvements (code style, comments)
      -Question from person B
    4. Person A: Status on task (requirement, backlog)
      -Question from person B
    5. Change roles an start from 1.

Making Customer Journey maps

Customer Journey maps helps figuring out what it’s like for customers to interact with your brand over time and across different channels. 

In the slide I recommend a Customer Journey map that includes 4 element in the map:

  1. Customers as ref. to Personas
  2. Stages in the journey
  3. Channels on interaction (online , offline)
  4. Touchpoint  Experiences – positive/negative 


UML and System development on MMD

This lecture is about how system development and requirements and modelling/diagramming  can be seen in  connection with a design thinking process and scrum elements like user stories on 2.sem MMD student.  Modelling with UML elements like use case diagrams and use case descriptions will also involved.

Some desk research behind the slide


SCRUM exercise with Lego

Intro to 3 central elements in the Scrum framework for MMD students.

  • Roles (PO: Mr. Ping, SM: Students with support of teachers)
  • Artifacts (Product backlog, Scrum board, Lego )
  • Meetings ( Estimates, Sprint planning, Sprint(10 min), Review an Retrospective)

The session was a 2 hours long and with 6-9 teams of 5 students that did 3 iterations/sprint before making the final pitch of their solution.