Review/Post-mortem of the Agile Development

The purpose of the review is to find ways that we can improve the agile development process for future releases. By ‘review’, I mean taking the time to look at the JIRA reports and associated code fixes and to try to find ways in which we could avoid such a high level of issues in the future.

agile-review

A set of points are taken and at the end of meeting, everybody gets to vote that what are the most 3 important aspects.

1. Features – Include Spike Tasks
2. Quick Feedback on new features – show and tell, trial demo
3. Regular sprint review
4. User stories, include agile modelling, accepting criteria test cases
5. Feature sponsor
6. Assign multiple people to development of features (domain, code knowledge sharing)
7. Re-work JIRA Workflow
8. Done criteria – code review, passes unit tests, passes formal testing
9. ENforce separation across user interface, data model, domain model
10. Bug fixes have formal review with two or more peers, identify areas for refactoring
11. Switch on loggin, user platforms like Raygun, Stackify
12. Customer bug reporting, how to handle/analyse
13. User Virtual Machine and tablet simulator for testing
14. Continual review of bug list (weekly)
15. Better definition of what is a blocker bug
16. backward compatibility testing
17. Pay attention to static analysis tools / commented out code
18. Re-architect structure of code

Looks like the team is going to do a lot of refactoring.

statistics-review-agile

–EOF (The Ultimate Computing & Technology Blog) —