Essentials of the Essentials Flashcards

1
Q

4 principles of agile PROJECT management (DYBA)

A
  1. Minimal critical specification
  2. Autonomous teams
  3. Redundancy -> people can do more tasks
  4. Feedback and learning.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the four steps in waterfall approach, what do they deliver, and which two additional steps can be added?

A
  • Analysis (–> requirements)
  • Design (–> specification)
  • Implement (–> software)
  • Test
  • Adoption;
  • Maintenance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Conditions when Agile is useful?

A
  • Complex problem;
  • Solutions are initially unknown;
  • Requirements will change;
  • Work can be modularized;
  • Close collaborations with end-users is possible;
  • Creative teams will outperform other types of teams;
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Four difficulties in software engineering according to brooks?

A
  • Complexity
  • Conformity
  • Changeability
  • Invisibility
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is complexity according to Brooks?

A
A function of:
Number of components (volume)
Types of components (variety)
Number of attributes (depth)
Number of relations (dependencies
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Through which quadrants go each phase in the spiral model?

A
  1. Objectives determination and alternative solution identification;
  2. Identify and evaluate risk
  3. Develop next version of the product;
  4. Review and plan for next phase;
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the 4 requirement principles proposed by Jarke?

A
  1. Intertwine requirements with organizational context
  2. Evolve designs and ecologies
  3. Manage through architecture
  4. Recognize and mitigate against design complexity
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

How do you adress complexity and how not?

A
  • Have a loosely coupled architecture to prevent dependencies;
  • Centralization -> entities linked to central entity, not to all entities;
  • Standardization
  • Re-use of modules
  • Buy instead of build

Do NOT add extra man at the last phases.

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

How do you calculate the cashflow?

A

Benefits - Cost

Sometimes specified per year.

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

How do you calculate payback period?

A

Investment / cashflow

Investment = investment cost

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

How do you calculate return on investment (ROI)?

A

((expected benefits - expected cost) / expected cost) * 100%

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

How do you calculate NPV?

A

( SUM of (Benefits - cost) / (1 + R)^t ) - initial investment

NPV > 0 –> do the project

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

What is the formula from cocomo II

A

E = (A) (KLOC^b) (EAF)

E = effort in person months
A en B = given
KLOC = number of lines x 1000
EAF = given -> contextual, between 0.9 - 1.4 (effort adjustment factor)

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

Sprint burndown chart?

A

Shows remaining work in a sprint backlog, updated every daily scrum

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

Release burn up chart?

A

Progress towards the end product -> shows progress and what each sprint contributed

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

What are the similar principles between Lean and Agile?

A
  • Value through better allignment with customer;

- Flow (sprints, continious delivery, immediate feedback)

17
Q

What is lean six sigma and what are the steps?

A
  • Data driven improvement focused on problems
    5 steps: DMAIC
  • Define
  • Measure
  • Analyze
  • Improve
  • Control
18
Q

What is DevOps, what are the phases and what is the challenge?

A
  • Collab between developers and operations (building it)
  • Increase speed of comitting to change and actual changing the system
  • Challenge: IT audit -> specific roles and segration of roles.

DTAP street:

  • Develop environment
  • Test environment
  • Acceptance test environment
  • Production of the environment
19
Q

Key concepts of continious development (fitzgerald and stol 2015)?

A
  • Aligning business, development and operations;
  • Combining practices of agile and lean;
  • Implies constant change -> challenge: trade off between stability and flexibility
  • It has implications on safety and security
  • Resilience and robustness;
20
Q

Four ways to get money from OSS?

A
  1. Selling services around the software (training/maintenance);
  2. Open core model
    - Selling extensions such as security
    - Dual licensing (personal / enterprise)
  3. Software as a service
    Subscription to access certain features
  4. Voluntary donations
21
Q

What is the development life cycle of an OSS?

A
  1. Planning
    First prototype on personal idea
  2. Analysis
    Feedback from community, discussion, ratification
  3. Design
    Modular design, define core and interfaces
  4. Implementation
    Fork and merge, incremental changes
  5. Maintenance
    - Report of issues
    - Triage
22
Q

What is the development life cycle of a commercial software?

A
  1. Planning
    Organizational objectives, alternative solutions, cost/benefit
  2. Analysis
    Convertion of goals in functions. Obtaining requirements
  3. Design
    Describing of features, layouts and documentation
  4. Implementation
    Develop and test -> waterfall/agile
  5. Maintenance
    Incident management
23
Q

What is meant by Impose with Leeway?

A
  • Be very strict in some ways like deadlines;

- Leave room for discussion with details (for stakeholders);

24
Q

What is an E3 diagram?

A

A network diagram that shows the exchange of things / value between the actors.

Shows:

  • Mutual dependence;
  • No value leak for sustainable network;
25
Q

What is the power interest grid?

A

A simple grid that shows the power (low to high) on the horizontal axis and the interest (low to high) on the vertical axis.
Shows the stakeholders.
From left under, to right under, to left top to right top:
- Crowd
- Context setters
- Subjects
- Players

26
Q

What is an other way to deal with stakeholders and issues?

A
  • Make a mindmap.

- All the stakeholder groups are linked to potential issues they might have;

27
Q

What is the problem-frame stakeholder map?

A

Same as power interest grid, with power (low to high) on the horizontal axis and support on the vertical axis (low to high).
Shows which of the stakeholders support your ideas and also if they can do something about it.
From left under to right under, to left top to right top:
Weak opponent
Strong opponent
weak supporter
strong supporter

28
Q

What do spotify and rabobank want from their team?

A
  • High autonomy and high alignment