Академический Документы
Профессиональный Документы
Культура Документы
Ulhas M. Samant
Computer Support for Successful Project Management: Using MS Project
2016 with Information Technology Projects
10 9 8 7 6 5 4 3 2 1
Keywords
agile, information technology, Microsoft Office Project, MS Project,
Office Project, PMBOK, PMI, Project 2016, project management,
project professional, scheduling software, software development, software
project management
Contents
Acknowledgments....................................................................................xi
Introduction����������������������������������������������������������������������������������������xiii
Chapter 7 enhancement-start.mpp
web-site-improvement-start.mpp
Chapter 8 bank_app_desn_complete.mpp
Chapter 9 In Dependency folder two files
hw-setup.mpp
Testing-project.mpp
In Files-for-consolidation folder two files
AppDevelopment.mpp
Testing-project.mpp
Chapter 10 AppDevelopment-start.mpp
enhancement-start.mpp
RiskRegister-Software-Project.xls
Chapter 11 Agile-project-management—Start
Appendix D AppDevelopment.xls
Project-Progress-Report.doc
enhancement- complete.mpp
CHAPTER 1
Introduction to Information
Technology Project
Management
Objectives
1. Understand about the Software Process Model
2. Understand about the waterfall model and the Agile Development
3. Learn at Macro Level how MS-Project can help project managers
Change or enhancement
Business
plan
Idea Divestment
Product Operations or decommis
–sioning
Requirements
and Design Build Testing
Figure 1.1 Relation between Product Life Cycle and Project Life
Cycle
INFORMATION TECHNOLOGY PROJECT MANAGEMENT 3
Requirements engineering
System design
Software design
Software programming
System validation
The system is delivered to the customer or the end user and will be
used the first time by him. Not only the customers (or the end users) will
check if the requirements were implemented as expected, but they will
also validate if the correct requirements have been set up in the beginning.
In case there are changes necessary, it has to be fixed to make the system
usable or to make it comply with the customer wishes. In most of the
“Waterfall Model” descriptions, this phase is extended to a never-ending
phase of “Operations and Maintenance.” All the problems which were
not captured during the previous phases will be solved in this last phase.
The Waterfall Model has several weaknesses. The prominent ones are:
Agile Development
Agile Project Management is a method of delivering projects in a highly
flexible and interactive manner. It is derived from Agile Software Devel-
opment standards. It is a variant of iterative life cycle where deliverables
are submitted in stages in weeks as shown in Figure 1.3. There are several
variants in Agile, including Scrum and Extreme Programming.
Given as follows are four distinct items of Agile Manifesto which need
to be addressed by the methodology:
6 COMPUTER SUPPORT FOR SUCCESSFUL PROJECT MANAGEMENT
Planning
Requirement
Testing
analysis
Planning Iteration 3
(2–3 months)
Requirement
Testing Construction Design
analysis
Iteration 2
(2–3 months)
Requirement
Testing
Analysis
Iteration 1
(2–3 months)
Construction Design
many believe that it doesn’t scale well, waterfall methodology is still used
for many large software projects.
Project information
Professional
Project Owner/ clientt Executive Contractor
planner / cost
manager
accountant
g
in
st
d
ca
management management
an
re
Fo
n
tio
ica
un
Project
m
m
Accountability Standards
management management