Week 5 Flashcards

1
Q

What skills does working in a team require?

A

Collaboration
Problem Solving
Agile Adaptability
Building Trust
Amplified Creativity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Describe the ideal team member. The ideal team member..

A

..is reliable
..communicates effectively
..embraces collaboration
..displays respect
..sets personal principles
..stretches themself

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the five stages of team development?

A

Forming
Norming
Storming
Performing
Adjourning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are the things that a team should definitely do?

A

Communicate and communicate
Fairly contribute and divide the workload
Respect and value differences
Foster trust and build relationships
Set clear goals and expectations

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the things that a team should definitely NOT do?

A

Micromanaging
Being afraid to ask for help
Negativity and blame game
Ignoring conflict
Procrastination

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is ‘Agile’?

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Why does ‘Agile’ matter?

A

software is developed in short iterations (sprints)
the development team is cross-functional
the team is self-organising and manages its own work

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What are the common ‘Agile’ frameworks?

A

SCRUM
Kanban
Lean

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are the benefits of ‘Agile’ teams?

A

Faster time-to-market
Increased collaboration
Higher quality
Flexibility

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Compare the two types of teams that exist.

A

Agile Team
work in short, time-boxed iterations called sprints
focuses on delivering a set of features during each sprint
holds sprint-planning meeting to define work to be done, effort and duration required
team works collaboratively
restrospective/sprint review held at end of sprint
team is self-organising

Traditional Team
follows sequential approach to development
members work separately, with clear division of labour
project manager monitors the progress of the project
members receive direction and oversight from project manager

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is the ‘Sprint Planning Meeting’?

A

meeting occurs at beginning of each sprint
team decides which tasks to work on in the sprint and who will handle them
project manager leads the sprint planning meeting
project manager ensures project is done within planned scope, budget and time
teams works together to set clear goal for the sprint

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is the ‘Sprint Retrospective’?

A

the goal is to reflect on the completed sprint
- identify what went well, what didn’t go well, and generate actionable improvements for next sprint
provides an opportunity to continuously improve processes, communication and collaboration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are some pointers for ‘Sprint Retrospectives’?

A

create safe and inclusive space
be honest and open
focus on observation and facts
use a collaborative approach
identify both success and areas of improvement
set SMART goals
follow up on action items

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Define a UX Researcher.

A

UX Researcher works closely with the product owner/project manager to identify user needs + expectations
they analyse data gathered from their research to help guide product development
UX research is an iterative process through the project lifecycle

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Define Product Manager.

A

responsible for driving the vision, strategy, design, and execution of product
ensuring team’s day-to-day is aligned with the business objectives
at intersection of UX, tech, and business

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Define Product or UX/UI Designer.

A

work hand in hand with UX Researchers and PMs
responsible to turn insights from UX research into wireframes/prototypes
they consider holistic product metrics

17
Q

Define Backend Software Engineer.

A

primarily responsible for designing, developing, and maintaining the server-side logic and databases of an app
they closely with PM and dev team to ensure architecture of app meets requirements
responsible for maintaining the logic that’s responsible for processing and storage of data on the server
responsible for designing database architecture
they write and maintain APIs (middleman of app’s front-end and back-end) > also likened to a waiter

18
Q

Define Frontend Software Engineer.

A

responsible for developing user interfaces for apps
collaborate w/ Product or UX/UI Designers to ensure interfaces meet design requirements
also work w/ BE to ensure needed API endpoints are provided

19
Q

Define Fullstack Software Engineer.

A

can do a bit of everything to ensure that website is complete and functional
develop both FE + BE components of software product

20
Q

Define Mobile Software Engineer.

A

they design, develop, and maintain mobile apps

21
Q

Define Cloud DevOps Engineer.

A

ensure that software development and delivery processes are streamlined, efficient, and of high quality
help the team by setting up systems and tools to make the building process easier
they create a plan for how all the different pieces will fit together and work as a unit
they find ways to make repetitive tasks automated

22
Q

Define Data Analyst.

A

their primary job is to collect the right information
collect data > organise data > analyse data > interpret data
to help make informed decisions and solve problems

23
Q

What is ‘Guestimation’?

A

estimation based on guesswork, logic, experience, and calculation
done when time, resources or data are too limited to conduct thorough research
good for low-impact decisions

24
Q

Describe steps taken for ‘Guestimation’.

A

Clarify the question
Break down the problem
Solve each piece
Consolidate
[Answer]

25
Q

Describe the approaches to ‘Guestimation’.

A

top-down
identify the big picture and all of its components
the components are the driving force for the end goal
uses previous experiences and expectations
using contextual or general knowledge

bottom-up
focuses on specific characteristics and micro attributes
explanation of the perception that involves starting with an incoming stimulus
purely data-driven, processing in real-time

26
Q

What is the Data Analysis Framework?

A

a structured approach used to examine and understand data
involves asking key questions to gain insights into the problem or situation

27
Q

Describe the steps in the Data Analysis Framework.

A
  1. Understand the Problem
    before solving, you must understand what the problem is about
  2. Identifying Relevant Data
    identifying the specific information or data points that will contribute to a viable solution
    requires thoughtful consideration of the problem’s context, scope and objectives
  3. Obtain the Data
    active process of collecting the required data from various sources
    data can be manipulated, must ensure source is reliable
  4. Clean the Data
    clean data is:
    - accurate > free of errors, inaccuracies or inconsistencies
    - complete > contains all necessary information without missing values
    - consistent > follows a uniform format + standard conventions
    - relevant > excluding unnecessary or redundant information
28
Q

Define ‘Data Tracking’.

A

the process of collecting, monitoring, and recording data over time

steps
Set clear goals
Choose what to track
Pick tools or systems
Collect data
Organise and store
Check for accuracy
Analyse and interpret
Share indights
Monitor and adjust

29
Q

Define data visualisations.

A

visuals that help your audience understand the data and the story you’re trying to tell with it

30
Q

What the five core elements of a chart?

A

Chart title
Vertical a is title
Horizontal axis title
Axes labels
Data labels