CA FINAL ISCA | CHAPTER 5 | ADIS | AGILE MODEL | MNEMONICS | MEMORY TECHNIQUE

CA FINAL ISCA
CHAPTER 5 | ADIS | MNEMONICS | MEMORY TECHNIQUE






AGILE MODEL



This is an organized set of software development methodologies based on the iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery; time boxed terative approach and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development life cycle.

Mnemonics are only for Strengths & Weakness

Features: 
  • Customer satisfaction by rapid delivery of useful software;
  • Welcome changing requirements, even late in development;
  • Working software is delivered frequently (weeks rather than months);
  • Working software is the principal measure of progress;
  • Sustainable development, able to maintain a constant pace;
  • Close, daily co-operation between business people and developers;
  • Face-to-face conversation is the best form of communication (co-location);
  • Projects are built around motivated individuals, who should be trusted;
  • Continuous attention to technical excellence and good design;
  • Simplicity;
  • Self-organizing teams; and
  • Regular adaptation to changing circumstances


MNEMONICS STORY IN हिन्दी 


If you haven't watched the Mnemonic video where the techniques are explained then watch it here.

DO watch the video to understand the linkage.

[ CLICK TO WATCH THE VIDEO]


  • GOD: GOD हमारी सारी REQUIREMENTS को find कर लेता है। 


  • MOTHER/FATHER: Mother /Father की टीम है जो respond करती है हमारी changing requirements को। 


  • TRIDEV: Tridev हमारी सारी Documentation रखते है। {सब हिसाब रखते है कि कोन क्या कर रहा है। }


  • DISHA: Disha का पता लगाने के लिए High-quality software use करते है {Google maps}


  • PANDAV: Pandav द्रौपदी से face to  face communication नहीं कर पाते थे और उसकी Continuous हेल्प i.e Input नहीं कर पाते थे। [जो hua था द्रौपदी के साथ because ऑफ़ that]


  • SIX- SIXER- YUVRAJ: verbal communication एक Potential threat बना जिसके response मे Yuvraj ने सिक्स six मारे [Flintoff ने verbal communication किया , yuvraj ने Broad को छक्के मारे]


  • VACHAN: शादी के beginning मे वचनो को निभाने मे efforts required होते है। 


  • WONDERS': वंडर्स ऑफ़ world को बनाने मई काफी Emphasis दिआ गया था on necessary designing & documentation [bht design/documentation पे emphasis दिया था]


  • DEVIYAN: सारी देवियों को प्रस्सन करने के लिए Long term planning चाईए [Long time पूजा पाठ]


  • SIKH GURU: सिख guru के कारण लोग easily off track नहीं होते। [babaji सबको सही रास्ते पे रखते है]



Now I'll show you the linkage of these Mnemonics with actual Strengths & Weakness.

{जो भी points मे बताता हू वो अगर Strengths के है तो +ve sense मे apply करना, अगर weakness के है तो -ve }
e.g: ye Weakness का point है।  "Emphasis on necessary designing" = ye  Weakness का है तो " LACK " ऑफ़ emphasis on necessary designing बनेगा actual point. 




Strengths:


  • Agile methodology has the concept of an adaptive team, which enables to respond to the changing requirements: MOTHER/FATHER = Mother /Father की टीम है जो respond करती है हमारी changing requirements को।



  • The team does not have to invest time and efforts and finally find that by the time they delivered the product, the requirement of the customer has changed: GOD = GOD हमारी सारी REQUIREMENTS को find कर लेता है।


  • Face to face communication and continuous inputs from customer representative leaves a little space for guesswork: PANDAV = Pandav द्रौपदी से face to face communication नहीं कर पाते थे


  • The documentation is crisp and to the point to save time: TRIDEV = Tridev हमारी सारी Documentation रखते है।


  • The end result is generally the high-quality software in the least possible time duration and satisfied customer: DISHA = Disha का पता लगाने के लिए High-quality software use करते है




Weakness: 


  • In case of some software deliverables, especially the large ones, it is difficult to assess the efforts required at the beginning of the software development life cycle: VACHAN = शादी के beginning मे वचनो को निभाने मे efforts required होते है।


  • There is lack of emphasis on necessary designing and documentation: WONDERS': वंडर्स ऑफ़ world को बनाने मई काफी Emphasis दिआ गया था on necessary designing & documentation


  • Agile increases potential threats to business continuity and knowledge transfer. By nature, Agile projects are extremely light on documentation because the team focuses on verbal communication with the customer rather than on documents or manuals: YUVRAJ: Flintoff ने verbal communication किया , yuvraj ने Broad को छक्के मारे


  • Agile requires more re-work and due to the lack of long-term planning and the lightweight approach to architecture, re-work is often required on Agile projects when the various components of the software are combined and forced to interact: DEVIYAN: सारी देवियों को प्रस्सन करने के लिए Long-term planning चाईए 

  • The project can easily get taken off track if the customer representative is not clear about the final outcome: SIKH GURU: सिख guru के कारण लोग easily off track नहीं होते।


  • Agile lacks the attention to outside integration.


YouTube: Video coming soon

Share:

2 comments