Automated Process for Auditng in Agile - SCRUM

download Automated Process for Auditng in Agile - SCRUM

If you can't read please download the document

Transcript of Automated Process for Auditng in Agile - SCRUM

  1. 1. AUTOMATED PROCESS FOR SOFTWARE PROJECT AUDITS IN AGILE
  2. 2. ABSTRACT In last decade Agile have gained significant attention in software community. Agile is focused on producing early releases of software projects and on delivering business value immediately from the beginning. Auditing and tracking is one of the most important pillars for smooth execution and delivery of software project. This research work formulates a procedure to gauge the progress of software project throughout the life cycle. It will cover details from very beginning (project kickoff) till delivery to the customer, keeping main focus on Scrum.
  3. 3. AGILE (SCRUM) Sprint planning, Iteration, Sprint Items, Sprint Retrospective, Product backlog, Standup meeting
  4. 4. RELATED WORK (AGILE) Boehm & Papaccio Understanding and controlling software costs. Software Engineering, IEEE Transactions on, 14(10), 1462-1477. Claim that during there working in software industry, requirements of a particular project changes by thirty percent or even more. L.Williams & A.Cockburn Agile Software Development: Its about Feedback and Change, IEEE Computer, June 2003, pp. 39-43. Pointed that major issue with traditional software development approach is the lacing to immediate respond to changing requirements and features. Boehm & Turner Balancing agility and discipline: Evaluating and integrating agile and plan-driven methods. In Software Engineering, 2004. ICSE 2004. Proceedings. 26th International Conference on(pp. 718-719). IEEE. Boehm and Turner added that the agile is actually agility of the development process, team and their environment Southwell Agile process improvement. TickIT International Journal, 3-14. According to Southwell this methodology entertain shared view all stakeholders and a concept of delivering the product features regularly to the client in short time spans
  5. 5. RELATED WORK (AUDIT) Namioka & Bran eXtreme ISO proceedings of the OOPL04, October 24-28, 2004. They proposed a process to make software project reportable which is using Agile approach. They uses the approach to focus on each increment like a separate project. This solution is workable but it creates some extra time frame gaps that are only limited to developing documentation. McMichael & Lombardi ISO 9001 and Agile development, AGILE 2007. They suggested a hybrid approach which is using Scrum and XP both combined, that system qualifies for all basic requirement needs of ISO 9001 standard. Their overall explanation is a bit imaginary but they are on the right direction when they claim that ISO 9001 does not equate quality. It simply helps ensure that your agile practices are being followed. Krishna Chandran created Mapping between quality standard ISO 9001 and Scrum methodology. ISO recommends a manual to achieve quality in software development. It makes sure the quality throughout in software development life cycle.
  6. 6. MAPPING B/W ISO-9001 AND SCRUM
  7. 7. THESIS SURVEY The survey covers total 428 responses from 6 different organizations in Pakistan and Middle East, practicing Agile as software development approach.
  8. 8. SURVEY FORM
  9. 9. SURVEY RESULTS
  10. 10. PROBLEM STATEMENT Development of a high quality software project is indeed a challenge. As projects are becoming larger and complex day by day so successful implementation and completion is becoming difficult. Regardless of software development approach used but it is very important to have proper auditing and tracking of particular project through the life cycle. IT auditing is one of the most important component in the development of software with high quality. Very few studies on auditing which are targeting Agile software development approaches.
  11. 11. PROPOSED SOLUTION Proposes an auditing model for project traceability that is applicable in Scrum development environment. An automated tool (SAM - Scrum Auditing Machine) will have three different categories: large, medium and small depending upon the scale of software project. Large Category: Project development estimates are greater than 4 months. Medium Category: Project development estimates are in between 1 to 4 months. Small Category: Project development estimates are less than 1 month.
  12. 12. PROPOSED SOLUTION Automated tool is designed in a way that it can be used by Scrum Master or any specialized auditor of organization. Tool will use latest edge cutting technologies and will be open source. Technology Stack: Ruby 2.1 (language) - Rails 3.2 (framework) AngularJS (backend) - Bootstrap (frontend) Mysql (database) Git (source code manager) Passenger (application server) - Nginx (web server) Capistrano (deployment) - Heroku (hosting) Ubuntu (operating system)