Val Charry

IS 4600: SPM
May 17, 2015
Assignment 1
1. Create Weebly portfolio site.
Link: http://valcharry.weebly.com/
2. What is the general Software Project Management Lifecycle? What are its phases and
what is generally done in each phase?
The general management lifecycle for a software project is comprised of the following
phases:
- Initiation
- Planning
- Execution
- Monitoring and Control
- Closure
During the Initiation phase, the authorization for the new project is obtained, the
initial scope of the project is defined, and the initial financial resources are committed.
This phase defines what the project is going to do, what its business case is, who wants
the project, how it will be funded, who will manage the work, and who will perform the
work. Within this phase, a Project Manager is usually assigned as well. Outputs are a
project charter, feasibility study, and stakeholder-related document.
The Planning phase is used to establish the total scope of the effort, provide more
definition and refine the objectives, and to develop the course of action needed to get
those objectives. This phase provides the decisions on how detailed to make the plan,
how far ahead to plan, how to involve stakeholders in the planning, how to keep the
planning process streamlined, and how to manage/audit the data that is being fed back
into the planning process. It also helps define how often/when to re-plan, how to
administer the changes to the plan, and how to minimize the effect of changes on work
that is currently in progress. Outputs are a project management plan, a WBS, schedule,
budget, and other subordinate plans.
The Execution phase involves the coordination of people and resources as well as the
integration and performance of the activities of the project in accordance with the
project management plan. It includes establishing and managing the project team,
monitoring the teams performance, directing and managing the project execution,
distribution of information, and performing quality assurance activities. Outputs are risk
management responses and corrective/preventative actions, deliverables and work
performance information, change orders, negotiations for proper staffing, motivation
building and mentoring, conflict resolution, contracts that are put into place, and
organizational process assets are updated as the execution phase occurs.

During the Monitoring and Controlling phase, project progress is tracked, reviewed,
and regulated. This includes status reporting, progress measurement, and forecasting,
reports on scope, scheduling, costs, resources, quality, and risks, and controlling of the
project and project document changes. This phase also implements risk treatment plans
and actions and records the quality control results. Outputs are progress/status reports,
plan updates, risks registers, change requests, and work products/deliverables.
Lastly, the Closing phase involves the activities needed to terminate the project or
project phase, the transfer of the completed project to others, or to close a cancelled
project. This includes approval to close, releasing of people and resources, reports on
team performance and lessons learned, updating/finalizing documents, records, and
results, finalizing procurements, quality assurance tests, and storing/archiving
information. Outputs are certificates of completion/closeout reports, staff work
assignments, resource calendars, plan updates, and final product/deliverables.
3. Why do modern software project generally fail? Identify at least five common failures.
Which of these can be mitigated through a better PMLC? Be sure to look at the most
recent Standish Group CHAOS study.
Common failures for software projects include lack of user participation, insufficient
time spent gathering and understanding requirements, poor project
planning/estimating, inadequate project management methodology, use of too many
new technologies, and incompetent team members. Both lack of user participation and
insufficient time spent gathering and understanding requirements can be mitigated
through an iterative or adaptive PMLC because it encourages regular communication
with the client to provide them with what they want. Inadequate project management
methodology can be mitigated through the use of a more iterative PMLC because it
encourages changes based on continuous feedback as the project develops. Use of too
many new technologies can be mitigated through the use of an incremental PMLC
because it releases solutions to goals in parts and encourages scope change requests,
allowing more control over the new technologies being implemented. Lastly, poor
project planning/estimating can be mitigated through an Agile Project Management
approach because it encourages a high level of communication between client and
project team, as well as within the project team itself, to provide continuous estimates,
designs, and objectives.
4. Which types of contracts are commonly used to develop software products? Compare
and contrast the advantages and disadvantages of each contract type and choose the
one that would be most appropriate for the development of a new iOS app that can
be used by sales representatives to enter and track customer orders for a toy
manufacturer. What type of payment schedule would you use? Should there be any
incentives? If so, define them.
- Fixed-price contract: provide goods or services to the project at an agreed-on
price; used on projects where the scope of the work is very clear and not
likely to change; risks are the costs associated if the project changes

Time and materials contract: hourly rate for labor, plus cost of materials, plus
a percentage of the total costs; used on projects for work that is smaller in
scope and has uncertainty or risk; project assumes the risk rather than the
contractor
Retainer: specific amount to be paid over a period of time; risk if the amount
of work goes over period of time, more hours must be scheduled and pay
renegotiated
Cost Plus: includes direct labor and indirect cost; emphasizes contractors
performance and quality; client is willing to pay more for higher performance
and better quality if applicable

I believe that a fixed-price contract would be the most ideal. Since the scope of the
project is fairly clear and it doesnt seem likely to change, this kind of contract would fit
best.
5. Identify at least 5 risks for the project from Question (4). Catalog the risks and identify
a probability, impact, and then calculate the risk score. Rank the risks. Identify how
you would manage each risk (mitigate, avoid, transfer, accept).
Risk
Probability Impact Score
Manage
Cannot find a solution
10%
7
70
Accept
Client wants to add more
10%
8
80
Mitigate Re-plan
features
Mitigate Reduce
Went over budget/schedule
10%
6
60
scope
App not compatible with
Mitigate Plan
20%
10
200
manufacturer infrastructure
development
Incompetent Developers
10%
4
40
Avoid