10 Questions
What is software project management?
The process of planning and leading software projects
In the 1970s and 1980s, why did the software industry grow quickly?
Recognizing the relatively low cost of software production compared to hardware production
What is the method known as the waterfall model in software project management?
Matching user requirements to delivered products
What has analysis of software project management failures shown as common causes?
Insufficient end-user involvement
What is a key factor contributing to software project management failures?
Poorly managed risks
Match the following with their common cause of software project management failures:
Insufficient end-user involvement = Poor communication among customers, developers, users and project managers Unrealistic or unarticulated project goals = Inaccurate estimates of needed resources Badly defined or incomplete system requirements and specifications = Poor reporting of the project's status Stakeholder politics = Sloppy development practices
Match the following with their primary focus in software project management:
Planning and leading software projects = Implementation, monitoring, and control of software projects Matching user requirements to delivered products = Managing new development efforts Analysis of software project management failures = Maturity of the industry Use of immature technology = Handling the project's complexity
Match the following with their role in the history of software project management:
1970s and 1980s = Rapid growth of the software industry Established project management methods = Applied to manage new development efforts Confusion between user specifications and delivered software = Resulted in slipping project schedules during test runs Waterfall model = Focused on matching user requirements to delivered products
Match the following with their relation to software production in the 1970s and 1980s:
Software industry growth = Recognized relatively low cost compared to hardware production and circuitry Application of established project management methods = To manage new development efforts Slipping project schedules during test runs = Confusion between user specifications and delivered software Common causes of software project management failures = Insufficient end-user involvement
Match the following with their primary focus in software project management methods:
Matching user requirements to delivered products = Waterfall model Analysis of software project management failures = Identifying common causes Use of immature technology = Inability to handle the project's complexity Poorly managed risks = Inaccurate estimates of needed resources
Explore the history of software project management, tracing its development and growth in the 1970s and 1980s as a sub-discipline of project management. Learn about the planning, implementation, monitoring, and control of software projects.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
