Class Learnings Flashcards

1
Q

Cognitive load

A

All communications put cognitive load on the audience. We are trying to decrease that load in order to persuade through clarity.

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

Encoding + decoding

A

Many factors influence decoding. We will focus on encoding data for people with different contexts so that they decode it reliably

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

Curse of Knowledge

A

When we explain our data we need to rewind to what it was like before we saw the data to ensure we see things from our audience’s point of view

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

Explanatory vs. exploratory visualizations

A

Each has a different audience, purpose and set of requirements. Visuals designed to explain data require an entirely different mindset.

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

Agile

A

Agile is when a group of people building a product trying to iterate on new features quickly so they can estimate scope and define what we’re building next. Rather than working on a huge deadline and overcomplicating what you’re building by. Go live as you go with feedback so you get feedback on what needs to change in real time.

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

Difference between agile and waterfall

A

Agile chunks the work up into much smaller pieces where waterfall many features are being built at once

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

Difference between Scrum and Agile??

A
  • Scrum is a subcategory of agile that is a framework for agile development
  • Scrum is an agile framework. Agile is a way of thinking with small chunks or sprints of work and time to pivot accurately
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Agile Team Make Up

A
  • Product owner/manager: consumer-facing; provide a vision for the team. Prioritizes the stories and features to max customer value with minimal effort. Makes sure the team is working on the right things and that things are of high enough quality to be released.
  • Scrum master: Expert > making the sure team is working super effectively, clearing impediments, managing team dynamics, nurturing relationship between team, product owner and others, protecting the time of the team
  • The development team: 3 to 10 people. Ideal if these people are T shaped people (person perfect for scrum teams) because they can pick up any piece of work on the team and get started (breadth of knowledge but also depth of experience)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is Agile development?

A

Agile software development is an umbrella term for a set of frameworks and practices based on the values and principles expressed in the Manifesto for Agile Software Development and the 12 Principles behind it.

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

Agile Manifesto

A
  1. Individuals and interactions over processes and tools.
  2. Working software over comprehensive documentation.
  3. Customer collaboration over contract negotiation.
  4. Responding to change over following a plan.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Benefits of using agile

A
Self-organizing teams
Stability
Concurrent development
Multilearning
Organizational Knowledge
Transparency/Communication
Continual improvement
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is a sprint?

A

A short (1 to 4 week) time period that results in some kind of incremental output (draft, prototype, new/updated feature, etc). These could focus on exploration, problem definition, building, testing, or validation

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

Different agile frameworks

A
Scrum
eXtreme Programming (XP)
Dynamic Systems Development Method (DDSM)
Feature Driven Development (FDD)
Adaptive Software Development (ASD)
The Crystal Method
Lean Software Development (LSD)
Disciplined Agile (DA)
Scaled Agile Framework (SAFe)
Rapid Application Development (RAD)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What is the primary role of the product owner on a Scrum team?

A

The primary goal of the product owner is to provide vision for the team. They do this by:

  • Prioritize the stories and features to achieve maximum customer value with minimum effort
  • Providing clear descriptions and information to create a shared understanding of the problem and users
  • Be the final check on whether an increment is ready
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Role of the Scrum Master on a Scrum team?

A

The primary goal of the scrum master is to make sure team is working as effective as possible. They do this by:

  • Being a Scrum expert
  • Clearing impediments
  • Developing a productive environment
  • Managing team dynamics
  • Nurturing the relationship between the team, product owner, and others
  • Protecting the time of the team
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

The development team on a scrum team

A
The team (3 to 10 people) is responsible for the work that gets done to develop a product and is responsible for determining the solution and how it works. Good or bad, the outcomes belong to the whole team and roles are fluid.*Research shows 5 is an ideal team size
- T shaped people (breadth of skills and knowledge, depth of expertise)
17
Q

What is the product backlog in a sprint/agile methodology?

A

A single prioritized list of items for the team to work on (new features, fixes to features, bugs, etc)
- Items are most commonly represented as user stories
- It should be easy to add and remove items
- Items are different sizes, but need to meet the team’s definition ofready
**Definition of Ready: An agreement on the amount of information, size, and estimates
Some items are left as larger and more ambiguous when they aren’t intended to be work on soon…why?Artifact

18
Q

What is sprint planning?

A

It’s when you determine the items from the product backlog that will move to the sprint backlog to be worked on during that sprint

  • Product Owner: Ensures that all decisions are made based on user needs and product vision. Additionally provides clarification of backlog items
  • Scrum Master: Facilitates the meeting to have productive discussions that lead to agreement on the sprint goal and items
  • Team: Determines how many items they will be able to complete and how they will achieve the goal.Event
19
Q

How do you execute sprint planning?

A
Step 1: Scope
- What is the goal? (used as a filter)
- Which items are ready and contribute to goal?○What is our work capacity? (past trends, holidays, vacations, etc)
- Which items fit goal and capacity?
- Reflect
Step 2: Plan & Strategize○What are the tasks?
-Are there dependencies?
- Who is working on what?
20
Q

Format/purpose of daily scrum meeting?

A

A daily meeting at the same time where the team brings everyone up to date on progress towards the sprint goal

Each person answers the 3 Scrum questions:
○What have you completed since the last meeting?○What do you plan to complete by the next meeting?○What is getting in your way?

Keep this time boxed (15 min max)

This is a peer-to-peer meeting, not directed at individual. If something starts a discussion, put it in the “parking lot” for after

21
Q

Three questions asked at every scrum meeting

A

○What have you completed since the last meeting?○What do you plan to complete by the next meeting?○What is getting in your way?

22
Q

Sprint Review

A

Sprint reviews happen at the end of a sprint to demonstrate the product increment(s) in front of stakeholders and collect feedback.
- Priority: Collecting feedback from customers and users
- Secondary: Collaborative discussion around priorities
- Product Owner traditionally facilitates and the team contributes when necessary
○Letting someone show off their work can be empowering
- Presentation should be well prepared and engaging, but you don’t want to eat up this time

23
Q

Sprint Retrospective

A

Retrospectives happen after the sprint review to highlight lessons learned and collectively agree on changes to improve the team.
Step 1: What happened?
Step 2: What should we do differently next sprint? The goal is to come up with one “experiment” to improve teamwork that will be tested in the next sprint.

24
Q

Kaizen

A

Japanese term for change for the better or continuous improvement

25
Q

Backlog Refinement

A

Ideally, you want 2-3 sprints worth of backlog items always ready
- Product Owner
○Remove user stories that are no longer relevant
○Create new user stories based on the discovery
○Re-assess story priority
○Splitting stories that are of high priority but too large for the sprint
- Team
○Assign estimates or create new ones based on new information
- Point Estimates/Planning PokerOrganizations will do this differently, but team involvement is always critical