#separator:Pipe
#html:true
#notetype:Basic
#deck:ASPICE 4.1::05 Level 2, managing performance
#tags:aspice::lesson-05
#guid column:3
#columns:Front|Back|GUID
From level 2 up, what kind of indicator does the PAM use, and how is it applied?|Generic practices: the same GPs applied to every process in scope. “SUP.10 at level 2” means the GPs of PA 2.1 and PA 2.2 applied to change request management. (PAM §3.3.1, p. 23)|aspice-05-01
List the six generic practices of PA 2.1 in order.|2.1.1 objectives and strategy · 2.1.2 plan the performance · 2.1.3 determine resource needs · 2.1.4 make resources available · 2.1.5 monitor and adjust · 2.1.6 manage the interfaces. (PAM §5.3.1, pp. 101–103)|aspice-05-02
Which generic practice is the keystone of PA 2.1?|GP 2.1.1: identify the process performance objectives and define a strategy. Everything else in PA 2.1 hangs off it.|aspice-05-03
What is a process performance objective, and what two things is it not?|A target for how one process is performed, e.g. “all CRs analysed within 5 days”. Not a project goal (a release date, a budget), and not a restatement of the process's outcomes. (PAM GP 2.1.1 note 1, p. 101)|aspice-05-04
Is “Release 3.0 ships on 1 March” a process performance objective?|No: it is a project goal.|aspice-05-05
Is “Change requests are approved before implementation” a process performance objective?|No: it restates a SUP.10 outcome. Objectives say how the outcomes are organised, not that they happen.|aspice-05-06
Is “No more than 10 open change requests six weeks before each release” a process performance objective?|Yes: a target for how SUP.10 is performed.|aspice-05-07
Do process performance objectives need MAN.6-style measurement or level 4 statistics?|No. They may be quantitative or qualitative, ideally SMART. (Guidelines §4.1.2.1, p. 235)|aspice-05-08
Must a level 2 process performance strategy be a written document?|No. Tools that enforce a workflow, automated pipelines and CI all count. (Guidelines §4.1.2.2, p. 236)|aspice-05-09
Are explicit process descriptions required at level 2?|No, “providing the PA achievements are met”. (Guidelines §4.1.1, p. 234)|aspice-05-10
How do the ratings of MAN.3 and PA 2.1 of other processes relate?|MAN.3.BP4–BP8 should be in line with GP 2.1.2–2.1.6 of the other processes; a gap of more than one NPLF step suggests an inconsistent rating. (Guidelines §4.1.3.2, p. 245)|aspice-05-11
Seat-Heat reviews a dashboard of overdue bugs and re-plans the sprint when the target is breached. Which GP?|GP 2.1.5 monitor and adjust.|aspice-05-12
A named triage rota and 20 % of sprint capacity reserved for bugs. Which GP?|GP 2.1.4: resources identified and made available.|aspice-05-13
OEM bugs arrive via their portal, and the triage owner answers there within a day. Which GP?|GP 2.1.6 manage the interfaces between the involved parties.|aspice-05-14
Bugs are logged, analysed and fixed “when people have time”. Can SUP.9 still reach PA 1.1 = F? What about PA 2.1?|PA 1.1 can be F: problems are recorded, analysed and closed. But there is nothing for PA 2.1 to rate: no objective, plan, resources or monitoring.|aspice-05-15