Unit 2 Qestion

 

Using a Visualisation diagram as part of the planning process can be very effective for the team, as it offers specific advantages over other project management tools.

For example, to create a visualisation it requires less time to read and also offers a better understanding when being being shown to clients. This means there will be better communication with the client and the team as it offers a quicker, high lever representation of the contained data. Reducing time spent on planning and helping both sides come to a quicker understanding off the profit.

Furthering this point, Due to how simply and quick it is to make a visualisation diagram. The time spent on planning can be greatly reduced while the efficiency of the team would be greatly increased. This means that more time can be spent on the more important tasks at hand like the production and post production of the final product. Proving how a visualisation diagram is very effective when planning a product. 

A Visualisation diagram allows the encouragement of creativity and self-expression for a product. This would be useful for a product that needs to be interactive and have many features as a visualisation diagram would allow the team to introduce their own ideas and plus improve on the client requirements. Improving the website and proving that a visualisation diagram can be useful for planning a website.

However, while a Visualisation diagram has its advantages proving its effectiveness when planning a website. It does also have some disadvantages; Such as:

while the use of a visualisation diagram does offer effective communication between the team and client, if this isn't kept up throughout the whole creation of the visualisation diagram, then you could have a complete detailed design that the client may not like. As it can be very one-sided and bias can take effect when the team is designing it. This mean that they would have to spend more time focussed on a new diagram that wont offend the client. This would waste a lot of time and shorten the already short deadline. 

Unfortunately the use of a visualisation diagram doesn't allow a lot of improvement for the final product. Some changes may offend the client and may not keep to their requirements, also, it doesn't offer the amount of help when making a product unlike a SWOT analysis would. Which shows the strength and weakness' of the product. This means the team wont get the full potential from their design and it could effect the product as a whole. Proving that a design doesn't allow growth of the product when in the planning stage and isn't as effective as other documents.

when creating the diagram, wrong focussed people can skip core parts of the website. This could lead to disagreements with the team and the client as it may not have the requirement's that they asked for. Even worse is that it can effect production and post production making some core elements of the website being untreated with which will leave them unfinished in the final product. Finally proving that while a diagram has many pros it also has quite a few cons that effect production as a whole