Panning an Information

Technology Project
Loida F. Hermosura, CoE, MSIT
Lesson Outcomes

 At the end of this lesson, the student will be able to:

 Define an IT project.
 Discuss the IT project life cycle
 Identify the Composition of an IT project team
Lesson Outline

 Introduction to IT projects
 Types of IT projects
 IT projects life cycle
 IT project Team Structures
Introduction to IT Projects

 Have you ever looked up at a building that’s being constructed and wondered how every
worker knows exactly what to do in a given day? Have you ever wondered what it takes to
make sure that the materials get to the construction site on time, that the workers focus on the
important task, that the building is constructed on time and on budget? These responsibilities
are the main architects, engineers, building planners, etc.
 A PROJECT can be defined as a complex understanding that has clear goals, has a definite
beginning and end, and can be broken down into smaller, more specific tasks. A group can
have any number of projects, ranging from the noble to the absurd,. Case in point: the
Society’s projects of doing away with Old Cheeseman, a teacher at the school, in a Charles
Dickens’s The Schoolboy’s Story.
 Using the definition above, you can see the project can exist across all industries. The success of
companies in industries like construction, manufacturing, services and utilities depend heavily
on well-managed and well-executed projects.
 Projects in IT

Resources in Building a House Resources in Creating a Website

 Information Technology Materials Hardware
projects, or IT projects, are • Hollow blocks • Development Environment
managed in a way that • Cement • Server
similar to other projects. • Iron bars • Connection/Internet
• Woods Software
The project manager
• GI Sheets • OS
takes care of all the • Pipes • Graphics Software
necessary resources, • Paint • Programming Language
schedules the specific Human Resources • Database Management System
tasks, and estimates the • Foreman (Project Manager) Human Resources
total time it would take to • Architect • IT project Manager
complete the project. • Carpenters • Information architect
• Web designer
• Tester & Maintenance
• Content Writer
IT project Management

 IT project management (ITPM) is the process of managing the plan, organization, and
accountability to achieve information technology goals. Since the reach of IT spans across
most of a business or enterprise, the scope of these projects can be large and complex.
 The magnitude of IT project management often means that it’s more than just applying
knowledge, aligning skills, and using regular tools and techniques to drive a project to
completion. IT project managers deal with the challenges of interdependent integrations,
rapid technology upgrades, and version changes that can occur throughout the project
timeline.
 Role of the IT Project Manager

 Today’s IT project managers (IT PM) must be able to juggle a wide

range of tasks and responsibilities. They must be able to handle
firmware and software integrations, website construction, database
storage and management, and also build complex and
geographically diverse infrastructures and networks, all while
planning for potential security and data risks.
 Throughout their projects, an IT PM is responsible for setting goals,
communicating and motivating team members and stakeholders,
identifying the right resources for each task, researching, managing
change, performing needs assessment, and properly sequencing
tasks.
 Additional responsibilities of the IT project manager include the
following:
 Project planning and overall management
 Promoting and achieving project support
 Ensuring overall capability with existing technology
 Minimizing duplicate work
 Utilizing team member skills
 Controlling costs and maintaining budgets
Challenges Faced by IT Project Managers

 The complexities and interdependencies of large-scale, long-term, diverse IT projects are

among the most challenging issues of IT projects. Here are a few more top challenges
faced by IT project managers:
 Making multiple assumptions when integrating different hardware, networks, and software
to the existing system.
 Unclear expectations from the business, end-users, and stakeholders.
 Rapidly changing technology, leading to necessary mid-project upgrades that can affect
timelines.
 Geographically diverse offices and remote work associated.
What Are The Different Types Of Tech
Projects?

 IT projects may come in different forms and require different approaches but they have
one thing in common, that is they utilize information technology to achieve the objectives
of the project.
THEN AND NOW
 Application today can be use through client-server applications because the computer
networks became available.
 Stand-alone applications are meant to execute certain tasks within a single computer.
WEB DEVELOPMENT

 - Aims to design, create and launch a website.

 - Graphical in nature and use images.
 Examples are: Corporate websites, personal websites and online journals
APPLICATION DEVELOPMENT

 - Aims to create a customized program that addresses a specific need.

 - Used by companies to automate a certain portion of their business.
 Examples: MS Office, Adobe products, online enrollment, computerized grading system,
payroll system, etc.
SYSTEMS DEVELOPMENT

 - It links together a number of applications that when combined may address a broader
objective.
 Examples are: Operating system (OS), Device drivers, utility programs like antivirus
VIDEO DEVELOPMENT

 - Not a traditional IT project but since it uses different tools or programs in the computer
and uses the Internet for distribution it is already recognize as a type of IT project.
 Examples are: Movies, Clips, Animations, etc.
 The IT Project Management Lifecycle

 The ITPM lifecycle includes the five basic phases of project

management, but the main difference for IT project
management is how the project lifecycle is managed.
 The most common ITPM method is the Waterfall methodology,
which involves a predictive linear process. The entire project is
defined before starting, and each phase is initiated and
completed before moving on to the next phase.
 Another lifecycle method is the Iterative method, which uses a
more incremental approach. The iterative or incremental
approach repeats phases, and each iteration completes the
planning, analysis, and design phases with the ability to deliver
on a specific goal at the end of the iteration.
Project Management IT Project Lifecycle

 The Project Framework consists of multiple elements working together to help ensure
successful delivery of projects. These elements are:
 Project Types – help determine the adapt to the needs of different projects
 Project Phases – the project lifecycle broken into specific blocks, each with its own
purpose, deliverables, and gate required to progress
 Project Gates – formal key decision points between each project phase where the
elements of the project are reviewed and must be approved before the project can
progress to the next phase
 Templates – standardized forms or documents that collect and report consistent data
about the project so that it may be effectively tracked through the project lifecycle
The Project Lifecycle

 The IT Project Management lifecycle consists of five phases:

 Identification – capture the business need for the project and the ideal solution
 Initiation – document the project deliverables and resources needed to complete the project
 Planning – develop the project schedule, assign resources, clarify risks
 Delivery – do the project work (execution) and report on progress (monitor and control)
 Closeout – capture lessons learned, document project successes for future use
 Phase One: Identification

 Identification, or phase one of the project lifecycle, includes activities related to the
development of a business case and proposal. This phase often is triggered when a
department, team, or individual identifies a project-worthy need, demand, or opportunity.
During this phase, a sponsor requests and/or receives a business case that includes cursory
information on the purpose and need for the project, a cost estimate, timeframe, and any
associated major risks. The sponsor evaluates the case and determines if the project
should be undertaken. Projects receiving formal sponsorship progress to the second phase
of the lifecycle
 Phase Two: Initiation

 The Initiation Phase is the second phase of the project lifecycle. The phase begins once the
PCW (business case) is approved. During initiation, the project is more fully defined so that it
may be properly resourced and realistically planned in the next phase. The sponsor assigns a
project manager. The project manager proceeds to fully describe the project scope and
prepare the project charter. The major deliverable of the phase is the project charter, which:
 Identifies the stakeholders
 Defines the project timeframe
 Provides the rationale for the project
 Identifies the core project deliverables, assumptions, and potential risks

 The phase concludes when the sponsor signs off on the charter, signaling that the project may
move to the Planning Phase and project manager may begin the detailed planning work.
Phase Three: Planning

 The Planning Phase builds on information captured in the Initiation Phase and is
traditionally considered the most important. Unfortunately, many times project teams
often minimize or overlook planning activities, anxious to begin the development activities
of the Delivery Phase as soon as possible. A well-developed and holistic plan, however,
helps ensure that the project team completes a project successfully, on time, and on cost
with fewer surprises and deviations from the originating charter. The project plan must
consist of the schedule and resources for the project, budget requirements, performance
measures, and clear actions for managing change, risk, and communications. The phase
concludes with a sponsor-approved project plan.
 Phase Four: Delivery

 Delivery consists of two specific sub-phases that occur concurrently. It is when the actual project
deliverables are completed and progress is reported. Specifically, it includes:
 Execution – doing the work identified in the project plan
 Monitoring and Control – keeping the plan and schedule up to date, reporting project progress, issues, etc. and
ensuring the project is on track.
 Execution: With an approved plan, a project can move into the Delivery-Execution (Execution) Phase of
the project lifecycle. This is where "the work gets done"; where the project team completes the tasks
outlined on the project schedule and develops the project deliverable(s). The Execution Phase
concludes with the project deliverable(s) achieved and accepted by the users and the sponsor.
 Monitor and Control: The second portion of the Delivery Phase is Delivery-Monitor and Control. Monitor
and Control consist of the activities needed to track the work. The team delivers status reports, monitors
and reports on issues and risks, creates change requests, and conducts procurement activities. There
are no specific deliverables or templates associated with the Monitor and Control activities; however,
Project Status Reports and Briefings may be requested by the Project Sponsor or other stakeholders
during Delivery.
Phase Five: Closeout

 Projects are temporary in nature and a project team must complete the activities of the
final phase – Closeout – in order to officially complete the project. Conducting the
activities of this phase is vital to continuous improvement efforts and the successful
transition of the project deliverable(s). After achieving acceptance of the deliverable(s),
the project team documents lessons learned and archives project documentation for
future use. The project manager transfers the project deliverable(s) to operations and
support staff or unit, who will maintain it as an operational activity. Finally, and often
overlooked, the project team disbands.
 Types of IT Project Life Cycles

 Throughout IT history, different methodologies in managing the project life cycle have been
presented. Each theory has given birth to various life cycle models, each one attempting to
represent the project in its entirety. It would be very difficult to discuss all of these models. There
are, however key methodologies that have made their mark on how we currently handle IT
projects. Here are some of them.
 The waterfall Model and Systems Development
 Spiral Model
 Software Prototype Model
 Waterfall Model - Design

 Waterfall approach was first SDLC Model to

be used widely in Software Engineering to
ensure success of the project. In "The
Waterfall" approach, the whole process of
software development is divided into
separate phases. In this Waterfall model,
typically, the outcome of one phase acts as
the input for the next phase sequentially.
 The sequential phases in Waterfall model
are −

 Requirement Gathering and analysis − All possible requirements of the system to be developed are captured in this phase
and documented in a requirement specification document.
 System Design − The requirement specifications from first phase are studied in this phase and the system design is
prepared. This system design helps in specifying hardware and system requirements and helps in defining the overall
system architecture.
 Implementation − With inputs from the system design, the system is first developed in small programs called units, which
are integrated in the next phase. Each unit is developed and tested for its functionality, which is referred to as Unit Testing.
 Integration and Testing − All the units developed in the implementation phase are integrated into a system after testing of
each unit. Post integration the entire system is tested for any faults and failures.
 Deployment of system − Once the functional and non-functional testing is done; the product is deployed in the customer
environment or released into the market.
 Maintenance − There are some issues which come up in the client environment. To fix those issues, patches are released.
Also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the
customer environment.
All these phases are cascaded to each other in which progress is seen as flowing steadily downwards (like a waterfall)
through the phases. The next phase is started only after the defined set of goals are achieved for previous phase and it is
signed off, so the name "Waterfall Model". In this model, phases do not overlap.
 Waterfall Model - Application

Every software developed is different and requires a suitable SDLC approach to be followed based
on the internal and external factors. Some situations where the use of Waterfall model is most
appropriate are −
 Requirements are very well documented, clear and fixed.
 Product definition is stable.
 Technology is understood and is not dynamic.
 There are no ambiguous requirements.
 Ample resources with required expertise are available to support the product.
 The project is short.
 Waterfall Model - Advantages

The advantages of waterfall development are that it allows for departmentalization and control. A schedule
can be set with deadlines for each stage of development and a product can proceed through the
development process model phases one by one.
Development moves from concept, through design, implementation, testing, installation, troubleshooting, and
ends up at operation and maintenance. Each phase of development proceeds in strict order.
Some of the major advantages of the Waterfall Model are as follows −
 Simple and easy to understand and use
 Easy to manage due to the rigidity of the model. Each phase has specific deliverables and a review process.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well understood.
 Clearly defined stages.
 Well understood milestones.
 Easy to arrange tasks.
 Process and results are well documented.
 Waterfall Model - Disadvantages

The disadvantage of waterfall development is that it does not allow much reflection or revision. Once an
application is in the testing stage, it is very difficult to go back and change something that was not well-
documented or thought upon in the concept stage.
The major disadvantages of the Waterfall Model are as follows −
 No working software is produced until late during the life cycle.
 High amounts of risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and ongoing projects.
 Not suitable for the projects where requirements are at a moderate to high risk of changing. So, risk and
uncertainty is high with this process model.
 It is difficult to measure progress within stages.
 Cannot accommodate changing requirements.
 Adjusting scope during the life cycle can end a project.
 Integration is done as a "big-bang. at the very end, which doesn't allow identifying any technological or business
bottleneck or challenges early.
 Spiral Model

 The spiral model combines the idea of iterative development with the systematic, controlled aspects
of the waterfall model. This Spiral model is a combination of iterative development process model
and sequential linear development model i.e. the waterfall model with a very high emphasis on risk
analysis. It allows incremental releases of the product or incremental refinement through each
iteration around the spiral.
Spiral Model - Design
 The spiral model has four phases. A software project repeatedly passes through these phases in
iterations called Spirals.
Identification
 This phase starts with gathering the business requirements in the baseline spiral. In the subsequent
spirals as the product matures, identification of system requirements, subsystem requirements and
unit requirements are all done in this phase.
 This phase also includes understanding the system requirements by continuous communication
between the customer and the system analyst. At the end of the spiral, the product is deployed in
the identified market.
Spiral Model

Design
 The Design phase starts with the conceptual design in the baseline spiral and involves
architectural design, logical design of modules, physical product design and the final
design in the subsequent spirals.
Construct or Build
 The Construct phase refers to production of the actual software product at every spiral. In
the baseline spiral, when the product is just thought of and the design is being developed
a POC (Proof of Concept) is developed in this phase to get customer feedback.
 Then in the subsequent spirals with higher clarity on requirements and design details a
working model of the software called build is produced with a version number. These
builds are sent to the customer for feedback.
 Evaluation and Risk Analysis

 Risk Analysis includes identifying,

estimating and monitoring the
technical feasibility and management
risks, such as schedule slippage and
cost overrun. After testing the build, at
the end of first iteration, the customer
evaluates the software and provides
feedback.
 The following illustration is a
representation of the Spiral Model,
listing the activities in each phase.
 Based on the customer evaluation,
the software development process
enters the next iteration and
subsequently follows the linear
approach to implement the
feedback suggested by the
customer. The process of iterations
along the spiral continues throughout
the life of the software.
 Spiral Model Application

The Spiral Model is widely used in the software industry as it is in sync with the natural development
process of any product, i.e. learning with maturity which involves minimum risk for the customer as well
as the development firms.
The following pointers explain the typical uses of a Spiral Model −
 When there is a budget constraint and risk evaluation is important.
 For medium to high-risk projects.
 Long-term project commitment because of potential changes to economic priorities as the requirements
change with time.
 Customer is not sure of their requirements which is usually the case.
 Requirements are complex and need evaluation to get clarity.
 New product line which should be released in phases to get enough customer feedback.
 Significant changes are expected in the product during the development cycle.
Spiral Model - Pros and Cons

 The advantage of spiral lifecycle model is that it allows elements of the product to be
added in, when they become available or known. This assures that there is no conflict with
previous requirements and design.
 This method is consistent with approaches that have multiple software builds and releases
which allows making an orderly transition to a maintenance activity. Another positive
aspect of this method is that the spiral model forces an early user involvement in the
system development effort.
 On the other side, it takes a very strict management to complete such products and there
is a risk of running the spiral in an indefinite loop. So, the discipline of change and the
extent of taking change requests is very important to develop and deploy the product
successfully.
The advantages of the Spiral SDLC Model are as follows −

 Changing requirements can be accommodated.

 Allows extensive use of prototypes.
 Requirements can be captured more accurately.
 Users see the system early.
 Development can be divided into smaller parts and the risky parts can be developed earlier
which helps in better risk management.
The disadvantages of the Spiral SDLC Model are as follows −

 Management is more complex.

 End of the project may not be known early.
 Not suitable for small or low risk projects and could be expensive for small projects.
 Process is complex
 Spiral may go on indefinitely.
 Large number of intermediate stages requires excessive documentation
Software Prototype Model

 The Software Prototyping refers to building software application prototypes which displays
the functionality of the product under development, but may not actually hold the exact
logic of the original software.
 Software prototyping is becoming very popular as a software development model, as it
enables to understand customer requirements at an early stage of development. It helps
get valuable feedback from the customer and helps software designers and developers
understand about what exactly is expected from the product under development.
What is Software Prototyping?
 Prototype is a working model of software with some limited functionality. The prototype
does not always hold the exact logic used in the actual software application and is an
extra effort to be considered under effort estimation.
 Prototyping is used to allow the users evaluate developer proposals and try them out
before implementation. It also helps understand the requirements which are user specific
and may not have been considered by the developer during product design.
 Following is a stepwise approach explained to design a software prototype.
 Basic Requirement Identification
 Developing the initial Prototype
 Review of the Prototype
 Revise and Enhance the Prototype
 Basic Requirement Identification- This step involves understanding the very basics product requirements especially in
terms of user interface. The more intricate details of the internal design and external aspects like performance and
security can be ignored at this stage.
 Developing the initial Prototype - The initial Prototype is developed in this stage, where the very basic requirements are
showcased and user interfaces are provided. These features may not exactly work in the same manner internally in the
actual software developed. While, the workarounds are used to give the same look and feel to the customer in the
prototype developed.
 Review of the Prototype - The prototype developed is then presented to the customer and the other important
stakeholders in the project. The feedback is collected in an organized manner and used for further enhancements in the
product under development.
 Revise and Enhance the Prototype - The feedback and the review comments are discussed during this stage and some
negotiations happen with the customer based on factors like – time and budget constraints and technical feasibility of
the actual implementation. The changes accepted are again incorporated in the new Prototype developed and the
cycle repeats until the customer expectations are met.
Prototypes can have horizontal or vertical dimensions. A Horizontal prototype displays the user interface for the product and
gives a broader view of the entire system, without concentrating on internal functions. A Vertical prototype on the other side
is a detailed elaboration of a specific function or a sub system in the product.
The purpose of both horizontal and vertical prototype is different. Horizontal prototypes are used to get more information on
the user interface level and the business requirements. It can even be presented in the sales demos to get business in the
market. Vertical prototypes are technical in nature and are used to get details of the exact functioning of the sub systems.
For example, database requirements, interaction and data processing loads in a given sub system.
 Software Prototyping - Types

 Throwaway/Rapid Prototyping - Throwaway prototyping is also called as rapid or close ended prototyping. This
type of prototyping uses very little efforts with minimum requirement analysis to build a prototype. Once the
actual requirements are understood, the prototype is discarded and the actual system is developed with a
much clear understanding of user requirements.
 Evolutionary Prototyping - Evolutionary prototyping also called as breadboard prototyping is based on building
actual functional prototypes with minimal functionality in the beginning. The prototype developed forms the
heart of the future prototypes on top of which the entire system is built. By using evolutionary prototyping, the
well-understood requirements are included in the prototype and the requirements are added as and when
they are understood.
 Incremental Prototyping - Incremental prototyping refers to building multiple functional prototypes of the
various sub-systems and then integrating all the available prototypes to form a complete system.
 Extreme Prototyping - Extreme prototyping is used in the web development domain. It consists of three
sequential phases. First, a basic prototype with all the existing pages is presented in the HTML format. Then the
data processing is simulated using a prototype services layer. Finally, the services are implemented and
integrated to the final prototype. This process is called Extreme Prototyping used to draw attention to the
second phase of the process, where a fully functional UI is developed with very little regard to the actual
services.
Software Prototyping - Application

 Software Prototyping is most useful in development of systems having high level of user
interactions such as online systems. Systems which need users to fill out forms or go through
various screens before data is processed can use prototyping very effectively to give the
exact look and feel even before the actual software is developed.
 Software that involves too much of data processing and most of the functionality is
internal with very little user interface does not usually benefit from prototyping. Prototype
development could be an extra overhead in such projects and may need lot of extra
efforts.
 Software Prototyping - Pros and Cons

 Software prototyping is used in typical cases and the decision should be taken very
carefully so that the efforts spent in building the prototype add considerable value to the
final software developed. The model has its own pros and cons discussed as follows.
The advantages of the Prototyping Model
are as follows −

 Increased user involvement in the product even before its implementation.

 Since a working model of the system is displayed, the users get a better understanding of
the system being developed.
 Reduces time and cost as the defects can be detected much earlier.
 Quicker user feedback is available leading to better solutions.
 Missing functionality can be identified easily.
 Confusing or difficult functions can be identified.
The Disadvantages of the Prototyping
Model are as follows −

 Risk of insufficient requirement analysis owing to too much dependency on the prototype.
 Users may get confused in the prototypes and actual systems.
 Practically, this methodology may increase the complexity of the system as scope of the
system may expand beyond original plans.
 Developers may try to reuse the existing prototypes to build the actual system, even when
it is not technically feasible.
 The effort invested in building prototypes may be too much if it is not monitored properly.