-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathinit-en.txt
81 lines (56 loc) · 2.07 KB
/
init-en.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
Initial questionnaire for Project-Practice-Outcome database: establish baseline
==============================================================
I. Contact information
II. Project information
Start date should be counted as "first date when a participant with 'build' responsibilities (developer, architect, etc.) becomes involved full-time".
* Project start date - development:
* Team size (build):
* Team size (total full-time personnel):
* Other participants:
Per team member:
* specialization (dev, PM, test, etc.)
* experience in SW development (years)
* experience in Agile (years/months)
* domain expertise: low - some - high
* expertise in project tech: low - some - high
* Project input: document type (charter, user stories, use cases, text) and size
* Short description of project goals:
III. Effort information
* Project type: embedded - commercial - IS - web - other
* Project situation: greenfield - extension - porting - other
* Project domain:
* Project technology platform:
* Target man-month budget:
* Target end date:
* Target size if known (in KLOC, FP, User Stories):
* Customer(s):
IV. Ergonomic factors
* Participant locations (count):
If distributed, per location:
* which team members:
* office layout (dedicated room - open office - single office):
* communication facilities (Web/email - phoneconf - videoconf - other):
V. Outcomes
* Project objectives (short form):
Per objective:
* means of measurement/observation:
* baseline (current) level of satisfaction:
VI. Practices
* Agile practices intended on this project:
Per practice:
* already used previously:
* objective the practice contributes to:
Per skill AND team member:
* level of proficiency with this skill (low - medium - high)
* Agile practices ruled out on this project:
Per practice:
* reason excluded (constraint - cost - no benefit):
* replacement or mitigation:
VII. Internal data collection
Are you planning to collect and willing to share the following data:
* velocity or lead time history
* test coverage and test:source ratio
* CI build history
* defect counts
* source code analysis outputs
* other