Friday, 25 October 2019

Notes 25/10/2019

Notes 25/10/2019

Factory model- the problem is that most people think that we can fit into a factory model, however we can’t sometimes. Although in industry they will often have a team of people that is similar to a factory model. Having one also makes people not creative and reduces their innovation. 

Gantt chart- You divide your project into a small series of tasks, small chunks. Such as research, or presentation work. You also start assigning time to each of the tasks. We also need to have the equipment and software for each task. 

Problems with Gantt charts- The map is not the territory, they are just for guidance they won’t work often, they need to be updated. Very difficult to plan systematically when the process/equipment are not entirely clear.

The waterfall model- “The waterfall model is a breakdown of project activities into linear sequential phases, where each phase depends on the deliverables of the previous one and corresponds to a specialisation of tasks. The approach is typical for certain areas of engineering design.”    

Wicked problems- If you don’t know how to solve a problem, you need to try, prototype, and make and you’ll start to understand the problem. 

Extreme programming- Frequent releases, Pair programming- two brains are better than one, Regular builds and integration tests- what is the simplest version you can build then you add on top of that, Quality and avoiding code breakage.

Rubber duck programming- They get a rubber duck and you need to explain the problem to the duck, this will help you to talk out the problem. 

Scrums- This emphasises the importance of the chunks, the time boxes should show these chunks. A division of sprints, 1-6 weeks for each task. Huan recommends us to have 1-week ones. The goal at the end of the sprint is to do lots of tasks quickly. 

Product backlog- A wish list of what you want the project to do. I.e. we want 3 characters, the uniforms to be perfect, the landscape to look like this, etc. 

Tracking- Have a scrum meeting every session, 15 mins at most, has to be quick. Answer three questions, what have I done yesterday? What am I doing today? Any roadblocks? Any problems encountered; the problem will be fixed after the meeting. After the meeting, everybody knows what everyone’s been doing and what everyone needs to do. 

Using post-it notes- Each post it notes has the priority, the kind of story, task effort how many days it will take, description of task, who is responsible for the tasks. They can be used to backlog, then have it show it’s being worked on, then it’s completed. Can use digital tools too, such as trello. 

Scrum roles

Product owner- the client, the person who has final decisions on what is happening and what will be done. 

Scrum master- group leader, the personal that will lead meetings. 

The team- everyone who is working on the project. 

Tools

Trello- Post-its style app.

Slack- Huan is setting a slack, where we can post any questions and will get answers from Waterloo Uncovered. 

Tumblr- blogs. 

Organisational and schedule methods

In today’s lecture Juan mentioned some ways to be organised within the group. So, I did more research into it:

Gantt charts

A Gantt chart is a horizontal bar chart developed as a production control tool in 1917 by Henry L. Gantt, and American engineer and social scientist. They are frequently used in project management, a Gantt chart provides a graphical illustration of a schedule that helps to plan, coordinate, and track specific tasks in a project.

A Gantt chart is a visual way of seeing exactly what needs to be done for a project from start to finish. It is helpful for organising exactly what needs to be done and showing it in a specific simple way. 

You can make Gantt charts on Excel. 

Waterfall model

The waterfall model is a sequential design process in which progress is seen as flowing steadily downwards through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production/Implementation, and Maintenance. 

I found this list off of this website: https://airbrake.io/blog/sdlc/waterfall-model

The 6 stages are:

-       Requirements: During this initial phase, the potential requirements of the application are methodically analysed and written down in a specification document that serves as the basis for all future development. The result is typically a requirements document that defines what the application should do, but not how it should do it.
-       Analysis: During this second stage, the system is analysed in order to properly generate the models and business logic that will be used in the application.
-       Design: This stage largely covers technical design requirements, such as programming language, data layers, services, etc. A design specification will typically be created that outlines how exactly the business logic covered in analysis will be technically implemented.
-       Coding: The actual source code is finally written in this fourth stage, implementing all models, business logic, and service integrations that were specified in the prior stages.
-       Testing: During this stage, QA, beta testers, and all other testers systematically discover and report issues within the application that need to be resolved. It is not uncommon for this phase to cause a “necessary repeat” of the previous coding phase, in order for revealed bugs to be properly squashed.
-       Operations: Finally, the application is ready for deployment to a live environment. The operations stage entails not just the deployment of the application, but also subsequent support and maintenance that may be required to keep it functional and up to date.
Rubber duck programming
Rubber duck programming is for when you are having an issue with the software or coding. So, you have an inanimate object, or animal (commonly a rubber duck), that you can talk the problem you are having to. This is usually used as when you speak an issue out loud it helps you to think out the problem. 

The steps to do are:
-       Explain your problem and goals with the project. 
-       Explain what is not working and what you have done to try and stop the issue.
-       If you haven’t figured it out yet, explain it in finer details.
-       Find your solution. 

Scrum meetings

Scrum meetings are quick meetings that are held daily, or frequently. They are done so people can quickly say what they are working on and any issues that they are having. Then after the meeting if people need to speak over a topic in more depth, they will have a separate meeting. 

These meetings would be useful to have for our group projects as they make it so everyone knows what each person is doing, as well as meaning that nobody can get away with doing little or no work. 

Post-it notes

Post-it notes can be very effective for organisation. You can use post-it notes to create Gannt charts.

One way to use post-it notes is to create a timeline of the project. To make this you draw a grid to make a calendar, then write in important milestones on particular dates. Then you write down all the tasks needed to achieve each milestone on separate post-its.

Another way is to make a Kanban. Kanban’s are a way to track complex projects, by having multiple stages and splitting tasks into each section, as well as having them in sections for if they need to be done, are being worked on, and finished.

I found this on the post-its website:

1.     To start, you'll need a smooth surface a marker and Post-it Notes, one colour for each member of your team.
2.     Create columns by evenly spacing four notes of the same colour across the top of your poster board. Write “Owner” on the first, “To-Do” on the second, “In-Process” on the third and “Done” on the fourth.
3.     Assign a different coloured note to each member of your team. Place these notes in the “Owner” column to easily denote each team member’s tasks.
4.     Ask everyone to write down the names of their projects and tasks on notes in their assigned colour and place them in the “To-Do” column.

5.     Each team member should select a task to start with and place it in the “In-Process” section. Participants update the status of tasks by moving their notes to the right until they're in the "Done" column.

Sunday, 20 October 2019

Typically British features

As when I am drawing I usually will draw Korean faces I am not very good at coming up with features that are typically British. So decided to do some research into typically British features as to ensure that I draw someone that definitely looks like he is from here.

I found an image that shows the average persons looks from each country, and decided to base my male slightly off of the British one.

I then googled 'British people male' to see what results would come up. From this search I found that almost all the people that came up had brown hair, and many of them had green eyes. They also had double eye lids, and slender looking eyes, which were deepset. They were mainly pale and had pinkish undertones, and their mouths tended to be thinner.

Initial drawings of character


Here are my initial drawings of my soldier character, and the reference images of the characters. I drew the hat and jacket freehand just so that I had a reference of what it looks like straight on. I did these drawings so that I had a gage on what the uniform is going to be like when drawing, as well as the stylings of the soldier, such as facial hair. 

Friday, 18 October 2019

Presentation & notes

Today we presented our ideas for the rest of the class as well as some of the people from Waterloo uncovered.

I think that the presentation went really well, and everyone seemed to like our idea a lot. I also think that the client enjoyed the idea on a whole.

We all spoke about our respective areas of the project, so I spoke about the character and how I am going to be showing his story. I am excited to start this project properly.

Notes from Waterloo meeting

They started the charity on the 200th anniversary of the battle. Since 2015 they’ve helped 150 veterans and serving personnel. 

Waterloo weekend. Reenactors. Don’t have enough time to make it super big. Fundraisers, pop-up museums. 

We need to show what they do, because they don’t have a massive audience. 

360 idea is the one with most legs. 

How to make people care, enough to donate. 

Have the character be voiced and acted by veterans. 

Cold stream guards, red coat, bands, hip, hats. Ask for photos of re-enactments. 

GPR, donation process, data protection. How we are processing that information. Making sure people feel safe to give their data and information. 

Summer events. Sell: tour. The majority of the funding goes towards veterans, £3000 for each one. Nearly £100,000 for the dig, due to the exchange rates. 

Museum tour is for waterloo, memorial 1815. But they don’t have a permanent museum. 

App- Donations, 

Sunday, 6 October 2019

Research on one soliders story

To create my character and story for them, I tried to find some recalls from people that were actually in the battle, here is one article that I found:


Private Matthew Clay was a 19-year-old, who joined the 3rd Foot Guards (Scots Fusiliers) two years earlier than the battle of waterloo. He wrote some memoirs 40 years after the battle, which were later recovered and made into a book. 

Matthew wrote: “On my arriving at the pond, the light of day just enabled me to see that in and around lay the bodies of those who had fallen in combat on the evening previous, and the liquid we had partaken of was dyed with their blood.”

“We passed over numerous bodies of the slain,” he wrote. “I particularly noticed a young officer of the 33rd ­Regiment... his bright scarlet coat and silver lace attracted my attention when marching over his headless body.”

Each man was given a small piece of bread and an officer ordered one soldier to kill a pig. He was given a portion of head “in its rough state” which he tried to cook but found “too raw and unsavoury”.

As the French attacked on June 18, the day of Waterloo, the British took cover in a hedge to return fire, but they were so close “the spreading of their small shots rarely escaped contact with our knapsacks and accoutrements”.

At one point Matthew and another soldier, R Gann, got separated from the company and got back to the courtyard.

“I saw the doors or rather gates were riddled with shot-holes,” he wrote.
“It was also very wet and dirty; in its entrance lay many dead bodies of the enemy; one in particular I noticed which appeared to have been a French officer, but they were scarcely distinguishable, being to all appearance as though they had been very much trodden upon.”
He saw his commander Lieutenant-Colonel James Macdonnell use a large piece of wood to secure the gates, a crucial move in the British victory.
All the French soldiers in the ­courtyard were killed in fierce fighting except one, a drummer boy aged about 13. According to his account, Matthew pushed him into a stable to save his life.
“He was fetching water for people making them comfy and he picked this drummer boy up and put him out of the way so he wouldn’t die.
"Matthew had younger brothers at home, probably the same age as that boy.”
After Waterloo, Matthew was promoted to corporal then the 1st Pay and Drill Sergeant of the Scots Fusilier Guards. In 1823, he married Joanna Cornish.
I also found another recall of the battle: 

Captain J.H. Gronow joined the British Army in 1813 at age 19. He served under the Duke of Wellington in Spain and in Belgium. We join his story on the morning of the battle:
"On the morning of the 18th the sun shone most gloriously, and so clear was the atmosphere that we could see the long, imposing lines of the enemy most distinctly. Immediately in front of the division to which I belonged, and, I should imagine, about half a mile from us, were posted cavalry and artillery; and to the right and left the French had already engaged us, attacking Huguemont and La Haye Sainte. We heard incessantly the measured boom of artillery, accompanied by the incessant rattling echoes of musketry.
As well as a letter written by a soldier that was a part of the battle:


Battle of Waterloo
Letter from a private solider of the 42D regiment to his father in this city.
General Hospital, Antwerp, 24th June 1815. After a long silence, I embrace the opportunity of informing you respecting my present situation. On the 15th, about 12 o’clock at night, we turned out, and at two in the morning marched from the city of Brussels, to meet the enemy, who were advancing in great force on that city. About three o’clock in the afternoon of the 16th, we came up with them. Our whole force did not exceed 12,000 men, who were fatigued with a long march of upwards of 20 miles, encumbered with knapsacks and other language. The day was uncommonly warm, and no water to be had on the road; however, we were brought up, in order of battle The French being strongly posted in a thick wood, to the number of 40,000 men, including cavalry and lancers, gave us very little time to look round us ere the right commenced on both sides, in an awful and destructive manner, they having every advantage of us, both as to position and numbers, particularly in cavalry, as the British dragoons had not yet come up. The French cavalry charged the British line of infantry three different times, and did much execution, until we were obligated to form squares of battalions, in order to turn them, which was executed in a most gallant manner, and many hundreds of them never returned. Still they sent fresh forces, and as often we beat them back. The battle lasted until it was quite dark, when the enemy began to give way, our poor fellows who were left alive following them as long as they could see, when night put an end to the fatigues of a well fought day. Thousands on both sides lay killed and wounded on the field of battle; and as the greater part of the action lay in the corn fields along a vast track of country, many hundreds must have died for want of assistance through the night, who were not able of themselves to crawl away. I was wounded by a musquet ball, which passed through my right arm and breast, and lodged in my back from whence it was extracted by a surgeon in the hospital of this place. Captain M. is most severly wounded, having several shots through his body, and the regiment, in general are mostly cut off. We have heard, since we came here, that our fine brigade, which entered the field on that eventful day, consisting of the 3d batt. Royal Scots, 42d, 44th, and 92d regiments, are now formed into one battalion, not exceeding in whole 400 men. Lord Wellington retired in the night, to wait for reinforcements, and next day our cavalry and the rest of the army arrived. The Prussians came on the other side, and I am happy to understand the enemy ultimately got a most complete dubbing, losing cannon, baggage, and a great number of prisoners. They retreated towards Valenciennes, and other garrisons on their frontiers, the first allied troops pursuing them. 

Thus, I have given you as an account of affairs, principally what I witnessed on the 16th, as I could; that relating to the 18th being from report. Nothing can exceed the kindness and attention of the inhabitants of this city to our wounded men: the hospital is constantly filled with ladies and gentlemen, who, although speaking a different language, personally administer to our wants, with the kindest attention, distributing clean shirts, bread, wine, coffee, tea, milk, and fruit of all sorts, with every requisite, for our comfort and accommodation.

Friday, 4 October 2019

Design thinking


Design thinking- 

We are thought to be the people that make things look good, designers. We actually are experts in humanising technology, usability, humanising, human experience. 

We work differently from everyone else; we do things creatively.

Designers sensibility and methods, human centre approach. 

We start with emphasize, then define it. This is how we understand the context of a project. Ideate, prototype, test, implement. People are missing the empathy when designing, that’s what we are good at. 

Agnes suit, it helps people to empathize with other people, you can’t understand how other people use things, such as people with disabilities, etc.

Define- Analysis and synthesis. We need to write a problem statement, human centred, allow creative freedom, narrow enough to be manageable.

Ideation section- think outside of the box on how to solve the problem.

Prototype- something that we can test and interact with, something that is quick and disposable, wireframes are prototypes, storyboards are prototypes, sketching is a prototype. Prototyping isn’t a finished product, it is to learn about the strengths and weaknesses of the idea, so we can then move to the next section. 

Project spaces- Inspiration, ideation, implementation. 

Design thinking encourages an organisation to focus on the people they are creating for, which leads to better products, services, and internal processes. Your first thought when creating a product is ‘what is the human need behind this?’

Design thinking is important because it can help a business find unmet needs of the people your product is aimed towards, it reduces the risks associated with launching new ideas, it generates solutions that are new and uncharted, and it helps businesses learn faster. 

3 essentials of design thinking are:
Empathy- understanding those who you’re designing for.
Ideation- generating a lot of ideas. Brainstorming is one technique, but there are many others.
Experimentation- Testing those ideas with prototyping. 

When done right design thinking captures the mindsets and ideas of your consumers, paints a picture of the opportunities based on the needs of these people, leads you to innovative new solutions starting with quick, low fidelity experiments that provide learning and gradually increase fidelity. 

Areas that design thinking can be applied:
-       Product design
-       Service and experience design
-       Business design
-       Leadership
-       Organizational change

Design Thinking tackles complex problems by:
1.     Empathising: Understanding the human needs involved.
2.     Defining: Re-framing and defining the problem in human-centric ways.
3.     Ideating: Creating many ideas in ideation sessions.
4.     Prototyping: Adopting a hands-on approach in prototyping. 

5.     Testing: Developing a prototype/solution to the problem.

Notes 04/10/2019

Notes:

Have a real-life item and it connects to the digital, i.e. a musket that ‘shoots’ on screen. 

Video on Blackboard: they have an online data base of the exhibits so that people can go online and see them all, and even order specialised merch from any image that they want from the museum. 

Digital heritage

Use technology for the objects but also a sense of place and environment. 

We have a year so we can be ambitious, we have technology so we can do anything we want. 

Pool is on blackboard. 

PDF- working in groups (no more than 5 pages)
-       Our inspiration, mind-maps, schemes, sketches, annotations, photos, etc. 
-       Problem statement
-       Questions (what we will ask waterloo uncovered, anything we need to know)
-       Explain initial idea through sketches etc. 

My idea initial idea is to focus on one person that was at the battle and show their story, this would be through either VR or a 4D cinema. Having the idea based on just one person would make the whole thing feel more personal, especially if you are 'living' as this person, this would be especially effective as I found that not amen people feel a connection to the battle or the people involved as it happened so long ago and personally I don't know much about it as it was not taught in school.

I chose to be in group with Glen, Emily, Jo and Sophie k. I chose this group because they wanted to do an idea that correlated with my ideas, also I work well with everyone in the group, as well as I think that they our work styles and aesthetics mesh well with each other which is good when creating a group.

our initial idea as a group was to create a VR and AR experience of the environment. So we would have a experience where you could find pieces of items from the original area pre-battle and it will piece together so you can see what it would've been like at the time.

We all chose what roles we would be doing, so Sophie K will be making the app that will have the AR experience version of the VR one, so that lots of people can experience it without having lots of vr.

I am going to be designing the graphics as well as drawing all of the characters and objects if we can't find real images of them.

Glen and Jo are going to be designing the environment as well as the game, VR and AR aspects as they both enjoy doing that type of work and are good at it.

Emily is going to be creating the videos that go alongside the VR and AR, these are going to be shown to enhance the overall experience. 


Final reflection

I think that in the first semester I really enjoyed this brief and was very excited to do work for it. However, because I was excited to do...