Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 3 (Management activities (Project planning :male-office-worker:…
Chapter 3
Management activities
Project planning :male-office-worker:
Planning stages
Bidding for a contract to develop /provide a software system
Modify your plan in the light of experience gained
Project planning
Proposal planning
Outline software required
Aim :bow_and_arrow:
Provide information that will be used in setting a price for the system to customers
Software pricing
Challenge? :warning:
Development cost + price charged to customer = :red_cross: simple
What for:question:
Estimates are made to discover the cost to producer of producing a software system.
Software
Hardware
Travel
Training
Effort cost
Factor :page_facing_up:
Broader organisational
Economic
Political & business
Types
Quality Plan
Validation Plan
Configuration Management Plan
Maintenance Plan
Staff Development Plan
Project Scheduling
Project Milestones
Points in the schedule against which you can assess progress
Eg: Handover of the system for testing
Project Deliverables
Work products that are delivered to the customer.
Eg: Requirements document for the system
Schedule Representation
Graphical notations
Bar charts
Reporting :writing_hand:
Risk Management :!!:
Objective :goal_net:
Identifying risks
Drawing up plans to minimize their effect on a project
What for:question:
Project risks
affect schedule / resources
Product risks
affect the quality / performance of the software.
Business risks
affect the organisation developing / procuring the software.
RM Process :thinking_face:
Risk Identification
Risk Analysis
Risk Planning
Risk Monitoring
People Management
:silhouettes:
What for:question:
:-1::skin-tone-2: people management = :arrow_up: project failure
:silhouettes:= organisation's most important assets
Factor :newspaper:
Consistency
Respect
Inclusion
Honesty
Need Satisfcation :fireworks:
Social
Provide communal facilities.
Allow informal communication.
Esteem
Recognition of achievements
Appropriate rewards
Self-realization
Training
Responsibility
Motivation :<3:
Types of Motivation
Basic Needs (eg: food, accommodation)
Personal Needs (eg: respect, self-esteem)
Social Needs (eg: recognization)
Personality types
Task-oriented
Self-oriented
Interaction-oriented
Group Cohesiveness :umbrella_on_ground:
Advantages
Quality Standards
Learning
Knowledge
Continual Improvement
Effectiveness of a team
People in the Group
Group Organization
Technical & Managerial Communications
Selecting Group Members
Cohesive Group
Aim for Balancing
Challenges in assembling a team
Project budget may not allow for the use of highly-paid stuff.
Staff with the appropriate experience may not be available.
An organisation may wish to develop employee skills on a software project.
Proposal Writing
:computer:
Criteria for :100: software project
Time :timer_clock:
Cost :money_with_wings:
Expectation :eyes:
Team :silhouettes:
Software management distinctions
Product is intangible.
Many software projects are 'one-off' projects.
Software processes are variable & organization specific.
Objective
:goal_net:
Ensure that software is delivered on time & on schedule.
In accordance with the requirements of the organisations developing & procuring the software.
Why need Software Project Management (SPM)?
Always subject to budget.
Schedule constraints that are set by the organisation developing the software.