RETAIL PARTNERS ROUND P 61,850 YEN 81 1,680 YEN 1,680 YEN ...
CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.
-
Upload
leonard-warner -
Category
Documents
-
view
220 -
download
0
Transcript of CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.
![Page 1: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/1.jpg)
CHAPTER 11
SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT
Modified by Prof. V. Yen
![Page 2: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/2.jpg)
11.1 Importance of SOFTWARE
Software that is built correctly can transform as the organization and its business transforms
Software that effectively meets employee needs will help an organization become more productive and enhance decision making
Software that does not meet employee needs may have a damaging effect on productivity and can even cause a business to fail
![Page 3: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/3.jpg)
THE SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)Systems
development life cycle (SDLC) – the overall process for developing information systems from planning and analysis through implementation and maintenance
![Page 4: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/4.jpg)
THE SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)
1. Planning phase – involves establishing a high-level plan of the intended project (problem) and determining project goals
1. Analysis phase – involves analyzing end-user business requirements and refining project goals into defined functions and operations of the intended system
• Business requirement – detailed set of business requests that the system must meet in order to be successful
![Page 5: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/5.jpg)
THE SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC))
1. Design phase – involves describing the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other documentation
1. Development phase – involves taking all of the detailed design documents from the design phase, such as coding and transforming them into the actual system
![Page 6: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/6.jpg)
THE SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)1. Testing phase – involves bringing all
the project pieces together into a special testing environment to test for errors, bugs, and interoperability and verify that the system meets all of the business requirements defined in the analysis phase
1. Implementation phase – involves placing the system into production so users can begin to perform actual business operations with the system
![Page 7: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/7.jpg)
THE SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)1. Maintenance phase – involves performing
changes, corrections, additions, and upgrades to ensure the system continues to meet the business goals
![Page 8: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/8.jpg)
SOFTWARE DEVELOPMENT METHODOLOGIES
There are a number of different software development methodologies including:
Agile Waterfall Rapid application development (RAD) Rational unified process (RUP)
![Page 9: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/9.jpg)
Waterfall Methodology
This is an activity-based process in which each phase in the SDLC is performed sequentially from planning through implementation and maintenance
![Page 10: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/10.jpg)
Agile Methodology
aims for customer satisfaction through early and continuous delivery of components developed by an iterative process
An agile project sets a minimum number of requirements and turns them into a deliverable product
Iterative development – consists of a series of tiny projects
![Page 11: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/11.jpg)
Rapid Application Development Methodology (RAD)
emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process
The prototype is an essential part of the analysis phase when using a RAD methodology
Prototype – a smaller-scale representation or working model of the users’ requirements or a proposed design for an information system
![Page 12: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/12.jpg)
Rapid Application Development Methodology (RAD)
Fundamentals of RADFocus initially on creating a prototype that
looks and acts like the desired systemActively involve system users in the analysis,
design, and development phasesAccelerate collecting the business
requirements through an interactive and iterative construction approach
![Page 13: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/13.jpg)
Rational Unified Process (RUP) Methodology provides a framework for breaking down the
development of software into four gatesGate One: InceptionGate Two: ElaborationGate Three: ConstructionGate Four: Transition
![Page 14: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/14.jpg)
Rational Unified Process (RUP)
![Page 15: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/15.jpg)
Implementing Agile Methodologies
The Agile Alliance ManifestoEarly and continuous delivery of valuable
software will satisfy the customerChanging requirements are welcomeBusiness people and developers work togetherProjects need motivated individualsUse self-organizing teamsReflect on how to become more effective
![Page 16: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/16.jpg)
DEVELOPING SUCCESSFUL SOFTWARE
Primary principles for successful agile software development include:
Slash the budget If it doesn’t work, kill it Keep requirements to a minimum Test and deliver frequently Assign non-IT executives to software projects
![Page 17: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/17.jpg)
11.2 MANAGING SOFTWARE DEVELOPMENT PROJECTS
Analysts predict investment in IT projects worldwide through 2010 will be over $1 trillion
70 percent will be lost due to failed projects
The consequences of failed projects include:Damaged brandLost goodwillDissolution of partnershipsLost investment opportunitiesLow morale
![Page 18: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/18.jpg)
The Triple Constraint
Project management interdependent variables
![Page 19: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/19.jpg)
PROJECT MANAGEMENT FUNDAMENTALS
Project – temporary endeavor undertaken to create a unique product, service, or result
Project management – the application of knowledge, skills, tools, and techniques to project activities to meet project requirements
![Page 20: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/20.jpg)
PROJECT MANAGEMENT FUNDAMENTALS
The Project Management Institute (PMI) develops procedures and concepts necessary to support the profession of project management (www.pmi.org) and has three areas of focus:
1. The distinguishing characteristics of a practicing professional (ethics)
2. The content and structure of the profession’s body of knowledge (standards)
3. Recognition of professional attainment (accreditation)
![Page 21: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/21.jpg)
PROJECT MANAGEMENT FUNDAMENTALS Project deliverable – any measurable,
tangible, verifiable outcome, result, or item that is produced to complete a project
Project milestone – represents key dates when a certain group of activities must be performed
Project manager – an individual who is an expert in project planning and management
Project management office (PMO) – an internal department that oversees all organizational projects
![Page 22: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/22.jpg)
PROJECT MANAGEMENT Activities
Project management role
![Page 23: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/23.jpg)
CHOOSING STRATEGIC PROJECTS
Project stakeholders - individuals and organizations actively involved in the project or whose interests might be affected as a result of project execution or project completion
Executive sponsor - the person or group who provides the financial resources for the project
![Page 24: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/24.jpg)
CHOOSING STRATEGIC PROJECTS
Three common techniques for selecting projects
1. Focus on organizational goals2. Categorize projects3. Perform a financial analysis
![Page 25: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/25.jpg)
UNDERSTANDING PROJECT PLANNING
After selecting strategic projects and identifying a project manager the next critical component is the project plan
Building a project plan involves two key components:Project charterProject plan
![Page 26: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/26.jpg)
Project Charter
a document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities and includes:Project scopeProject objectivesProject constraintsProjects assumptions
![Page 27: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/27.jpg)
A Guide to Project Charter Development
SMART criteria are useful reminders on how to ensure that the project has created understandable and measurable objectives
![Page 28: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/28.jpg)
Project Plan a formal, approved document that
manages and controls project execution
A well-defined project plan should be: Easy to understand and read Communicated to all key participants Appropriate to the project’s size, complexity,
and criticality Prepared by the team, rather than by the
individual project manager
![Page 29: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/29.jpg)
Project Plan – Scheduling Tools
Two primary diagrams used in project planning include PERT and Gantt charts
PERT chart – a graphical network model that depicts a project’s tasks and the relationships between those tasks
Dependency Critical path
Gantt chart – a simple bar chart that depicts project tasks against a calendar
![Page 30: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/30.jpg)
A PERT Chart Example
![Page 31: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/31.jpg)
MANAGING PROJECTS
Managing a project includes:Identifying requirementsEstablishing clear and achievable objectives.Balancing the competing demands of quality,
scope, time, and costAdapting the specifications, plans, and
approach to the different concerns and expectations of the various stakeholders
![Page 32: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/32.jpg)
Three Critical Areas in MANAGING PROJECTS
A project manager must focus on managing three primary areas to ensure success:
Managing peopleManaging communicationsManaging change
![Page 33: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/33.jpg)
Change Management
1. Concerns requests for changes in the content of software – this should be carefully managed.
Change management system – a collection of procedures to document a change request and define the steps necessary to consider the change based on the expected impact of the change
Change control board (CCB) – responsible for approving or rejecting all change requests
2. Concerns the effect on employees due to installation of new technology/software
![Page 34: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/34.jpg)
Preparing for Change
Three important guidelines for effectively dealing with change management
1. Institute change management polices2. Anticipate change3. Seek change
![Page 35: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/35.jpg)
OUTSOURCING PROJECTSInsourcing (in-house-development) – a
common approach using the professional expertise within an organization to develop and maintain the organization's information technology systems
Outsourcing – an arrangement by which one organization provides a service or services for another organization that chooses not to perform them in-house; it may be classified into one of:Onshore NearshoreOffshore
![Page 36: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/36.jpg)
Why OUTSOURCING PROJECTS?
Factors driving outsourcing growth include:Core competenciesFinancial savingsRapid growthIndustry changesThe InternetGlobalization
According to PricewaterhouseCoopers “Businesses that outsource are growing faster, larger, and more profitable than those that do not”
![Page 37: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/37.jpg)
Outsourcing BenefitsIncreased quality and efficiency Reduced operating expensesOutsourcing non-core processesReduced exposure to riskEconomies of scale, expertise, and best
practicesAccess to advanced technologiesIncreased flexibility Avoid costly outlay of capital fundsReduced headcount and associated overhead
expenseReduced time to market for products or
services
![Page 38: CHAPTER 11 SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT Modified by Prof. V. Yen.](https://reader036.fdocuments.us/reader036/viewer/2022062309/56649e175503460f94b02544/html5/thumbnails/38.jpg)
Outsourcing Challenges
Outsourcing challenges include Contract length
1. Difficulties in getting out of a contract2. Problems in foreseeing future needs3. Problems in reforming an internal IT department
after the contract is finished Competitive edge Confidentiality Scope definition