Agile Maintenance by ShriKant Vashishtha
•Transferir como PPT, PDF•
1 gostou•837 visualizações
![Agile Maintenance A Case Study ShriKant Vashishtha [email_address] http://svashishtha.wordpress.com/about/](https://image.slidesharecdn.com/agilemaintenancebyshrikantvashishtha-110429032013-phpapp01/85/Agile-Maintenance-by-ShriKant-Vashishtha-1-320.jpg)
![[object Object],Definition](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (20)
Semelhante a Agile Maintenance by ShriKant Vashishtha
Semelhante a Agile Maintenance by ShriKant Vashishtha (20)
Último
Último (20)
Agile Maintenance by ShriKant Vashishtha
- 1. Agile Maintenance A Case Study ShriKant Vashishtha [email_address] http://svashishtha.wordpress.com/about/
- 7. Test Cases Bug to be fixed or code to be refactored Tests as Vise
- 14. One Team Multiple Projects Common Sprint Backlog
- 15. One Team Multiple Projects Scrum Board and Burndown Chart
- 20. Type A - Isolated cycles of work Type B - Overlapping iterations Type C – All at Once Type C Scrum
- 21. Type C Scrum Explained
- 23. Questions
Notas do Editor
- Many organizations explore agile development methods as way to efficiently deliver software. • Agile can deliver long-term benefits, if built on a foundation of best practices and skills to drive success. • Agile does not equal ad hoc or development with no control, which may produce early returns but long-term failure. Agile is not an excuse to eliminate processes or controls. Agile teams can often point to agile themes of "value working code over comprehensive documentation," or "individuals and interactions over process and tools," and mistakenly strip away the need for all design, documentation and any semblance of tools and process.
- Many organizations explore agile development methods as way to efficiently deliver software. • Agile can deliver long-term benefits, if built on a foundation of best practices and skills to drive success. • Agile does not equal ad hoc or development with no control, which may produce early returns but long-term failure. Agile is not an excuse to eliminate processes or controls. Agile teams can often point to agile themes of "value working code over comprehensive documentation," or "individuals and interactions over process and tools," and mistakenly strip away the need for all design, documentation and any semblance of tools and process.