-
Notifications
You must be signed in to change notification settings - Fork 12
/
Exam1QandA.txt
134 lines (91 loc) · 6.21 KB
/
Exam1QandA.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
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
Software Engineering Profession
-------------------------------
(Not covered on exam 1; covered on 2 or 3)
Requirements
------------
Q1. Are Requirement documents necessary for projects?
A1. Yes, requirement documents describe what a particular software does or shall do. It is produced and consumed by everyone involved in the production of software. (Andrew L.)
Q3. What is the difference between functional and non-functional requirements? - Jonathan W.
A3. Functional requirements are discrete (Either the feature is present or it's not). (Paul B.)
Q4. Name and describe the 3 types of requirements (John Donich)
A4.(John Donich)
1. Functional Requirements - the primary features of the app,
2. Non-functional requirements - things like suability, and quality requirements,
3.and constraints - the basic parameters of the project like the type of solution used or specific time frames for completion.
Q5. Are Requirement documents necessary for projects?
A5. Yes, requirement documents describe what a particular software does or shall do. It is produced and consumed by everyone involved in the production of software. (Andrew L.)
Q6. Are Requirement documents necessary for projects?
A6. Yes (Rob Williams)
Q7. What is the difference between functional and non-functional requirements? - Jonathan W.
A7. Functional requirements are discrete (Either the feature is present or it's not). (Paul B.)
Non-Functional requirements are continuous - present to some degree (scalable) ie. Ease of Use: Less <-|-|-> More (Paul B.)
Q8. Which type of requirement is more likely to be present to a degree - more or less present? (Kingsley)
A8. Non-Functional Requirements (Kingsley)
Project Management
------------------
Q1. All tasks on the critical path must have non-zero free slack and non-zero total slack. (Eddie B.)
A1. Yes (Jinal)
A1. True (Andrew B.)
Q2. What, if anything, is wrong with reporting the status of a user story or milestone as "kind of done"?
A1. It's ambiguous. - Aaron H.
A2. Nothing. - Aaron H.
Q3. What are four variables of a Project? (Jinal)
A3. Scope, Time, Resources, and Quality (Rob Williams)
Q4. How are effort and duration used? (Jose)
A4. Effort is used to measure resource usage and duration is used in scheduling. (Jose)
Q5. Why is a risk management plan important? (Aaron S.)
A5. This allows you to mitigate the damage that potential risks have, and allows you to follow a procedure when something goes wrong. (Dan R.)
Project Planning
-----------------
Q1. Why is it important to have project planning in every project? - Andrew L.
A1. A project plan will allow you to know if you are on track for your goals, and what is expected in the future. (Ben S.)
Q2. Describe effort and duration. (Jinal)
A.Duration is amount of calendar time or clock time required to finish the task. (Jinal)
Effort is amount of labor required to finish the task. (Jinal)
Q3. Why refer to a project plan as a living document? (Kingsley)
A3. This is because project plan evolves/grows/changes along with the project as the conditions change during the project life. (Kingsley)
Q4. Give the four main components of a project plan. - Jarred
Q5. In the project lifecycle, what comes after the Initial Project Planning? - Jarred
A. Preliminary Requirements Development
B. Release Planning - This one (Jarred)
C. Candidate Architecture Specification
D. Lunch
Working in Teams
----------------
Q1. Give several examples of ground rules for a team. (Eddie)
A1. Practice mutual respect ever day. Meetings will start and end on time. Honesty before cohesiveness.
<<<<<<< HEAD
=======
Q2. What are some range of responses to a conflict
A2. Do nothing. Private Conversation between affected members. Professional Airing of grievances. ---(Lukman B.)
Q3. Name three characteristics of a highly functional team. --(Lukman B.)
A3. Healthy relationships. Efficient and Effective. Energizing. Unity, Trust and Shared Purpose.----(Lukman B.)
Q4. Describe how conflict might be beneficial to a project. (John Donich)
A4. (John Donich)
Healthy conflict requires you to understand the motivations and outcomes of your stated project better because you have to defend your ideas.
It also brings out the weaknesses in your planning as those who oppose the plan are more likely to see flaws and thus you can address those issues.
Q5. What are the reasons that make developers "Going Dark"?
Q6. What are the four stages of team development? - Jonathan W.
A6. Forming, Storming, Norming and Performing - Jonathan W.
Q7. What are the reasons that make developers "Going Dark"?
A7. i) avoid criticism ii) retain authorship of new work (Paul B.)
Q8. What are the 3 principles of a healthy interaction? Which one is LEAST likely to mitigate ego programming? (Paul B.)
A8. Respect, Trust, and Humility are three foundational principles of healthy team interaction. Trust is the least likely to mitigate ego programming. (Andrew B.)
Q9. Why is team conflict good? (Andrew B.)
A9. Conflict in a team prevents groupthink and allows a variety of ideas to be considered. (Aaron S.)
A9. Adds to the creative process and can increase inter-team competition. - Jarred
Q10. At what stage of team development are teams least productive? (Andrew B.)
A10. Teams are least productive during the 'storming' stage of team development. (Andrew B.)
Q11. What are the four stages of team development? - Jonathan W.
A11. Forming, Storming, Norming and Performing - Jonathan W.
GIT / Github
-------------
Q1. What's the difference between fork and clone? - Aaron H.
A1. Fork only allows clone on the server side and clone is a copy of a repository. (Andrew L.)
>>>>>>> upstream/master
Q2. What's the difference between committing and pushing in Git? (Rob Williams)
A1. Commiting is the action of saving it to your local repository and prepping the document(s) to be transferred to the server-side. Pushing is the action of sending
the document to the server. (Dan R.)
Q3. What is the difference between a branch and a fork? (Aaron S.)
A1. A fork is a team member's work, "forked" from the main repository. A branch is an individual version of the project or experimental work. (Dan R.)
Q4. Since Github is public by default, does the original owner have any control of WHO gets to fork or branch off from their original code? (Ben S.)