Living on Internet Time

Presented by: Group O Ragini Iyer Rishabh Khandhar Sandeep Agarwal Sria Majumdar Sushant Gupta Abhishek Singh

Objective
Product development at various companies Comparison of Software development models Contemporary models of development

Netscape
Netscape Navigator- the first mover
Engineering team driven project Role of users and news groups

Yahoo
Beginning- surfers travel the net Product testing Scalability

Rewriting the whole program to a different programming language

Net Dynamics
Provided tools to help develop web pages with links to companys internal database

Net dynamics 2.0 team Programming language Working with other companies beta software

Studio and runtime team Software integrated into working system each day

Launch announcement

Microsoft
Entered late in the explorer market
Product Specification Market Analysis and Discussion with focus groups

Product Development Aimed at enhancing flexibility and responsiveness

Project Manager Technology integrator Iterative Approach Functional and Priority Development Driven by internal feedback (Developer Extensive Users) - Risk Mitigation Time - key performance variable to be managed to attain improved cost and quality Three version of explorer in 9 months

Microsoft Development Cycle

Performance Measures
Time to Market
Frequency of new product Time from conception to market Estimation planning Engineering hours per project Cost of material and tooling Projection v/s Output User friendliness Performance and customer satisfaction Continuous improvement

Productivity

Quality

Common Features
Each Aware of/Engaged in Competitive Benchmarking

Each Used Effective Prototyping/Beta Models (Microsofts Approach More Internally Focused) Aware of Interoperability

Differences
Philosophy, Culture, and Development Process
Size of Development Staffs and Resources Microsofts Total-System-Solution Mindset Microsoft Sought to Expand Competencies Heavyweight Team Structure (Microsoft) vs. Lightweight (Yahoo!) Net Dynamics Philosophy of Open Architecture Based on Standards Netscapes Heavy Focus on Early Releases Before Feature Release

Learning from the Case

Role of process refinement Role of good management Customer needs and satisfaction Importance of feedback system

Software Development Models

Waterfall Model
Spiral Model Rapid Application Development Incremental model Agile Approach Lean Development V model IBM Rational Unified Process

Process Improvement Models

Capability Maturity Model Integration (CMMI) ISO 9000 ISO 15504 : Software Process Improvement Capability Determination (SPICE)

THANK YOU