3. Individuals and Interactions Flashcards

1
Q

What is context switching?

A

The transition period for your brain to go from one task to the next.

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

Is multitasking a good idea?

A

No. Each time you switch between tasks, you have to do a little bit of thinking to get back on track. Humans have a difficult time switching between work items.

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

What should be the attitude towards multitasking in an Agile environment?

A

Try to limit the team’s multitasking. Instead of working on several different things at once, the entire team will focus on a limited set of high-value tasks.

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

What do the statistics show in regards to the time spent context switching while multitasking?

A

That if you multitask on three items or more, you’re spending more time adjusting from one item to another than you’re spending solving the problem.

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

What are the short iterations of work called in an Agile context?

A

Sprints.

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

What is one of the very first things you should think about related to dealing with multiple tasks when embracing an agile mindset?

A

Trying to limit your team’s multitasking. Instead of working on several things at once, the entire team must focus on a limited set of high-value tasks.

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

What does focusing on a limited set of high-value tasks accomplish for Agile?

A

It helps with one of Agile’s guiding principles: continuous delivery in short iterations.

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

What is can be said about multitasking in the context of “scrum”?

A

That reducing multitasking is one of the original ideas behind the scrum framework.

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

What are handoffs?

A

Finishing work on a task and then giving it to another person or department for processing.

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

Are handoffs an efficient way to work and why?

A

No. Much like multitasking, there’s a lot of overhead. A lot of time gets wasted waiting for someone else to finish their work.

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

What is the challenge of handoffs in regards to the size of the workload and why is it a challenge?

A

It encourages large batches of work (queue size) to go through the system. If you have large batches of work going through the system, then people are going to process these batches at different speeds. This means that at some point, everyone is either speeding or crawling.

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

What’s a way to make it easier to limit your handoffs.

A

Keeping the batch sizes smaller.

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

Is the belief that you might be more productive alone in a quiet office true?

A

Yes. However, an organisation is not just one individual. Even though you as an individual might be much more productive working on your task, as a team overall, you’d actually be less productive.

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

What is the most productive way to work as an agile team in regards to the batch size of tasks?

A

By moving around small batches of work and eliminating handoffs. Even if the individual productivity decreases, the team’s overall productivity increases.

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

What is a sprint?

A

A timeboxed iteration of work intended to deliver a shippable portion of a product in a shorter time scale.

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

Why does most agile teams deliver software in sprints?

A

Because it’s a very well-structured way to deliver products quickly.

17
Q

Should Agile teams be cross-functional and why?

A

Yes. It’s nearly impossible to have everyone on the team equally skilled in all of the functional areas, but Agile teams should strive to have everyone good enough to be able to contribute something to every bit of work on the team.

If you have work that only one person can complete, then you’ll create handoffs and backups. This expert needs to train the other people on the team so you can be sure to continuously deliver at a predictable pace.

18
Q

What is a cross-functional team?

A

A cross-functional team has each member working horizontally through the different functional areas. This means that there might be software engineers that help you write requirements. You might have quality assurance people who are also developing software. Each person focuses on the work and not on their own functional role.

19
Q

How do user stories relate to project requirements in formality?

A

There’s a form and format to the user stories, but they are not nearly as formal as project requirements.

20
Q

How are user stories used in terms of defining the requirements and why?

A

As a placeholder for future conversations, because Agile promotes face-to-face communication independent from the documentation. So, user stories aren’t about getting the right format, they’re much more about having the right conversation.

21
Q

What is the common format for user stories?

A

As a [USER], I want to [SOME FEATURE] so that I can [GET SOME VALUE].