DeepDive Management Flashcards

1
Q

‘Time-and-Material’ (T&M) contracts

A

when the project effort is not clearly predictable. In this type of contract, client pays the software vendor by total number of hours/days of effort put into the project

Application maintenance projects normally are contracted on a T&M basis.

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

fixed price software contract

A

defines the service to be provided and states a single price for the project regardless of how much time and expenses the software service vendor incurs

most commonly deployed in the Development or Re-engineering type of projects.

two subtypes:

  • Fixed price for fixed amount of work in fixed schedule
  • ) Fixed price for fixed scope (applicable only if scope is very well detailed during the contract phase
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Acceptance criteria

A

an explanation attached to the user story which describes how a particular user story will be tested and accepted

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

Regarding Contract Negotiation

A

Collaboration with customer is more valuable than the contract mediation

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

Contracts in Agile projects

A
  • The contractual agreements pertaining to procurement process should be varied in Agile projects.
  • The legal aspects of Agile project contracts need to be changed as compared to the traditional project contracts
  • If Contractual agreements are not aligned in context of execution of Agile projects, it would likely to get into challenges and risks.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Since Sprint duration is internal to Agile project execution, it must not be covered as part of project contract.

A

True

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

At what stage of the project ‘Definition of Done’ criteria for Sprint and Release level should get discussed?

A

At the Sprint Planning

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

Software projects are typically controlled by four major variables

A
  • Schedule
  • Scope
  • Cost
  • Effort
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Estimation is done at the following three stages

A
  • Proposal or Project Level
  • Release Level
  • Sprint Leve
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

function point

A

the metric which converts requirements or user stories into a number.

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

Quick Function Points

A

method is a unique approach for rapidly estimating FP

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

DETs

A

Data Element Types

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

RETs

A

Record Element Types

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

FTRs

A

File Type Referenced

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

ILFs

A

Internal Logical Files

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

EIFs

A

External Interface Files

17
Q

Story Point

A

represents the relative amount of work required to implement a feature, compared to other features.

18
Q

4D framework

A
  • Demand, Fit Gaps Business processes, System Landscape, NFRs, Product defects and Information Architecture will be taken as inputs.
  • Determine, These rationalized list of requirements will be analyzed based on their business relevance during, and they will be mapped to Epics and Themes
  • Define, stage the User Stories will be derived by analyzing technical feasibility, business benefits and they will get updated in the Product Backlog
  • Decide, stage they will be groomed and prioritized in terms of risk and dependency and the groomed product backlog will be created.
19
Q

Infrastructure Planning for Agile is needed only when projects are executed in distributed environment.

A

True

20
Q

Process Performance Models (PPMs)

A

enable the team to validate size and determine effort and schedule by applied estimation technique

21
Q

Sprint Retrospective report

A

aims at providing leading indicators, like Velocity, Defect Density, for project progress to identify corrective and preventive actions

22
Q

What is the purpose of setting goals at a Project, Release and Sprint level?

A
  • To help team plan the project better in terms of realistic targets, appropriate strategies and quantitatively track Project/Sprint progress
  • To monitor the project progress and update internal stakeholders in an objective manner
23
Q

‘Risk Profiler

A

risk assessment questionnaire

24
Q
A