Project management

Question 1

What is software engineering PM

Answer 1

ensuring that software is delivered on time and on schedule and in accordance with the requirements of the organizations developing and procuring the software.

Question 2

Two categories of difficulties with building software

Answer 2

essence - conceptual structure

Accidents - realizing conceptual structure in executable form

Question 3

Some PM tools

Answer 3

MS teams, Discord, Monday.com, Slack, Asana

Question 4

Scope

Answer 4

Functions and features to be delivered to end-users
Data that are input and output
Content that is presented to users as consequence of using the software
performance, constraints, interfaces and reliability that bound the system

Question 5

two ways to define scope

Answer 5

narrative description of software scope

set of use cases

Question 6

how to determine feasibility

Answer 6

Given scope, determine resources required
Do we have the resources to build this software?
Resources to consider: people, hardware and software tools, reusable components

Question 7

Stakeholder

Answer 7

Someone impacted by project

Question 8

Goals need to be smart. What does smart stand for?

Answer 8

S - specific, significant, stretching
M - measureable, meaningful, motivational.
A - agreed upon, attainable, action oriented
R - realistic, relevant, results oriented
T - timeboxed, trackable

Question 9

Deliverables

Answer 9

LIst of items that have to be delivered to meet the goals
Say when needs to be delivered
Quality standards

Question 10

Human resource plan

Answer 10

Describe the number and type of people needed
describe roles and responsibilities
start dates, duration and how to get them

Question 11

Communications and management plan

Answer 11

who needs to be informed bout the project

how will they receive the information

Question 12

Risk management plan

Answer 12

identify all risks and be prepared if anything happens

Question 13

Range of management activities (4 P’s)

Answer 13

People - project manahgers, leaders, software team, customers, end users
Product - scope and decomposition
Process - software dev life cycle, unified process
Project - size estimation, scheduling, risk management, tracking

Question 14

13 essential roles in small software dev teams

Answer 14

course developer - prep and organization of training
database designer
implementer
integrator
process engineer - management of dev process
project manager
project reviewer
software architect
system administrator
system analyst
system tester
test manager
user interface designer

Question 15

how to choose people

Answer 15

cv
people worked with before
interviews
references and recommendations

Question 16

Activity

Answer 16

Task that takes time - duration, due date, precursor

Question 17

Milestone

Answer 17

completion of activity, check points throughout project life cycle

initiate -> plan -> execute -> close

Question 18

Deliverable

Answer 18

project result that is delivered, tangible

Question 19

Why software metrics

Answer 19

plan and manage software dev project
- estimate resources required for each activity
- metrics measure some aspect of software development
metrics are smart

Question 20

Examples of smart metrics

Answer 20

counts, percentages, sums or totals, averages, ratios

Question 21

Process metrics

Answer 21

Measure some aspect of development process

• cost to date
• time spent
• • the above can change all the time

Question 22

Product metrics

Answer 22

measure some aspect of the software product

• analysis models
• test plans
• program code

Question 23

Result metrics

Answer 23

measure outcomes - current cost of project
aka control metrics - used to determine how management control should be exercised
- measurement of the current level of progress in the project used to decide if action is necessary (to bring project back onto schedule)

Question 24

Predictor metrics

Answer 24

quantify estimates for project resource requirements
measure some aspect of a software product that is used to predict another aspect of the project/product progress (e.g. predict that system will be difficult to maintain)

Question 25

Are software metrics worth it?

Answer 25

useful for prediction and resource estimation

Question 26

Validity of predictor metrics is base don these three assumptions …

Answer 26

you can measure something useful
that measure actually predicts something worthwhile
the relationship is real and can be expressed in model/formula

Question 27

Why do software engineers think that metrics are not importatn

Answer 27

used to monitor developer performance - ethical and management issues

Question 28

Metrics for OO development

Answer 28

Application size 
class size
ability of package to absorb change (this partially depends on the ratio of abstract classes to all classes)