Sunteți pe pagina 1din 5

Chapter I 5. Has interrelated activities (tasks) 13.

New operating systems, telecommunications,


To Day’s IT Environment 6. Is an instrument of change interfaces
A Competitive Advantage comes only with superior IT The Project Manager is the leader of a team performing 14. New technology in general
Server Technology to replace Mainframe a project. The project manager and his team must 15. Measurement of return on investment (ROI) and
1. Better identify the stakeholders, determine their needs, and other business metrics is difficult
2. Cheaper manage and influence those needs to ensure a succesful 16. There are often unrealistic goals and pressures
3. Faster project. placed upon project managers and project teams to
The Roles of Project Manager deliver software products better – cheaper- faster.
1. Identifying the requirement and risks 17. To day, IT project often involve many outside
2. Making plans and organizing the effort parties as consultants and vendors
3. Qualifying and possibly selecting project team, 18. To day, IT projects often involve offshore resources.
vendors, and their participants The Three Most Valuable Cerfication in IT
4. Communication among team, management and 1. PMI Project Management Professional (PMP) : 15%
stakeholders 2. GIAC Certified Intrussion Analyst : 12%
5. Assessing the probability of occurence of problems 3. Microsoft Certified Trainer : 12%
6. Developing solutions to problems (both in advance
and on the spot )
7. Ensuring that progress occurs according to the plan
8. Deliverable Management
9. Running Meetings
10. Acquiring Resources for The Project
11. Influencing the Organization
12. Leading and Team Building
13. Negotiation ( External and Internal ) IT Critical Success Factors
1. User Involvement
Three Challenges to Software Engineering Project 2. Executive Management Support
1. The Heterogeneity Challenge : Flexibility to operate 3. Clear Business Objectives
on and integrate wtih multiple hardware and 4. Experienced Project Manager
software plattforms from legacy mainframe 5. Minimal Scope and Requirement
environments to the landscape of the global web. 6. Iterative and Agile Process
2. The Delivery Challenge : Ability to develop and 7. Skilled Personnel
integrate IT systems rapidly in response to rapidly 8. Formal Methodology
changing and evolving global business needs. 9. Financial Management
3. The Trust Challenge : Being able to create vital ( 10. Standar Tools &Infrastructure
Creating a Number of Stragies Major IT Success Factors
mission and/or life critical) software that is
1. Instant Value Alignment : Understanding the 1. Ability to Perform
Major Differences and Difficulties of IT PM trustworthy in terms of both security and quality.
customer so well that the customer’s need are 2. Commitement to Perform
1. The major cost is labor with high degrees of The Possible Misuse of IT
anticipated. 3. Methodology
specializations 1. Price for computational resources has dropped so
2. Instant Learning : building learning directly into each 4. Verification
2. There is a large difference in productivity rates of low that even the smallest of organization and
employees work process and /or schedule. 5. Technology
the human resources even in sam job category countries can obtain massive power
3. Instant Involvement : Using IT to communicate all 6. Project Management
3. There are multiple quality dimensions and criteria 2. Advances in data storage technology mean that
needed information to vendors, employees and so Satisfaction Criteria
4. Cost and time estimation is more complex huge amounts of data can be stored cheaply.
forth. 1. Business Satisfaction
5. There are multiple architectures, methodologies, 3. Advances in data mining techniques mean that
4. Instant Adaptation : Creating an environment 2. Validation
tools, et cetera, and these are constantly changing huge amounts of data can be analyzed in many
enabling all teams to act instantly and to make timely 3. Workflow and Content
6. Projects have a high degrees complexity ways.
decisions. 4. Standards
7. Project may effect the entire organization or 4. Advances in data networking mean that the cost
5. Instant Execution : designing business processes so 5. Maintainability
beyond and time of moving and accessing data has
that they havee as few people involved as possible 6. Adaptability
8. Project have a large amount of changes to becomes very low, and that computers both inside
and reduce cycle times so that these processes 7. Trust and Security
requirement and outside of an organization are increasingly
appear to execute instantly.
9. Project usually have a high degree of significant connected.
Characteristics of Project Definition
risks, including. Chapter II
1. Temporary endeavor with a beginning and an end
10. New Features Critical Success Factors For IT Projects
2. Often broken into subprojects ( or phases )
11. New algorithmes and methods
3. Creates a unique product or service
12. New languages, platforms, architectures and
4. Done for a purpose
supporting tools
1
11. OT - Option Theory
12. \ROI = Return On Investment
13. ROM = Return on Margin
14. SIESTA = Siesta Method
15. SP = Scenario Planning
16. SWOT = Strength, Weaknesses, Opportunities,
Threat
17. TCO = Total Cost of Ownership

Chapter IV
The Project Management Discipline
Project Management Competencies
1. Project Management : Covering the key elements that
differentiate project from general management
2. Organizations and People : Detailing the main
qualitative skills of a project manager.
3. Techniques and Procedures : Details the quantitative
methods
4. General Management : Covers industry specific
concepts.
The Stated Objective Guidance
1. General Managers, to enable them to provide proper
support for project managers and their teams
2. Project Manager, to improve their ability to manage
their projects.
3. Project Support Staff, to help them understand
project management issues and solutions, and
4. Educators and Trainers, to help them understand the
project management environment and the context in
which project management methods are deployed.
Five Process Group Related Project Work
1. Initiation
2. Planning
3. Execution
Chapter III Information
4. Control
Project Selection and Initiations 1. B’s = Bedell’s method
5. Closing
2. BSC = Balanced Scorecard
3. CBA = Cost Benefit Analysis
4. CSF = Critical Success Factors
5. DCF = Discounted Cash Flow
6. DT = Decision Trees
7. IE = Information Economics
8. IM = Investment Mapping
9. IP = Investment Portfolio
10. KU = Kobler Unit Framework

2
4. Finalize project team
5. Do network team diagram Classical Methodology
6. Estimate cost and time, find the critical path 1. Definition
7. Determine overall schedule and budget 2. Specification ( Requirement )
8. Procurement plan 3. Design
9. Quality plan 4. Construction ( Programming and Unit Testing )
10. Identify risks, quantity them, develop risk 5. Testing ( System and Integration )
responses 6. Installation
11. Other plans : Change control plan, 7. Operation and Maintenance
communication plan, management plan
12. Overall project plan
Feasibility, Proposal, Business Plan 13. Project plan approval
Requirement Specification 14. Kick off meeting
Design
Overall Design Key Execution Activities
External ( User interaction ) specification 1. Execute the project plan
Detail Design 2. Compute work packets
“As designed” internal documentation 3. Information distribution
Test plans 4. Quality Assurance
Deployment and integration specification 5. Team development
Implementation 6. Scope verification
Coding 7. Progress meetings SDLC Goals Are To
Unit Testing Key Control Activities 1. Do it right the first time
Nine Knowledge Areas Module and Feature Testing 1. Overall Change Control 2. Meet customers stated requirements
1. Integration Management ( 3 processes ) User Documentation 2. Performance Reporting 3. Have a timely completion
2. Scope Management ( 5 processes ) “As built” internal documentation 3. Scope Control 4. Complete within cost construction
3. Time Management ( 5 processes ) Installation 4. Quality Control 5. Builde system with the necessary quality
4. Cost Management ( 4 processes ) Converision 5. Risk Response Control The Following is What Can, and Often Does, go
5. Quality Management ( 4 processes ) Training 6. Schedule Control Wrong
6. Human Resources Management ( 3 processes Network and Site preparation 7. Cost Control 1. User requirement are misunderstood,
) Hardware install and integration 8. Manage By Exception to The Project Plan incomplete, not fully documented, or not fully
7. Communication Management ( 4 processes ) Integration and Acceptance Testing Key Closing Activities implemented
8. Risk Management ( 4 processes ) Paralel Operation 1. Procurement Audits and Contract 2. Requirement have changed
9. Procurement Management ( 6 processes ) Operation and Maintenance ( O & M ) Close Out 3. Documentation is unusable
2. Product Verification 4. System is difficult to use
3. Formal Acceptance 5. Training is ineffective
4. Lesson Learned Documentation 6. Capacity or performance problems are
5. Update All Project Records present
6. Archive Records 7. Audit and integrity problems are present
7. Release Team 8. Bugs and other quality issues are present
9. Standards are not followed
Chapter V 10. Estimation of workload is poor
The Software Engineering Discipline 11. Project is managed poorly, budget is exceeded
12. Not completed on time
Common Feature of the Maturity Models
Key Initiation Activity 1. Commitment to Perform
1. Project Feasibility ( High – level ROI 2. Ability to Perform
Approximation ) 3. Activities Performed
2. High Level Planning 4. Measurement and Analysis
3. Project Charter Document 5. Veryfying Implementation
( Memo, Letter )
Key Planning Activities
1. Develop scope statement
2. Assemble project team
3. Develop work breakdown structure

3
Key Process Areas ( Basic Project Management ) 6. Software Maintenance 4. Risk Management Plan
1. Requirement Management 7. Software Configuration Management 5. Infrastructure Plan
2. Software Project Planning 8. Software Engineering Process 6. Closeout Plan
3. Software Project Tracking and Oversight 9. Software Engineering Tools and Methods Technical Process Plan
4. Software Subcontract Management 10. Software Quality 1. Process Model
5. Software Quality Assurance 2. Methods, Tools, Techniques
6. Software Configuration Management Chapter VI 3. Infrastructure Plan
Project Overall Planning 4. Product Acceptance Plan
Supporting Process Plan
The Project Charter Contains 1. Configuration Management Plan
1. Project Title and Description 2. Verification and Validation Plan
Management Would Traditionally Review 2. Project Manager assigned and his or her authority 3. Documentation Plan
1. Defined Output ( Stages Deliverables ) level set ( i.e. Authority to set budget, schedule, 4. Quality Assurance Plan
2. Completion status of Activities staffing, procurement ). 5. Review and Audits ; Problem Resolution Plan
3. Actual Costs to Date 3. Goals and Objective ( What the project is to 6. Subcontractor Management Plan; Process
4. Estimated Cost at Completion accomplish ). Improvement Plan
5. Estimated Time to Complete 4. Product ( or service ) descriptions Additional Plans
6. Updated Risk Analysis ( i.e.. The need for more or less 5. Applicable standards Scope Management
reserves ) 6. Assumption and constraints. 1. Scope Initiation
2. Scope Planning
3. Scope Definition
4. Scope Verification
5. Scope Change Control

Key Process Areas ( Organizational Process


Standardization )
1. Organization Process Focus
Joint Application Design (JAD) 2. Organization Process Definition
1. Have Management Support 3. Training Program
2. Use Experienced Fasilitators 4. Integrated Software Management
3. Get the Right People to Participate and Set Their Roles 5. Software Product Engineering Deliverable Definition Document
4. Set Clear Session Objective and Deliverables 6. Intergroup Coordination 1. Requirement Document
5. Have a Detailed Agenda and Stick With it 7. Peer Reviews 2. Overall Design Document
6. Product Deliverables Shortly After the Session Key Process Areas ( Quantitative Process Analysis - 3. Paper Prototype (story boards )
The Rational Unified Process (RUP) have 4 Phases Metrics ) 4. Detail Design Document
1. Inception : Understanding the need, understanding 1. Quantitative Process Management 5. Product Prototype
the proposed system to address the need, making the 2. Software Quality Management 6. User’s Manual ( External Specification Document )
business casse for the proposed solution. Key Process Areas ( Continuous Improvement of Entire 7. Internal Specifications Document
2. Elaboration : Selecting the architecture and Process ) Elements of Management Plan 8. Test Plan and Scripts
developing the project plan 1. Commitment to Perform Overview, References, and Definitions 9. The Product Itself
3. Construction : Design, Coding, Integrating and Testing 2. Ability to Perform Project Organization 10. Installation and Operation Document
4. Transition : Installing the product on the target 3. Activities Performed 1. External Interfaces Requirements Analysis Process
platform (s) and getting the user take ownership of the 4. Measurement and Analysis 2. Internal Interfaces 1. Requirement Discovery
system. 5. Verifying Implementation 3. Roles and Responsibilities 2. Requirement Organization and Documentations
5 Level of Software Maturity Software Engineering Body of Knowledge ( SWEBOK ) Managerial Process Plan 3. Requirement Prioritization and Project Phasing
1. Initial 1. Professional Engineering Economics 1. Start up ( Estimation, Staffing Plan, Resources 4. Requirement Change Management
2. Repeatable 2. Software Requirements Plan, Budget Plan )
3. Defined 3. Software Design 2. Work Plan ( Activities, Schedule, Resources,
4. Managed 4. Software Construction and Implementation Budget )
5. Optimized 5. Software Testing 3. Control Plan ( Requirement, Schedule, Budget,
Quality, Reporting, Metrics )

4
10.Other plans : change control plan, communication 3. Does the work content include more than one type of
plan and management plan activity?
11. Completion of an overall project plan 4. Is there a need to know precisely the timing of
12. Project plan overall activities internal of the work package?
13. Kick off Meeting 5. Is there a need to cost out activities internal to the
work package?
6. Are there any dependencies between the internal
activities of the work package and other work
packages?
7. Are there any significant time breaks in the execution
of the internal activities?
8. Do resource requirements within the work package
change over time?
9. Do the prerequisite differ among the internal
activities?
10. Are there acceptance criteria applicable before the
completion of the entire package?
11. Are there intermediate deliverables that can be used
to generate positive cash flow?
12. Are there specific risks that require focused
attention?

Forms of Requirements Document


1. No Document at all ( ony in the minds of the users and
developers )
2. Simple Checklist
3. Spreadsheet
4. Database
5. Formal Document
6. High Level desgin documents
7. Specialized Software Product
Quality Management Systems Requirements
1. The requirement Processes and the Management of Developing The Cost Plan
These Processes 1. Planning and Staffing : Project plan, Resource
2. The Commitment and Involvement Top Management Commitment
3. The Customer Focus 2. Prototype Design : Requirement & Design
4. The Involvement of People 3. Construct Prototype : Detail Design, Construction
5. Continual Improvement of the processes 4. Test/Evaluate/Prototype : Test plan development,
6. The Factual Approach To Requirement Decision Component Testing, Full Testing, Destructive Testing,
Test Documentation
CHAPTER VII 5. Full Design Specification : External Specifications,
DEVELOPING SCHEDULE AND COST PLAN Internal Specification
6. Documentation : Internal Specifications, Required
DETAIL PROJECT PLANNING External Documents
1. Develop Scope Statement 7. Site preparations : Site design, Site Construction
2. Assemble Project Team 8. Construction : Component construction, Component
3. Develop work breakdown structure Assembly
4. Finalize Project team 9. Test Certification : Test Plan Development, Component
5. Build a Network diagram Testing, Full Testing, Destructive Testing, Test
A Work Packet Decomposition Checklist
6. Estimate cost and time and find the critical path Documentation.
1. Is there a need to improve the accuracy of the cost
7. Determine the overall schedule and budget 10. Finishing : Component finishing, Assembly Finishing
and duration estimates?
8. Plan Procurement 11. Maintenance Training : Maintenance personnel,
2. Is more than one individual responsible for the work?
9. Identify risks, quantity them, and develop response supervisory personnel.