POM L2 Flashcards

1
Q

Project Definition (What is it consist of? )

A

A project consists of (SARD)
• A start date and duration
• A set of deliverables to a client • A schedule
• All technical and managerial activities required to produce and deliver the deliverables
• Resources consumed by the activities

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

Modeling a project: Dynamic model

A
  1. Definition (do/define scope)
  2. Start (do/Assign Tasks)
  3. Steady state (do/develop state)
  4. Termination (do/deliver system)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Modeling a project: Dynamic model

A
  1. Definition (do/define scope)
  2. Start (do/Assign Tasks)
  3. Steady state (do/develop system)
  4. Termination (do/deliver system)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Project as a class

A

has Attributes:

  • Start Date
  • Duration

has Methods:

  • Define Scope()
  • Assign Tasks()
  • Develop System()
  • Deliver System()
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Project Manager as a class

A

has Methods:

  • Administer Resources()
  • Maintain Accountability()
  • Meet Project Goals()
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Role

A
  • defines a set of responsibilities (a duty or a task)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Roles: System Architect

A

System architect
• Decompose the system into subsystems
• Choose a software architectural style
• Select the system integration strategy

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

Role: Minute taker

A

Minute taker
• Record the meeting
• Identify action items and issues
• Distributed the minutes to the participants and other stakeholders

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

Role

A
  • defines a set of responsibilities (a duty or a task)

Responsibilities are assigned to toles, roles are assigned to people and people are assigned to teams.

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

Role assignments to people

A
  • One-to-Oe
  • Many-to-Few (danger of overcommitment)
  • Many-to-“Too-Many” (Some people don’t have significant roles)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Problems in Role Assignments

A
  • Incompetence: The wrong person fills the wrong role
  • Useless role: The role exists only to minimize damage
    control
  • Increase of Bureaucracy: The role swells unnecessarily simply because it can.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Bad role assignments

A

Incompetence => Peter Principle:

“Employees who perform their roles in a hierarchy with competence are promoted to a higher level until they reach a level where they are no longer competent. There they remain forever”
-Solution: It makes little sense to take your most brilliant engineer
and have him or her manage people and budgets
#Useless role => Dilbert’s Law
“promote least- competent employees to management (generally middle management), to limit damage they are capable of doing”
-solutions: Put individuals to work in their core competencies.
#Increased Bureaucracy => Parkinson’s Law
„Work expands to fill the time available for its completion“
- Dont wait for the last minute

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

Task

A

A task describes the smallest amount of work monitored (tracked) by the project manager (Typically 3-10 working days effort).

Tasks are associated with a:

  • Role
  • Work Package
  • Work Product
  • Start date
  • Duration
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Task

A

A task describes the smallest amount of work monitored (tracked) by the project manager (Typically 3-10 working days effort).

Tasks are associated with a:

  • Role
  • Work Package
  • Work Product
  • Start date
  • Duration
  • Required resources

If a task size is too large, the task should be renamed into an activity, decomposed into smaller task sizes that allow monitoring.

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

Activity

A
  • An activity is a major unit of work • Culminates in a project milestone
  • A project milestone is a scheduled event used to visualize/measure progress
  • A project milestone is visible to the customer
  • A project milestone usually produces a baseline
  • Activities can also have internal checkpoints
  • These are not externally visible to the customer
  • Precedence relations often exist among activities
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Unit of Work

A

A task or an activity that contains other tasks and lower-level activities

17
Q

Project Function

A

Project Function: An activity that spans the entire duration of a software project. Examples of project functions include project management, configuration management, quality assurance, and verification and validation.

18
Q

Project Function

A

Project Function: An activity that spans the entire duration of a software project. Examples of project functions include project management, configuration management, quality assurance, and verification and validation.

Examples of Project Functions:

  • Project management
  • Documentation
  • Configuration Management
  • Testing

Sometimes project functions are also called cross-development processes or Integral processes.

19
Q

Name 3 Meeting roles !

A
#Minute taker : Record the meeting and identify actions
#Time Keeper: Keep track of time
#Primary facilitator: Organize the meeting and guide the execution
20
Q

What types of role do exist ? (Role Taxonomy )

A
(CoDeMaLi)
#Developer
#Manager
#Liaison (Connector)
#Consultant
21
Q

What is a work package ?

A

A task or activity is specified by a work package which
contains:
• Description of work to be done
• Preconditions for starting, duration, required resources
• Work products to be produced, acceptance criteria for it
• Risks involved
• A work package must have completion criteria

22
Q

Explain the Functional Organization (ad/disadv.) !

A

In a functional organization people are grouped into

departments, each of which addresses an activity (Analysis, design,
integration, testing, delivery)
#Projects are pipelined through the departments
+Members of a department have a good understanding of the functional area they support
-High chance for overlap or duplication of work among
departments.

23
Q

Explain Project-based Organization !

A

• In a project-based organization people are assigned to a project, each of which has a problem to be solved in a

certain time within a given budget
# Teams are assembled for a project when it is created
• Each project has a project manager
+Very responsive to new requirements
-Teams cannot be assembled rapidly

24
Q

What are differences btw Flat Staffing vs Gradual Staffing ?

A
# Gradual Staffing: 
• The organization is gradually ramped up by hiring people as needed
# Flat Staffing: 
• All the participants are assigned at the start of a project
25
Q

When to use a Project-based Organization ?

A

• Project has high degree of uncertainty
• Open communication is needed among participants
• Requirements are expected to change during the project
• New technology that could effect the outcome may appear
during the project.

26
Q

Explain the matrix Organization !

A

In a matrix organization, people from different departments of
a functional organization are assigned to work on one or more
projects
+ Teams for projects can be assembled rapidly from the
departments
+Expertise can be applied to different projects as needed
-Team members are often not familiar with each other
- “Double-boss problem”:

27
Q

What is “Double-boss problem”

A

When Team members must respond to two
different bosses with different focus:
• Focus of the manager of the department
• Focus of the project manager

28
Q

What is Project Organization Structure and name 3 relationships !

A

A project organization defines the structure among the

members (participants) of a project in terms of
relationships
1)Decision structure : It models the control flow: Who decides what?
2) Reporting structure: Who reports their status to whom?
3) Communication structure : It models the information flow: Who facilitates
communication with whom?
#Org-chart usually visualize these 3 structures in one graph with a single hierarchical relationship

29
Q

What are the communication skill for software project manager ?

A

• Collaboration: Negotiate requirements with the client and with
members from your team and other teams
• Presentation: Present a major part of the system during a review
• Technical writing: Write part of the proposal, part of the project
documentation
• Management. Facilitate a team meeting, find compromises, negotiate
between conflicting demands

30
Q

What are the 2 communication events ?

A

Planed communication,

Event-driven communication

31
Q

What is Communication mechanism:

A

Tool or procedure that can be used to deal with a communication event

#Synchronous mechanism: Tool requires communication
partners to be available at the same time
• Asynchronous: Tool does not require communication
partners to communicate at the same time.

32
Q

Name some communication events !

A
#problem definition
#client review
#walk trough
#project review
#inspection
33
Q

Name examples for communication mechanism(both synchronos and asynchronos)

A
#Synchronous :
-Informal meeting 
-Formal meeting
#Asynchronous
-Emails
-Forums