The Scope Plane Flashcards

0
Q

Why is the product of defining scope valuable?

A

It gives the entire team a reference point for work to be done and a language for talking about that work.

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

Why is the process of defining scope valuable?

A

It forces us to address potential conflicts and rough spots in the product while its still hypothetical.

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

What are the two main reasons to define requirements?

A

1) so you know what you’re building.

2) so you know what you’re not building.

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

Having a defined set of requirements allows you to do what more evenly?

A

Dole out work.

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

If a feature idea falls outside of scope…

A

You still might want to build it later, it’s just not being built right now.

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

If the strategy question is “Why are we making this product?” The scope question is…

A

“What are we going to make?”

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

Functionality and content seem very different but they can be dealt with in..

A

A very similar fashion

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

What are functional specifications?

A

The document containing all the detailed descriptions (requirements) of the features of the final product.

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

What are content requirements?

A

A description of the various required content elements the site will need

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

What’s a situation where functionality might have content implications?

A

Error messages are a piece of content that might be neglected without proper requirements

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

Three of the best ways to develop requirements are:

A

1) asking users
2) brainstorms with diverse groups
3) looking at competitors

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

What are scenarios?

A

A short simple narrative describing how a persona might go about fulfilling a user need.

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

Specs should be…

A

Lightweight and useful… Just describe what needs clarity and precision

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

“Be positive” means what in relation to specs?

A

It means don’t describe a bad thing the system won’t do, instead describe a positive thing it will do

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

Be specific means what in relation to specs?

A

It means objective measures are the only way to know if a requirement is met or not. “Most popular” sounds specific, “most watched” actually is

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

Don’t say “the site will look hip,” say…

A

The site will look hip according to x person or the site will meet branding guidelines.

16
Q

Content requirements should be detailed enough to describe

A

Size, format, and frequency of posting. Also who is producing the content.

17
Q

What 4 things need consideration when prioritizing requirements? What should decide?

A

Product objectives. User needs. Feasibility of the build. and stakeholder preference. Alignment with strategy is most important factor

18
Q

What’s the best approach to resolving stakeholder conflict over potential features?

A

Appeal to strategy - convince them a different feature also meets strategy and they won’t feel so attached to the feature itself.