Analysis of information sources in references of the Wikipedia article "توسعه نرمافزاری چابک" in Persian language version.
{{cite web}}: Explicit use of et al. in: |author2= (help){{cite web}}: Explicit use of et al. in: |author2= (help){{cite journal}}: Unknown parameter |coauthors= ignored (|author= suggested) (help){{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help) Appendix A, pages 165–194We were doing incremental development as early as 1957, in Los Angeles, under the direction of Bernie Dimsdale [at IBM's ServiceBureau Corporation]. He was a colleague of John von Neumann، so perhaps he learned it there, or assumed it as totally natural. I do remember Herb Jacobs (primarily, though we all participated) developing a large simulation for Motorola, where the technique used was, as far as I can tell ... All of us, as far as I can remember, thought waterfalling of a huge project was rather stupid, or at least ignorant of the realities. I think what the waterfall description did for us was make us realize that we were doing something else, something unnamed except for 'software development. '
{{cite journal}}: Check |issn= value (help); Unknown parameter |month= ignored (help)Only 6 percent indicated that their productivity was lowered ... No change in productivity was reported by 34 percent of respondents and 60 percent reported increased productivity ... 66 percent [responded] that the quality is higher ... 58 percent of organizations report improved satisfaction, whereas only 3 percent report reduced satisfaction.
{{cite web}}: نگهداری یادکرد:نامهای متعدد:فهرست نویسندگان (link)95% [stated] that there was either no effect or a cost reduction ... 93% stated that productivity was better or significantly better ... 88% stated that quality was better or significantly better ... 83% stated that business satisfaction was better or significantly better
{{cite web}}: External link in |publisher=|month= ignored (help){{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)Agile delivers
{{cite web}}: Explicit use of et al. in: |author2= (help){{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help){{cite web}}: نگهداری یادکرد:نامهای متعدد:فهرست نویسندگان (link)95% [stated] that there was either no effect or a cost reduction ... 93% stated that productivity was better or significantly better ... 88% stated that quality was better or significantly better ... 83% stated that business satisfaction was better or significantly better
{{cite web}}: External link in |publisher=|month= ignored (help)Only 6 percent indicated that their productivity was lowered ... No change in productivity was reported by 34 percent of respondents and 60 percent reported increased productivity ... 66 percent [responded] that the quality is higher ... 58 percent of organizations report improved satisfaction, whereas only 3 percent report reduced satisfaction.
Agile delivers
We were doing incremental development as early as 1957, in Los Angeles, under the direction of Bernie Dimsdale [at IBM's ServiceBureau Corporation]. He was a colleague of John von Neumann، so perhaps he learned it there, or assumed it as totally natural. I do remember Herb Jacobs (primarily, though we all participated) developing a large simulation for Motorola, where the technique used was, as far as I can tell ... All of us, as far as I can remember, thought waterfalling of a huge project was rather stupid, or at least ignorant of the realities. I think what the waterfall description did for us was make us realize that we were doing something else, something unnamed except for 'software development. '
{{cite journal}}: Check |issn= value (help); Unknown parameter |month= ignored (help)