1. Elena Cuevas­Cobo
Mayur Katariya
Devendra Kumar Lavaniya
Debatri Mitra
Melwin James Poovakottu
Expert Practices
Snippet 1 ­ Experts solve simpler problems first
After a first approach to the problem by brainstorming, the team decides what is part of the
Minimum Valuable Product we want to pursue.
Snippet 2 ­ Experts prefer solutions that they know work
[Out of the picture] one of the team members finds a general representation of the
architecture of a mobile phone application. The team then decides to work on that in order to
draw our architecture diagram.
Snippet 3 ­ Experts use notations as lenses, rather than straightjackets
While drawing Entity/Relation diagram, one of the members of the team wonders why we
don’t use stricter notation for the relations. The team agrees to use a more flexible notation,
since there is a common ground of understanding.
Snippet 4 ­ Experts shift between formal and informal
Firstly, the team started drawing informal sketches of the mobile app, once everybody had the
idea in mind, we started drawing a more formal flow diagram [see in the design file].
Snippet 5 ­ ​Experts keep sketches
During the meetings, team members kept taking pictures of important concepts or sketches.
Snippet 6 ­ ​Experts go as deep as needed
While transitioning into the E/R design, a member of the team starts thinking about how would
we represent a ​path​ in the system. The rest of the team, though, suggests that we shouldn’t
go into that much detail now, since we are on early stages of design.

2. Snippet 7 ­ ​Experts prototype concepts
The different stages of the flow that the team drew on the board are good examples of
mockups for the final application.