Agile Maintenance 1.0
•Download as PPT, PDF•
2 likes•4,054 views
This ppt is presented by Shrikant Vashishtha (Principle Consultant @Xebia) at Agile NCR 2009 Conference held on 18th July at Park Premier Hotel.
![Agile Maintenance A Case Study ShriKant Vashishtha [email_address] http://svashishtha.wordpress.com/about/](https://image.slidesharecdn.com/agilemaintenance-1-0-090724071656-phpapp01/85/agile-maintenance-10-1-320.jpg)
![[object Object],Definition](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Agile Maintenance 1.0
Similar to Agile Maintenance 1.0 (20)
More from Xebia IT Architects
More from Xebia IT Architects (20)
Recently uploaded
Recently uploaded (20)
Agile Maintenance 1.0
- 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
Editor's Notes
- 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.