Design Methodologies

A methodology is a system of methods used in a particular area of study. It is important to explore different design methodologies in order to understand how the industry operates and to use the methodologies when producing our group app, in order to achieve a successful design solution.

Waterfall:

waterfall_model

The waterfall methodology was one of the first to be introduced. It is a simple, linear model that is easy to follow and understand. The model is fixed and doesn’t offer much room for constant improvements and refinements to be made. Therefore, it would not be useful for us to follow this method as it is important that we are regularly engaging with the clients to ensure their requirements are being met. As well as constantly thinking about the users of the app and carrying out user testing with the target audience nearer to the end of the process. Following a waterfall methodology could result in the following:

mismatched_expectations

The illustration clearly explains mismatched expectations, hence showing the importance of regularly having team meetings as well as meetings with clients in order to ensure that everyone is working along the same lines. From this, it is very important that we meet the clients requirements in our app and also to sustain users expectations.

Iterative:

iterative-model

This is the methodology that we followed for the previous Design Iterations unit. It allows room for constant refinements and improvements to be made, and the cycle can be repeated various times, to produce a successful well developed end product. The testing stage in particular allows you to gain important user feedback, allowing you to improve on the product to enhance the users experience.

Agile:

agile-methodology

The agile methodology is an iterative model when design solutions are produced in incremental, rapid cycles. It is normally used when there is a short deadline and usually works best with smaller design teams. It involves constant testing and engagement with clients in order to satisfy their needs and requirements, therefore avoiding any mismatched expectations show in the illustration above. This is a diagram to visually show the sprint cycles within agile methodologies:scrum-overview-mark-hoogveld

The scrum methodology is that which we will be following for the production of our Magna Carta app. As it will ensure that each of us team members are on track, continuously working to produce a product that will meet the expectations and requirements of the clients and users. The daily scrum stand ups is something we could incorporate, as it will allow us to share how our individual work progress is going and any problems that we may be encountering. However, as we don’t have a dedicated office/room, the location would have to be organised in advance. We will hold stand up meetings once/twice a week rather than daily as we may not see each other every day at uni.

It is important that we explore different design methodologies, as using methodologies reflects the design industry and helps to make our team more professional, due to this project being a live brief. We will assign job roles to each of our team members (programmer/designer etc) and by following an iterative agile methodology, it will ensure that we are all working along the same lines in order to meet the users requirements and to produce a successful end product that satisfies the users.

Cheng, C, 2015. Why Scrum? Why Agile Development? [online]. Available from: http://calvinx.com/2014/05/22/why-scrum-why-agile-development/ [Accessed 1 March 2015].

ISTQB EXAM CERTIFICATION, 2015. What is Agile Model – Advantages, Disadvantages and When To Use It? [online]. Available from: http://istqbexamcertification.com/what-is-agile-model-advantages-disadvantages-and-when-to-use-it/ [Accessed 1 March 2015].

Advertisements