w hen management gets serious about managing software by k. ravikant 12mcmb21 author name :- p.a....

29
WHEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

Upload: willa-horn

Post on 11-Jan-2016

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

WHEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE

By K. Ravikant 12mcmb21

Author Name :- P.A. “TRISHA” JANSMA

Page 2: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

ABSTRACT

In FY 2002, JPL launched a lab-wide software quality improvement effort aimed at addressing the challenges of developing, managing and acquiring software in an engineering and scientific environment.

The areas of emphasis selected were based on the CMMI®model, The SQI Project developed a broad range of products, services, and training to support managers and practitioners throughout the entire software development

life-cycle.This paper describes JPL’s approach to improving howsoftware is managed, developed and acquired. It discussesthe various products, services and training that weredeveloped, describes the deployment approach used.

Page 3: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

CONTENTS

INTRODUCTION

GENERAL APPROACH

DEPLOYMENT PROCESS

INFRASTRUCTURE AND OPERATIONS

COMMUNICATION AND OUTREACH

EDUCATION AND TRAINING

PROJECT SUPPORT

CONCLUSION

Page 4: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

INTRODUCTION

The Jet Propulsion Laboratory (JPL), located in Pasadena, California, R & D center which is operated by the California Institute of Technology under a contract with the NASA.

Part of the U.S. aerospace industry, and is NASA’s lead center for robotic exploration of the solar system.

Performs tasks for a variety of other federal agencies, such as the U.S.

• DOD, • DOT• DOE etc.

Page 5: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

Formed SQI Project in 2002 to establish an on-going operational effort which results in continuous ,measurable improvement of

S/W quality. After some study, the SQI Project identified

several factors that are critical for the successful and timely management and implementation of software-intensive systems.

.

Page 6: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

COMPONENTS OF SQI PROJECT

SQI Project Management

Process and Product Definition Element

Measurement, Estimation and Analysis

Element

Deployment Element

CMMI® Implementation Team

Page 7: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

USE OF CUSTOMER RELATIONSHIP MANAGEMENT:-

Customer Relationship Management(CRM) :-

Develop stronger relationship with Customers.”

Provide Value Services.

Tailoring the communication messages and

approach to Customer specific needs. SQI Project identified five customer segments

shown in table 1..

Page 8: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA
Page 9: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

The SQI Project prioritized their activities based on classes of software and application domains as shown in Table 2

Page 10: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

GENERAL APPROACH :-

The initial focus of their efforts is the basic project management of mission-critical software based on the CMMI® model.

The process areas selected include Software project planning, Software project monitoring and control, Software acquisition management, Software requirements management, Software quality assurance, Software configuration management, Software measurement and analysis, and

software risk management.

Page 11: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

CAPABILITY MATURITY MODEL INTEGRATION(CMMI)

Popular framework for process improvement.

Developed by SEI at Carnegie Mellon Univ.

Evaluation & appraisal model , used to

evaluate “maturity” of an organization’s

processes.

Used to build ,extend & integrate best

practises for S/w.

Page 12: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

PROCESS MATURITY LEVELS :-

Page 13: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

The CMMI model is defined in terms of

Process Areas & Maturity Levels and has two

representations:

• Staged representation that organizes the

process areas by maturity level.

• Continuous representation that organizes

the process areas by process categories

and measures capability level.

Page 14: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

AVAILABLE PRODUCTS In past few years ,SQI Project developed a

broad range of products, services, and training to support managers and practitioners throughout the software development life-cycle. Available products fall into the following categories:• Institutional requirements (includes policies,

processes, procedures, and standards)• Handbooks and guides• Checklists• Templates• Sample documents• Studies and Reports (including engineering

models)

Page 15: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

USE OF ORGANIZATIONAL CHANGE MANAGEMENT (OCM) :- OCM is the methodology that integrates

change and the ability to adapt into the organization.

They impact the way that software is managed, developed and acquired.

It involves proactively reaching out to customers, and doing whatever it takes to facilitate their

understanding and usage of processes, products and services.

Page 16: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

Involves working with a target community to systematically introduce them to desired changes in such a way that those changes are eventually adopted.

One of the premise is that individuals tend to commit to change in predictable, sequential stages.

Page 17: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

Fig . OCM Curves and stages

Page 18: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

DEPLOYMENT PROCESS

Collect user requirements and/or CMMI® needs.

Generate the process, product. Develop Infrastructure and Operations

approach and tools to support it Develop Communications & Outreach

materials to support it. Develop Education and Training materials to support it.

Page 19: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

Perform Project Support. Collect process and customer metrics to

track it. Update the process, product based on feedback.

Page 20: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

Fig. Deployment Process

Page 21: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

INFRASTRUCTURE AND OPERATIONS Involves developing the necessary

infrastructure and operations approach for the SQI Project as a whole

It includes • contact management system,• problem management system (action item tracking, problem/failure reporting), • configuration management • Electronic library, metrics collection, customer e-

mail lists, customer tracking database for CRM, • project calendar, target audience definition and

strategy, • intellectual property approach, and Operations

Plan.

Page 22: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

COMMUNICATION & OUTREACH Communication and systematic reach to the

user so that user know & understand what is available.

SQI project generated an SQI OCM approach defines Organizational change management strategy. Goals and change acceptance time lines. Key stakeholders and segments. Communications vehicles. SQI logo, brochure, fliers, and tag lines. Roles and responsibilities, and interactions

amongst the elements to achieve the changes.

Page 23: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

Similarly, the SQI Project generated an SQI CRM approach that defined the primary, secondary and tertiary customer target segments and corresponding customer profiles.

Then they provide specific communication messages and approaches to the needs of each customer segment.

The SQI Project developed an extensive website to support their user community.

Page 24: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

The website is structured along the lines of the product categories .

It also includes information about training, seminars, CMMI, frequently asked questions, contacts, etc.

They use multiple communication channels to

communicate their message, ranging from community email lists to websites , posters, cafeteria monitors, newsletters etc…

Page 25: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

EDUCATION & TRAINING :-

Involves providing educational materials and classroom and computer-based training in the desired processes, products and tools.

It includes a JPL Software Training Plan that defines the target customers, required skills sets, and training goals, and describes the training process to be utilized.

Various Courses :-• Software Management Courses • Software Engineering Courses • Software Process Improvement Courses.

Page 26: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

PROJECT SUPPORT

Involves providing consulting support to projects :

• Consulting in the areas of cost estimation

• software project planning, software project

• tracking, earned value management (EVM), metrics

• definition and implementation, defects and

reliability

• software acquisition, software tools, use of

templates,

• software testing, software quality assurance,

CMMI®, etc.

Page 27: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

CONCLUSION

Changes in how software is managed, developed and acquired do not come quickly or easily. The improvement process needs to be approached with many of the same deliberate methods and practices that are used in actual system development.

It helps to proactively reach out to customers instead of merely waiting for them to come to you.

Page 28: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

REFERENCES

When Management Gets Serious About Managing Software P. A. “Trisha” Jansma Software Quality Improvement Project Jet Propulsion Laboratory

Mary Beth Chrissis, Mike Konrad, Sandy Shrum,CMMI: Guidelines for Process Integration and Product Improvement, Addison-Wesley, San Francisco, 2003

Randy Harris, What Is a Customer RelationshipManagement (CRM) System?, DarwinMag.com, December 2003

Page 29: W HEN MANAGEMENT GETS SERIOUS ABOUT MANAGING SOFTWARE By K. Ravikant 12mcmb21 Author Name :- P.A. “TRISHA” JANSMA

THANK U…….!