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.