Copyright Course Technology 2001 1 Chapter 15: Controlling.

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

Targets for the individual and the organisation By Rachel, Claire, Kirsten and Natalie.
Project Management 6e..
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Systems Analysis and Design 9th Edition
Systems Analysis and Design 8 th Edition Chapter 3 Managing Systems Projects.
Copyright Course Technology Chapter 12: Initiating.
Evaluation and Reporting ENTC 4060 Project Scheduling.
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
Project Scope Management
Feasibility and Cost/Benefit Analysis. Cost considerations u Cost classifications –Tangible / Intangible –Direct / Indirect –Fixed / Variable –Developmental.
Systems Analysis and Design 8th Edition
Chapter 5: Project Scope Management
4. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the elements of project management and the responsibilities of a.
Chapter 3: The Project Management Process Groups
Chapter 5: Project Scope Management
CHAPTER 9: LEARNING OUTCOMES
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 16-1 Accounting Information Systems 9 th Edition Marshall.
Project Scope Management
Week3: The Project Management Process Groups 1 Prof. Ahmed Sameh Professor of Computer Sc. And Information Systems.
Chapter 3: The Project Management Process Groups: A Case Study
Information Technology Project Management, Sixth Edition Note: See the text itself for full citations.
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Financial Area Representative Meeting FAR UTShare PeopleSoft Update October 16,
SA Capstone Requirements and Design Week 10 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.
L545 Systems Analysis & Design Week 4: September 23, 2008.
1 Chapter 1: Introduction to Project Management. 2 Learning Objectives Understand the growing need for better project management, especially for information.
Feasibility and Cost/Benefit Analysis. Cost considerations u Cost classifications –Tangible / Intangible –Direct / Indirect –Fixed / Variable –Developmental.
Copyright Course Technology Chapter 14: Executing.
Copyright Course Technology 1999
Copyright Course Technology 1999
Copyright Course Technology Chapter 16: Closing.
Chapter 3: The Project Management Process Groups: A Case Study
Information Technology Project Management, Sixth Edition Note: See the text itself for full citations.
1 Bonham, chapter 8 Knowledge Management. 2  8.1 Success Levels  8.2 Externally Focused KM  8.3 Internally Focused KM  8.4 PMO-Supported KM
Project Scope Management Process
Recap from last week Understand organizations, including the four frames, organizational structures. Explain why stakeholder management and top management.
Project Management Process Groups
Chapter 5: Project Scope Management Information Technology Project Management.
Copyright Course Technology 1999
1 Copyright Flying Kiwi Productions Inc. An Introduction to Object-Oriented Analysis Objects and UML in plain English. Chapter.
System Thinking and Project Management Process
Chapter 3: The Project Management Process Groups: A Case Study Information Technology Project Management, Fourth Edition.
Copyright 2009  Describe the five project management (PM) process groups, the typical level of activity for each, and the interactions among them  Understand.
Lecture 3 Title: Information Technology Project Methodology By: Mr Hashem Alaidaros MIS 434.
3 1 Project Success Factors u Project management important for success of system development project u 2000 Standish Group Study l Only 28% of system development.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1IT Project Management, Third Edition Chapter 3 Chapter 3: The Project Management Process Groups: A Case Study.
Lecture 2_2 The Project Management Process J. S. Chou, P.E., Ph.D. Assistant Professor.
Copyright Course Technology Chapter 15: Controlling.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 3 Managing the Information Systems Project 3.1.
Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects.
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
Information Technology Project Management, Seventh Edition Note: See the text itself for full citations.
Software Engineering INTRODUCTION TO SOFTWARE DEVELOPMENT.
Team-Based Development ISYS321 Managing the Information Systems Project.
Chapter 3: The Project Management Process Groups: A Case Study Information Technology Project Management, Fourth Edition Project Execution & Closing Thursday,
IT Project Management, Third Edition Chapter 11 Chapter 1: Introduction to Project Management.
Copyright 2012 John Wiley & Sons, Inc. Part II Project Planning.
The Project Management Process Groups
Project Management PTM721S
Systems Analysis and Design in a Changing World, 4th Edition
Copyright Course Technology 2001
Project Management Process Groups
Copyright Course Technology 2001
Copyright Course Technology 2001
Presentation transcript:

Copyright Course Technology Chapter 15: Controlling

Copyright Course Technology What Is Involved in Controlling Projects? Controlling is the process of –measuring progress towards project objectives –monitoring deviation from the plan –taking corrective action to match progress with the plan Controlling cuts across all of the other phases of the project life cycle and involves seven knowledge areas

Copyright Course Technology Table Controlling Processes and Outputs

Copyright Course Technology Schedule Control Peeter’s philosophy was to avoid schedule changes by determining important milestones and setting realistic completion dates Football analogy: Keep making first downs and you’ll score touchdowns! Peeter sacrificed some functionality in the system to meet schedule dates Everyone knew what key milestone dates were and that Peeter was serious about meeting them

Copyright Course Technology What Went Right? Peeter had gone through project management training when he worked in Canada. One piece of advice he remembered was to focus on meeting the project schedule goals. Date changes tend to cause chaos throughout a project. Therefore, his goal for ResNet was to establish key dates and vary the scope as needed to stay on schedule. To emphasize the importance of schedule, the ResNet team made the theme for the 1996 ResNet kickoff meeting "What About Wendy?" Wendy was the office manager of the last call center scheduled to get ResNet PCs. The theme stressed the importance of meeting schedule dates so that Wendy's group would not be disappointed. The ResNet team displayed a Gantt chart and explained that missing any deadlines would hurt Wendy. This personal touch helped everyone focus on meeting deadlines.

Copyright Course Technology What Went Wrong? The WorldPerks application development and office rollout in Chisholm, Minnesota, provided one of the toughest challenges for the ResNet team. They had underestimated how long it would take to develop the WorldPerks software, plus they ran into technical and personnel problems…Also, the state of Minnesota funded the Chisholm office to develop more jobs in the Minnesota Iron Range…Many of the new employees were also very inexperienced with computers. The ResNet team had to send in people to work with these new employees and help coordinate technical and training problems with the main office in Minneapolis. The project incurred additional costs, and the extra work for this office delayed the start of the Detroit implementation by about three weeks.

Copyright Course Technology The ResNet Team Vs. Management Peeter and Fay wanted to change the sequencing of office installations after the problems in Hibbing Arvid and other team members banded together to convince Peeter and Fay not to change the sequencing because it would cause even more problems With some overtime and additional funds, the Hibbing and Detroit offices were both completed on time

Copyright Course Technology Scope Change Control Everyone worked together to determine the scope of the project The 1996 ResNet kickoff meeting clarified scope and emphasized the shared responsibility in making the project a success Agents requested over 11,000 enhancements to the software. About 38% of them were implemented based on priorities and time and cost constraints

Copyright Course Technology Table Kickoff Meeting Statements About ResNet Purpose and Scope

Copyright Course Technology Quality Control The agents helping to write the code knew what shortcuts people might try, so they built user- friendly, foolproof software The industrial engineers used statistics to create random samples of agents to test the system Two quality control reports were very effective in tracking the quality of the system

Copyright Course Technology Figure New Hire Call Handle Time Learning Curves Call Handle Time (Seconds) Weeks Since Training ResNet Telex

Copyright Course Technology Figure Direct Tickets per 100 Calls - Actual Vs. Predicted

Copyright Course Technology Performance and Status Reporting Reports emphasized –key issues –decisions that needed to be made –numerical progress on the project Important numbers tracked were the number of PCs installed, the average call handle times for sales agents, and the number of calls resulting in direct ticket sales

Copyright Course Technology Figure Sample Weekly Status Report

Copyright Course Technology Managing Resistance to Change ResNet team members did not think of change management in the traditional view of handling change requests The ResNet team focused on managing people’s resistance to change when introducing a new system ResNet included a full-time analyst responsible for change management There was a change management plan and teams at each office Training helped reduce the fear of change

Copyright Course Technology ResNet Videotape Introduction "Recently we began testing a new reservation system call ResNet with agents from several of our offices. At the end of the test, we sat down with these agents and asked them their candid opinion of ResNet. Now we know that change can be difficult. But what we found and what you're about to hear will hopefully show you that this is change for the better. Our vision is that ResNet will improve customer service, increase efficiency and revenue, and ultimately make your job easier. Once again, you will be hearing from your peers¾agents who have used this new system, giving their honest opinion of ResNet" (Crystal Knotek, 1995).