7. Improve Customer Collaboration Flashcards

1
Q

What are the dangers of equating Agile and traditional roles?

A
  1. Place people in poorly fitting roles

2. Perpetuate stereotype of slow organisational change

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

What can be said about Agile roles in regards to traditional roles?

A

That they are usually radically different in nature. The traditional roles should not be used as a way to understand Agile roles. Instead, we must do away with the traditional roles and look at Agile roles with a fresh pair of eyes.

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

How is the traditional Project Manager different from the agile Scrum Master?

A

A project manager is used to being the point person for the project. People in the organisation will come to them for status updates, and they’re responsible for hiring and firing people on their team.

A scrum master is a COMPLETELY different role. A scrum master acts as a coach — instead of having authority over the team, you’ll be encouraging them to take on greater responsibilities.

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

What are the top three characteristics of a Scrum Master?

A
  1. Coaches
  2. Encourages
  3. Facilitates self-management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

How is the traditional Business Analyst different from the agile Product Owner?

A

They are entirely different.

A business analyst will typically create project requirements for the team. Then, it’s up to the team to deliver those requirements. There is a handoff here.

On the other hand, a product owner works with the team to deliver the product — there is a shared responsibility between the product owner and the development team.

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

What are the top two characteristics of a Product Owner?

A
  1. Works with the team

2. Has shared responsibility

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

What do most Agile coaches believe about the importance of the Product Owner and what’s the reason behind that?

A

That it’s the most important role on the team. This makes a lot of sense because the Product Owner owns the product — they are responsible for setting the direction and prioritising the work.

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

What can be said about the authority of the Product Owner in an Agile team and what can be said about their being knowledgeable?

A

That they should have authority to make real-time decisions. They should have most of the answers. If the developers have a question, they shouldn’t have to email someone for an answer.

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

How is a Product Manager different than a Product Owner?

A

A Product Manager works on the long-time strategy for a product — they create the budget and look at competing products. Once they have a vision, then they’ll bring in a Product Owner to actually own the product.

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

What does a Product Owner work off of in a typical Agile team?

A

A product backlog, which is a ranked list of different features that the Product Owner would like included in the product.

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

What did the course say was the key thing to remember about the Product Owner?

A

That they’re fully integrated into the team. They should sit with the team and be able to answer questions.

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

What is the primary disadvantage of not having a Product Owner in the team or having one that is not committed to the team?

A

The team may lose a sense of direction. The developers will just deliver the parts of the product that they can finish first, which may or may not have the highest customer value.

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

What is the “master” in Scrum Master about and what is it not?

A

It’s about mastering the Scrum, not about mastering the team.

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

Is a Scrum Master a manager?

A

No. They are much closer to being a trainer or a coach.

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

What are the characteristics of a Scrum Master?

A
  1. Operate as a trainer or coach
  2. Administrative worker
  3. Bulldoze obstacles
  4. Shield from outer interference
  5. Conflict negotiator
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Why do most software projects fail and what is the fix for this in accordance with the Agile mindset?

A

Not because of some overwhelming technical challenge but rather because of bad communication. The Agile fix for this is to put much more emphasis on face-to-facee interactions.

17
Q

What can be said about teaching and learning in Agile teams?

A

Everyone on an Agile team should always be teaching and learning.

18
Q

What can be said about distributing knowledge in an Agile team?

A

That it should be a goal to distribute the knowledge to everyone else on the team.

19
Q

What is groupthink?

A

It’s when a group decides to agree with the opinion of the few experts in the group. Think “Sam says it’s a good idea, so it must be right.”

20
Q

What can be said about groupthink in Agile teams and why?

A

That an Agile team should avoid groupthink because everyone should be able to ask challenging questions about the product. This means that a tester should be able to ask a question to the database developer about their design of the database.

21
Q

What can be said about developers explaining their people to other people in the team in Agile teams and what does this call for?

A

That if a developer can’t simply explain their thinking to someone else, then it’s probably not a well-designed solution. So, the team should always be having face-to-face meetings where everyone’s contributing their ideas and asking challenging questions.