Project Planning Flashcards Preview

Software Engineering Test 2 > Project Planning > Flashcards

Flashcards in Project Planning Deck (27)
Loading flashcards...
1

Parts of Software Pricing:

1.Contract
2.Uncertainty
3.Financial
4.Market
5.Volatility

2

What does the customer pay for?

1.Requirements/functionality delivered
2.Scheduled Deliverables
3.Milestones
4.Documents
5.Tests
6.Code

3

Work Breakdown:

1.Iterations
2.Milestones
3.Tasks

4

The Planning Process:

1. Startup Phase
- Initial project plan is created
2. Development Planning
- Monitor progress,update plan with actuals
- Revise plan to reflect changes
- Requirements
- Schedule

5

Define Project Scheduling:

Decide how to work in a project will be organized

6

Agile Planning:

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.

7

Agile Planning Approaches:

1. Planning in SCRUM
2.XP Planning "Game"

8

Planning in SCRUM:

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

9

Planning in XP

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.

10

How are Agile tasks allocated?

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

11

Agile Task Allocation Steps:

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.

12

Ideal time vs Elapsed Time Example:

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

13

Requirements Development (Elicitation and Analysis):

1.All the activities involved with discovering requirements
-Interviews, workshops, document analysis, prototyping

14

What is a viewpoint?:

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

15

Interactor Viewpoint:

The point of view of primary actors

16

Indirect viewpoint:

The point of view of the supporting actors

17

Domain viewpoint

The point of view of the domain

18

Techniques / Methodologies (Interviewing):

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

19

Techniques / Methodologies (Observation / Ethnography):

- Discover the state of actual practice
- Interaction with others, context
- Strengths and weaknesses?

20

Prioritization Scale:

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

21

Use-Cases:

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

22

Use-Case Diagram Elements:

1. System
2. Actor

23

Primary Actors:

Initiates use of the system

24

Supporting Actors:

Provide a service (to the system)

25

Offstage Actor:

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

26

What is a Use-Case:

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

Relationships for Use-Cases:

Extend and Include