TMAP Examp prep Flashcards

(21 cards)

1
Q

What are the 3 groups of IT delivery models?
(LO03: IT delivery models - general)

A
  • Sequential IT delivery
  • High Performance IT delivery
  • Hybrid IT delivery
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is Agile software about?
(LO03: Scrum)

A

It’s about the behavior and attitude of the people (mindset).

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

What is the difference between Scrum and DevOps? (LO03 & LO04)

A

In Scrum the deployment is at the end of each sprint, in DevOps there is continuous deployment.

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

What is Software Deployment?

A

Software deployment is the process of moving developed, tested code from a developer’s environment to a production environment where it is functional for end-users. It involves installing, configuring, and updating applications to make them operational, acting as the bridge between development efforts and live user

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

What’s the difference between Deployment and release?

A

A deployment is a technical act of moving code to a server, whereas a release is a business decision to make that feature visible to users.

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

What is fault clustering?
(LO24: Investigate and assess outcome)

A

Faults have the tendency to cluster within the same test object. If a fault occurs, chances are that other faults are there as well.

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

What are the possible test case outcomes (or results/status)?
(LO24: Investigate and assess outcome)

A

3 outcomes:
- Pass
- Fail
- Not Run

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

What are the two distinct possible causes of failing test case?
(LO24)

A

A test object fault may have various reasons e.g.:
* Fault in program code
* Configuration problem in IT system
* Firmware or hardware problem
* Etcetera

A test case fault may have various reasons e.g.:
* Wrong expected outcome
* Wrong test data
* Wrong interpretation of specification(s)
* Etcetera

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

What’s a good remark/tip about analyzing a failed test?
(LO24)

A

The investigation may be a tedious and time-consuming tasks:
- Apply pair debugging if necessary
- Start investingating the test case (to prevent waisting time)
- The investigation always involves human activity, it can not be (fully) automated.

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

Steps for analyzing the failed test case and creating an anomaly?
(LO24)

A

These steps are in a generic order but may also be done in parallel or in a different order.

  • Gather evidence (such as screenshots or database dumps)
  • Reproduce the failure (and register the steps to reproduce)
  • Check for faults in the test
  • Determine suspected cause(s)
  • Isolate the cause (optional)
  • Generalize the anomaly
  • Compare with other anomalies and eliminate double
  • Register the anomaly report
  • Have the anomaly report reviewed
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What are the fundamental activities of a DevOps team?
(LO05 - K2)

A

Monitor
Plan
Code
Integrate
Deploy
Operate

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

What is the VOICE model definition and why is it used by High-performance IT delivery teams?
(LO01 - VOICE model)

A

The VOICE model is about
establishing the level of confidence
that the pursued business value
can be achieved. It consists of 5 terms: Value, Objectives, Indicators, Confidence and Experience.

High-performance IT delivery teams (such as in Scrum and DevOps) use the VOICE model as a foundation to structure and organize their work.

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

How do the VOICE model elemnts realte to each other?
(LO01: VOICE model)

A

The main reason for building a business is to create Value. Thius value will the be detailed into Objectives. We use Indicators in order to measure wether these objectives are met. The results of resting indicators will establish a Confidence level for the stakeholders, which will support the decision wether or not the (version of) system will go live. When the IT system is used, the users Experience the real value

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

To which DevOps activities does each VOICE item relate?
(LO01 & LO05)

A
  • Value: “Monitor” and “plan”
  • Objectives: “Monitor” and “plan”
  • Indicators: defined in “plan” and measured in all other activities (“code”, “integrate”, “deploy”, “operate”, “monitor”)
  • Confidence: “deploy”, “operate”, “monitor”
  • Ecperience: “operate”, “monitor”
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are the different scopes of the VOICE model?
(LO01: VOICE model)

A

Scope of business delivery, which contains:
- Scope of value definition
- Scope of IT delivery
- Scope of IT use

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

What are the 4 group of indicators defined in TMAP?
(LO02: Indicators)

A

Business value related indicators
 Customer satisfaction
 Number of service calls to helpdesk

IT delivery related indicators
 Business features done
 Percentage of availability (up-time)

Team related indicators
 Availability of necessary skills
 Satisfaction and happiness of team
members

Problem related indicators
 Number of anomalies registered compared to expected
 Mean time to fix operational failures

17
Q

What are the 2 QA & testing topics and what’s the difference between them?
(LO11: Introduction to QA & testing topics)

A

The 2 topics are:
- Organizing: that’s about managing and organizing multiple teams.
- Performing: this one is about operating and managing test activities within one team.

18
Q

What are the organizing test topics?
(LO11: Introduction to QA & testing topics)

19
Q

What are the performing test topics?
(LO11: Introduction to QA & testing topics)

20
Q

What is Monitoring & control?
LO14 – K2

A

Monitoring is continuously gathering feedback, using tools,
of the indicators of the IT system throughout the IT delivery
cycle and use that information to forecast the behavior of
the IT system.

Control is to take adaptive measures, based on monitoring
information, to ensure proper behavior of the IT system
throughout the IT delivery cycle.

21
Q

How do we Monitor (what does monitoring use?
LO14 – K2

A

Quality indicators
* Related to business value
Team performance indicators
* May relate to one or multiple teams
* Is about the team and the performance (e.g. progress) of the team
Functional system indicators
* Heartbeat, healthcheck
* Logging & tracing
* Auditing
Non-functional indicators
* CPU, memory, diskspace, network, etc.