INTRODUCTION TO SPM

Ms. Sharmistha Roy Assistant Professor, School of Computer Engineering, KIIT University

Introduction
What is SPM? art and science of planning and leading software projects. Is it really different from ordinary project management? NO.. A software project must also satisfy real needs. To do this we must identify the projects stakeholders and their objectives.

What is the AIM? To met their objectives is the aim of project management.

Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

Why is SPM Important?

The first and foremost important reason is money. In UK, during the financial year 2002-2003, the Central Govt. spend more on contracts for ICT projects (about 2.3 billion). Unfortunately, among 13,522 projects that were analysed by Standish Group, only a third of projects were successful. (82% of projects were late and 43% exceeded their budget). The reasons for those project shortcomings if often the management of projects. Also, National Audit Office in UK identified that lack of skills and proven approach to project management and risk management are the factors causing project failure.
Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

What is a Project?
Planned activity. A specific plan or design. Routine maintenance dont require so much planning Difference between Job & Project Jobs: repetition of very well-defined and well understood tasks with very little uncertainty Exploration: e.g. finding a cure for cancer: the outcome is very uncertain Project is in the middle!!
Routine
Uncertainty of outcome

Jobs

Projects

Exploration
Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

What is a Project?
The following characteristics will make a task project-like: Non-routine Planned Aiming at a specific target Work carried out for a customer Involving several specialisms Temporary work group is made to carry out the task Made up of several different phases Constrained by time and resources Large and/or complex

Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

Are Software Projects really different from other Projects? Not really! but
Invisibility Complexity Conformity Flexibility

make software more problematic to build than other engineered artefacts

Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

Activities covered by SPM

Feasibility Study: Is project technically feasible and worthwhile from a business point of view? Planning: Only done if project is feasible Project execution: Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT It contains: design & implementation of sub-phases.

The ISO 12207 software development life cycle

Requirements Design

System

Requirement analysis Architecture design Requirement analysis Architecture design Requirement analysis

Process Implementation

Software

Detailed design Code and test Integration Qualification test

Code and test

System

Integration Qualification test

Installation acceptance support

Software

Installation Acceptance support

ISO 12207 Software Development Life Cycle

Requirement Analysis: Requirements elicitation: what does the client need? Analysis: converting customer-facing requirements into equivalents that developers can understand Requirements will cover Functions Quality Resource constraints i.e. costs

Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

ISO 12207 Software Development Life Cycle

Architecture design: Based on system requirements Defines components of system: hardware, software, organizational Software requirements will come out of this Detailed design: Design of each software components in detail separately.

Code and test: Of individual components

Integration: Putting the components together

Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

ISO 12207 Software Development Life Cycle

Qualification testing: Testing the system (not just the software) Installation: The process of making the new system operational Includes setting up standing data, setting system parameters, installing on operational hardware platforms, user training etc. Acceptance support: Including maintenance and enhancement

Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

Plans, Methods and Methodologies

Plan: some idea of a method to carry out the work.
For e.g. if you were asked to test some software, about which you know nothing. Requirement Analysis. Devise and write test cases. Create test scripts. Compare the actual results and the expected results and identify discrepancies. Converts a plan into real life activity. Its start and end dates. Who will carry it out. What tools and materials will be needed.

Methods: relates to a type of activity in general.

Methodologies:
Groups of methods or techniques
Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

Why Categorization?
Different technical products to be created. Compulsory versus Voluntary users. Information systems versus Embeded systems.

Outsourced projects.
Objective-driven development

Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

Project Success and Failure

When a project will success? Only when the business objectives is fulfilled. Project Objectives versus Business Objectives: Project objectives: the agreed functionality on time within budget. Business objectives: value of benefits exceeds the cost. A project can be success on delivery but then be a business failure!!
Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

What is Management?
This involves the following activities: Planning deciding what is to be done Organizing making arrangements Staffing selecting the right people for the job Directing giving instructions Monitoring checking on progress Controlling taking action to remedy hold-ups Innovating coming up with solutions when problems emerge Representing liaising with clients, users, developers and other stakeholders

Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

Management Control

Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

Management Control
Data the raw details e.g. 6,000 documents processed at location X Information the data is processed to produce something that is meaningful and useful e.g. productivity is 100 documents a day

Comparison with objectives/goals e.g. we will not meet target of processing all documents by 31st March

Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

Management Control
Modelling working out the probable outcomes of various decisions e.g. if we employ two more staff at location X how quickly can we get the documents processed? Implementation carrying out the remedial actions that have been decided upon

Ms. Sharmistha Roy, Assistant Professor, SCE , KIIT

THANKYOU......