Software Project Management Essay by capital writers

Software Project Management
A discussion of how bad project requirements lead to software failures.
# 29101 | 2,653 words | 4 sources | MLA | 2002 | US
Published on Jul 15, 2003 in Business (Management) , Computer and Technology (Software)

$19.95 Buy and instantly download this paper now


This paper examines how understanding the importance of good requirements and managing them well can be the biggest factor in keeping the cost low and improving the success rate of software projects. It looks at how good requirements start with an active project leader who can handle changes, customers who understand their role in the process and stay involved till the very end and developers understand the customer's business needs. It also shows how an integrated team-based approach from both customers and developers will result in good software and a successful software project.

Stakeholders Conflicts
Vague Requirements
Skills that do not Match the Project
What Managers Perceive
Risks Associated with Inaccurate Estimating and Schedule Planning
Risks Associated With External Schedule Pressures Which Damage Quality
Requirements Management Step-by-Step

From the Paper:

"In the past, a certain rate of failures was acceptable but with the current economic conditions granted better budgets, developers are doing a better job of managing both the software requirements and the software projects. In the software development team, the project leader is given the task of collecting the information that is essential for the team to understand the requirements of the project. The information is collected through various methods, such as, interview, surveys, and questionnaires. The people taken into consideration while collecting information are the end-user, the paying customer, and indirect users of the system, management, developers, system architects, and quality assurance staff. The information is contained in a document called the requirements document, which contains thesis about the testing, developing and information about the systems acceptance."

Cite this Essay:

APA Format

Software Project Management (2003, July 15) Retrieved July 06, 2022, from

MLA Format

"Software Project Management" 15 July 2003. Web. 06 July. 2022. <>