Summary
INF3708 ch1 Summary Notes
- Course
- Institution
- Book
Summary of the whole chapter
[Show more]
Connected book
Book Title:
Author(s):
- Edition:
- ISBN:
- Edition:
More summaries for
-
INF3708 ch4 Summary Notes
-
INF3708 ch5 Summary Notes
-
INF3708 ch6 Summary Notes
4 reviews
By: jakeskoorzen • 6 year ago
By: Riaan1803 • 7 year ago
By: chandreclassens • 7 year ago
By: tshepomogamisi • 8 year ago
Notes are good
Seller
Follow
khemi
Reviews received
Content preview
INF3708 – Software Project ManagementChapter 1
Introduction to software project management
1.2 Why is software project management important?
The lack of skills and proven approach to project management and risk management are the cuases of
failure in software projects.
1.3 What is a project?
A project is a planned activity.
The following characteristics distinguish projects:
non-routine tasks are involved;
planning is required;
specific objectives are to be met or a specified product is to be created;
the project has a predetermined time span;
work is carried out for someone other than yourself;
work involves several specialisms;
people are formed into a temporary work group to carry out the task;
work is carried out in several phases;
the resources that are available for use on the project are constrained;
the project is large or complex.
The more any of these factors apply to a task, the more difficult that task will be. Project size is
particularly important. The project that employs 20 developers is likely to be disproportionately more
difficult than one with only 10 staff because of the need for additional coordination.
1.4 Software projects versus other types of project
Invisibility When a physical artefact such as a bridge is constructed the progress can actually be seen.
With software progress is not immediately visible. Software project management can be seen as the
process of making the invisible visible.
Complexity Per dollar, pound or euro spent, software products contain more complexity than other
engineering artefacts.
Conformity The ‘traditional’ engineer usually works physical systems and materials like cement and
steel. These physical systems have complexity, but are governed by consistent physical laws. Software
developers have to conform to the requirements of human clients.
Flexibility That software is easy to change is seen as a strength. However, where the software system
interface with a physical or organisational system, it is expected to that the software will change ot
accommodate the other components rather than vice versa.
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller khemi. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $2.84. You're not tied to anything after your purchase.
Can Stuvia be trusted?
4.6 stars on Google & Trustpilot (+1000 reviews)
70055 documents were sold in the last 30 days
Founded in 2010, the go-to place to buy study notes for 14 years now