Project Planning Flashcards

1
Q

Parts of Software Pricing:

A
  1. Contract
  2. Uncertainty
  3. Financial
  4. Market
  5. Volatility
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What does the customer pay for?

A
  1. Requirements/functionality delivered
  2. Scheduled Deliverables
  3. Milestones
  4. Documents
  5. Tests
  6. Code
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Work Breakdown:

A
  1. Iterations
  2. Milestones
  3. Tasks
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

The Planning Process:

A
  1. Startup Phase
    - Initial project plan is created
  2. Development Planning
    - Monitor progress,update plan with actuals
    - Revise plan to reflect changes
    - Requirements
    - Schedule
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Define Project Scheduling:

A

Decide how to work in a project will be organized

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

Agile Planning:

A
  1. Release planning
    - Look ahead for several months and decide on the features that should be included in the release of a system.
  2. Iteration Planning
    - Focuses on planning the next increment of a system,
    - Typically 2-4 weeks of work for the team.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Agile Planning Approaches:

A
  1. Planning in SCRUM

2. XP Planning “Game”

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

Planning in SCRUM:

A

Based on managing a project backlog (things to be done) with daily reviews of progress and problems

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

Planning in XP

A
  1. Based on user stories and the amount of time required to implement them
  2. Stories are assigned “effort points” reflecting their size and difficulty of implementation
  3. The number of effort points implemented per day is measured giving an estimate of the team’s “velocity”
  4. This allows the total effort required to implement the system to be estimated.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

How are Agile tasks allocated?

A

During the task planning stage, the developer break down stories into development tasks

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

Agile Task Allocation Steps:

A
  1. A development task should take 4-16 hours
  2. All of the tasks that must be completed to implement all of the stories in that iteration are listed
  3. The individual developer then signs up for the specific tasks that they will implement.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Ideal time vs Elapsed Time Example:

A

Ideally: Monday has 8 hours for the project BUT:
2 Hours of meetings
2 Hours of emails
4 Hours left for the project

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

Requirements Development (Elicitation and Analysis):

A
  1. All the activities involved with discovering requirements

- Interviews, workshops, document analysis, prototyping

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

What is a viewpoint?:

A

Stakeholders with the same perspective can be grouped together in a “viewpoint”

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

Interactor Viewpoint:

A

The point of view of primary actors

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

Indirect viewpoint:

A

The point of view of the supporting actors

17
Q

Domain viewpoint

A

The point of view of the domain

18
Q

Techniques / Methodologies (Interviewing):

A
  1. Closed interviews
    - Predefined questions
  2. Open interviews
    - No agenda, exploratory
  3. Strengths and weaknesses
19
Q

Techniques / Methodologies (Observation / Ethnography):

A
  • Discover the state of actual practice
  • Interaction with others, context
  • Strengths and weaknesses?
20
Q

Prioritization Scale:

A
  1. Urgent / Important
  2. Urgent / Not so important
  3. Not so urgent / Important
  4. Urgent / not so important
21
Q

Use-Cases:

A

Describe a system’s behaviour under various conditions as the system responds to a request from a stakeholder.

22
Q

Use-Case Diagram Elements:

A
  1. System

2. Actor

23
Q

Primary Actors:

A

Initiates use of the system

24
Q

Supporting Actors:

A

Provide a service (to the system)

25
Q

Offstage Actor:

A

Has an interest in the behaviour but is not primary or supporting.

26
Q

What is a Use-Case:

A
  1. An action that accomplishes a task in the system
  2. Named a verb
  3. Each actor is linked to a use case through relationships
27
Q

Relationships for Use-Cases:

A

Extend and Include