1 / 19

The Confounding World of Process Methodologies

The Confounding World of Process Methodologies. By Thelma Hataria. Overview. Importance of Methodologies Characteristics of Heavyweight Methodologies Heavyweight Methodologies Advantages and Disadvantages Characteristics of Lightweight methodologies Agile (Lightweight) Methodologies

jedge
Download Presentation

The Confounding World of Process Methodologies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Confounding World of Process Methodologies By Thelma Hataria

  2. Overview • Importance of Methodologies • Characteristics of Heavyweight Methodologies • Heavyweight Methodologies • Advantages and Disadvantages • Characteristics of Lightweight methodologies • Agile (Lightweight) Methodologies • Advantages and Disadvantages • Conclusion

  3. Definition-Methodology • “A methodology is a codified set of practices (sometimes accompanied by training materials, formal educational programs, worksheets, and diagramming tools) that may be repeatedly carried out to produce software”-Wikipedia

  4. Importance of Methodologies • Earlier method “Code and Fix” • Methodologies impose a disciplined process upon software development • An inappropriate choice of methodology can lead to delayed delivery, project failure and customer dissatisfaction • Making an informed choice will lead to high quality software

  5. Types of Methodologies Methodologies LightweightMethodologies Heavyweight Methodologies

  6. Characteristics of Heavyweight Methodologies • Plan-Oriented • Detailed Documentation • Predictive Approach • Process Oriented • Tool Oriented

  7. Heavyweight Methodologies “Waterfall Model” • Real heavyweight methodology • Phase oriented • Changes in requirements are not readily acceptable • Minimum customer involvement

  8. Heavyweight Methodologies “Spiral Model” • Not so heavy • Iterative & incremental approach • Focuses on risk resolution • Plan oriented

  9. Heavyweight Methodologies “Rational Unified Process” • Lightest heavyweight methodology • Focuses on process improvement • Iterative approach • Changes can be accommodated readily • Tool oriented

  10. Advantages of Heavyweight Methodologies • Safe Approach -“Tried and Tested” • Reliable • Work towards customer satisfaction • High Quality of Software

  11. Disadvantages of Heavyweight Methodologies • Bureaucratic by nature • Detailed activities slow process development

  12. Characteristics of LightweightMethodologies • People-Oriented • Conformance to Outcomes • Adaptive Approach • Balancing Flexibility and Planning • Decentralized Approach • Limited Team Size

  13. Lightweight Methodologies “Extreme Programming (XP)” • Short iteration cycles (2-3 weeks) • Communication and Feedback • Concentrates on Productivity • Pair Programming Approach • Complete customer involvement • Frequent Integration

  14. Lightweight Methodologies “Scrum” • Very short iteration cycles(30 days) • Sprint meetings held for each iteration • Demonstration of updates • Close monitoring through scrum meetings • More importance to working software

  15. Lightweight Methodologies “Crystal Family” • Heavy Lightweight methodology • Heaviness of methodology can vary depending on the criticality and size of the project • Group of approaches for different team sizes • Each team have different set of talent and skills • Dependent on advice of experts

  16. Advantages of Lightweight Methodologies • Flexible approach • Accommodate changes • Faster delivery • Customer satisfaction

  17. Disadvantages of Lightweight Methodologies • Experts not always on hand • Progress cannot be always tracked

  18. Conclusion • Both classes of methodologies have one goal-”Software Quality” • Project characteristics and organizations goals need to be matched to objectives of the methodology • Heavyweight methodologies is the best option when reliability is the issue • Lightweight methodologies are needed where customer requirements change constantly

  19. Thank you Any questions?

More Related