23
Software Process Improvement and e-Business: An Oxymoron? Boston SPIN March 19, 2002 Donna L. Johnson LOGOS International, Inc.

Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

  • Upload
    others

  • View
    1

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

Software Process Improvement and e-Business:An Oxymoron?

Boston SPINMarch 19, 2002

Donna L. Johnson

LOGOS International, Inc.

Donna L. Johnson

LOGOS International, Inc.

Page 2: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

2LOGOSInternational

Agenda

I. BackgroundII. e-Business and the Need for ProcessIII. CMM Adaptations for e-BusinessIV. Summary

Questions and Answers

Page 3: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

3LOGOSInternational

BackgroundThe e-Business Environment

BackgroundThe e-Business Environment

InternetExtranetIntranetWeb

Fast time to marketAccelerated rate of changeHigh quality demands

Page 4: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

4LOGOSInternational

BackgroundDefining the Environment

BackgroundDefining the Environment

Business using the internet for:e-commerceadvertisingcommunication

A project that has the following characteristics*:quick delivery research-like, yet mission criticalmanaged in turbulent business and technology environment

*James Highsmith, Cutter Consortium, Executive Report, Vol. 1, No. 1

Page 5: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

5LOGOSInternational

BackgroundThe ControversyBackgroundThe Controversy

Preserving flexibilityAdaptable to changing environments

Based on large DoD organizationsFocused on continuous improvementPromoting repeatable processes

Page 6: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

6LOGOSInternational

BackgroundThe Study

BackgroundThe Study

15 Software managers in e-business environmentsIT organizationsWeb page developmentWeb applicationse-Business applications

15 Software managers in e-business environmentsIT organizationsWeb page developmentWeb applicationse-Business applications

Page 7: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

7LOGOSInternational

BackgroundThe e-Business Companies

BackgroundThe e-Business Companies

Software development practicesProject plans developedIterative or evolutionary lifecycle used

Some parallelism of phasesLittle prototyping – mainly for proof of principle

Effort estimates generated based on experienceDelivery dates customer drivenDocumentation stored in librariesTechnology introduced gradually to minimize impactPersonnel issues identified as greatest risk

Page 8: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

8LOGOSInternational

Backgrounde-Project Discriminators

Backgrounde-Project Discriminators

Insufficient skilled, experienced software engineersRapidly changing technology and business environmentsMany functionally complex, interconnected systemsIncreased number of stakeholdersWorldwide, networked connectivityFuzzy requirementsCompressed development cycle/time-to-market pressures

Insufficient skilled, experienced software engineersRapidly changing technology and business environmentsMany functionally complex, interconnected systemsIncreased number of stakeholdersWorldwide, networked connectivityFuzzy requirementsCompressed development cycle/time-to-market pressures

Page 9: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

9LOGOSInternational

Need for Processe-Project CharacteristicsNeed for Process

e-Project Characteristics

Process solutionsTrainingHiring of experienced managersDocumented processesSubcontractor oversight

Impact on developmentSystems engineering inadequately performedSoftware development outsourced

Page 10: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

10LOGOSInternational

Need for Processe-Project Characteristics -2

Need for Processe-Project Characteristics -2

Process solutionsProcess for introducing changeShort development cyclesPlanning for changeManagement of requirements changes

Impact on developmentTurbulent transitions to technologies and business modelsFrequent updates/ revamping of software

Page 11: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

11LOGOSInternational

Need for Processe-Project Characteristics -3

Need for Processe-Project Characteristics -3

Process solutionsRisk identification and managementPlanning & tracking of commitmentsIncreased importance on integration testing

Impact on developmentDependent on external commitmentsSystem quality a product of vendor and COTs quality

Page 12: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

12LOGOSInternational

Need for Processe-Project Characteristics -4

Need for Processe-Project Characteristics -4

Process solutionsStakeholder buy-in/commitmentRequirements change processesConflict resolution

Impact on developmentConflicting requirementsChanging requirements

Page 13: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

13LOGOSInternational

Need for Processe-Project Characteristics -5

Need for Processe-Project Characteristics -5

Process solutionsImproved product quality

Impact on developmentImmediate distribution of information/newsWorldwide customer baseHigh visibility of SW problems

Page 14: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

14LOGOSInternational

Need for Processe-Project Characteristics -6

Need for Processe-Project Characteristics -6

Process solutionsPrototypingEvolutionary life cycleProcess for incorporating requirements changes

Impact on developmentRequirements evolving as project progresses

Page 15: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

15LOGOSInternational

Need for Processe-Project Characteristics -7

Need for Processe-Project Characteristics -7

Process solutionsImproved estimating processesTrainingHiring of experienced managersReduced reworkIncreased milestones for tracking progress

Impact on developmentInsufficient testingInadequate systems analysisReduced project functionality

Page 16: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

16LOGOSInternational

CMM AdaptationsCMM Adaptations

CMM Level KPAsLevel 2: Repeatable Requirements management

Software project planningSoftware project tracking and oversightSoftware subcontract managementSoftware quality assuranceSoftware configuration management

Level 3: Defined Organization process focusOrganization process definitionTraining programIntegrated software managementSoftware product engineeringIntergroup coordinationPeer reviews

Level 4: Managed Quantitative process measurementSoftware quality management

Level 5: Optimizing Defect preventionTechnology change managementProcess change management

Page 17: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

17LOGOSInternational

CMM Adaptations Requirements ManagementCMM Adaptations

Requirements Management

Processes for managing changing requirementsQuick turn-around process for responding to customer or market needs

Requirements not fully defined (i.e., incomplete, fuzzy)Increased importance of software review of requirements

Processes for managing changing requirementsQuick turn-around process for responding to customer or market needs

Requirements not fully defined (i.e., incomplete, fuzzy)Increased importance of software review of requirements

Page 18: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

18LOGOSInternational

CMM Adaptations Software Project PlanningCMM Adaptations Software Project Planning

Detailed planning for small, manageable units of workIterative or evolutionary life cyclePlans for introduction of technology changesIncreased planning needs

Increased risksIncreased interfacesIncreased commitmentsChanging training needs

Schedule & budget pressures on estimates

Page 19: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

19LOGOSInternational

CMM AdaptationsSoftware Project Tracking and Oversight

CMM AdaptationsSoftware Project Tracking and Oversight

Re-evaluation of project tracking metricsIncreased tracking of commitments and risksReduced frequency of plan updatesIncreased need for communication

Page 20: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

20LOGOSInternational

CMM Adaptations Software Configuration Management

CMM Adaptations Software Configuration Management

Heavy emphasis on toolsWider range of controlled items

Voice and video objects, graphic imagesDatabasesCopyright releases

Provision for fast track in change management

Heavy emphasis on toolsWider range of controlled items

Voice and video objects, graphic imagesDatabasesCopyright releases

Provision for fast track in change management

Page 21: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

21LOGOSInternational

CMM Adaptations Peer Reviews

CMM Adaptations Peer Reviews

Modified peer review methods to accommodate smaller teamsExpanded coverage of peer reviewsRe-definition of “code”

Page 22: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

22LOGOSInternational

Summary

The CMM can improve e-business software development, if:CMM practices are applied judiciously to recognize the e-business need for:

Improved qualityReduced time to marketIncreased productivity

Attention is paid to recognizing the alternative practices of e-projects when satisfying CMM KPA goals.

The CMM can improve e-business software development, if:CMM practices are applied judiciously to recognize the e-business need for:

Improved qualityReduced time to marketIncreased productivity

Attention is paid to recognizing the alternative practices of e-projects when satisfying CMM KPA goals.

Page 23: Boston SPIN · Iterative or evolutionary lifecycle used zSome parallelism of phases zLittle prototyping – mainly for proof of principle Effort estimates generated based on experience

23LOGOSInternational

Contact InformationContact Information

Donna Johnson

LOGOS International, Inc.8 Mackintosh LaneLincoln, MA 01773

Tel: 781-259-8266 Fax: [email protected]

Donna Johnson

LOGOS International, Inc.8 Mackintosh LaneLincoln, MA 01773

Tel: 781-259-8266 Fax: [email protected]

Visit our WEB site for more information:http://www.logos-intl.com

Visit our WEB site for more information:http://www.logos-intl.com