Project Planning and Management
Consider the following scenario:
You are part of a software team which has three to four developers. This team has a contract with a larger software company, which has asked your team to design a complex software component that will work within a larger software application the firm is creating.
One of the key challenges in this project is its volatility. As software requirements tend to change, developers may leave your team or the company's group, and new programmers may be added during the software development. In addition, the company will need to integrate your component within their own very complex system.
Write a 3- to 5-page paper in Microsoft Word document covering the following points:
- There are multiple SDLC methodologies for any software project. List and explain at least three of these approaches along with their respective advantages and disadvantages.
- Which SDLC methodology will you use to develop this project? Why? Justify why you would use this approach versus any other approach.
- Which are the key risk areas for the project? Illustrate.
- How will you plan to manage, mitigate, and remove identified risk areas as part of your project plan?
- There are multiple approaches to estimate the cost of any software project. List and explain at least two of these approaches? Explain the advantages and disadvantages of each approach.
- Which approach will you use to estimate the overall cost of the project? Why? Justify your choice. Why do you think that other approaches will be less appropriate?
In addition to the above, create a complete Microsoft Project file for this project including tasks, sub tasks, resources, and dependency.
Support your responses with examples.
Cite any sources in APA format.
- Name your document SU_ITS3100_W5_A2_LastName_FirstInitial.doc.
- Submit your document to the Submissions Areqa by the due date assigned.
Explanation & Answer
Running head: PROJECT 5
Project planning and management
The Software Development Life Cycle (SDLC) offers systematic processes for creating and
providing software application from the inceptions to the completions (Leau, et al. 2012). There
are various Software Development Life Cycle (SDLC) methodologies for any software projects.
The Waterfall Model
The waterfall is the most straightforward and oldest of Structured Software Development Life
Cycle (SDLC) methodologies. The model has strict phases or stages (Ruparelia, 2010). Every
stage or phase should be finished first before proceeding to the next stage. In the Waterfall
Model, there are no retreating ones a stage is passed. Every stage depends on the details from the
previous phase and has its own project plans.
The Waterfall model is simple to manage and easy to comprehend. Nevertheless, because each
stage should be fully signed off and reviewed before the next step can start; the model is often
prone to delays (Leau, et al. 2012). Problems also cannot be fixed until one gets to the
maintenance phase because there is little room for adjustments immediately a phase is finished.
Waterfall works best when the project has fixed timeline or schedule, flexibilities are not needed,
and requirements are known.
The major water model disadvantage is that all needs require to be known before the start of the
development of the project (Ruparelia, 2010). Thus, when a requirement is missing or wrong,
until the late life cycle stages, it won’t beco...