Agile
- 2. Page 2Classification: Restricted Agenda • What is Agile? • What does the Agile Manifesto Mean? • Difference with Waterfall • Agile Methodologies • Roles in Scrum • Working in Agile • Basic Terminologies in Agile - Scrum • Sprint Lifecycle • Agile Methods – Scrum • Advantage of Agile • Disadvantage of Agile
- 3. Page 3Classification: Restricted What is Agile Agile is a software development methodology to build a software incrementally using short iterations of 1 to 4 weeks so that the development is aligned with the changing business needs. Agile adopts a process of frequent feedback where a workable product is delivered after 1 to 4 week iteration Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Valuable More Valuable
- 4. Page 4Classification: Restricted What does the Agile Manifesto Mean?
- 5. Page 5Classification: Restricted Difference with Waterfall
- 6. Page 6Classification: Restricted Agile Methodologies • Scrum • Extreme Programming • Kanban • Rational Unified Process
- 7. Page 7Classification: Restricted Roles in Scrum • Scrum Master • Product Owner • Cross Functional Team
- 8. Page 8Classification: Restricted Working in Agile • An Agile team works in iterations to deliver user stories where each iteration is of 10 to 15 days. Each user story is planned based on its backlog prioritization and size. The team uses its capacity − how many hours are available with team to work on tasks − to decide how much scope they have to plan.
- 9. Page 9Classification: Restricted Basic Terminologies in Agile - Scrum • User Story • Tasks • Product Backlog • Sprints • Scrum • Acceptance Criteria • Definition of Done • Burndowm Chart Tools for Scrum Management : • TFS – Microsoft (Team Foundation Server) • JIRA
- 10. Page 10Classification: Restricted Sprint Planning •Requirement Gathering from Stakeholders/Product Owner •Creating Sprint backlog from the PB •Initiating the Sprint Sprint Execution •Daily Scrum •Impediments •Breaking User Stories in Tasks •Progressive Burndown •Development and testing Sprint Review • Demo for the developed items •Review done by Product Owner and other stake holders •feedbacks Sprint Retrospective • revisiting the entire sprint iteration by the development team and Scrum Master. •What went well? •What went wrong? •Scope of improvement Sprint Lifecycle
- 11. Page 11Classification: Restricted Agile Methods – Scrum (1)
- 12. Page 12Classification: Restricted Agile Methods – Scrum (2)
- 13. Page 13Classification: Restricted User Story User story is an informal, natural language description of one or more features of a software system. User stories are often written from the perspective of an end user or user of a system.
- 14. Page 14Classification: Restricted Product Backlog PBIs are Uniquely ranked items, progressive user stories are short plain language of description of functionality in terms of customer benefit/need Stories (=requirement) priority estima te As a user I want to be able to easily install the application so that I can access my bank account on my mobile 1 5 As a user I want to be able to view my bank transaction history so that I can track my transactions 2 3
- 15. Page 15Classification: Restricted Sprint Backlog The sprint backlog is a list of tasks identified by the Scrum team to be completed during the Scrum sprint. This can be identified from the list of Product backlog or as a result of feedbacks from previous Sprints review meeting. Decided by stakeholders , Technical manager and BA.
- 16. Page 16Classification: Restricted Sprint Tasks • Go through each Product Backlog item selected for the Sprint. Break the requirements into tasks. • Tasks may include the traditional steps in a development lifecycle (although limited to the feature in question, not the entire product). For instance: Design, Development, Unit Testing, System Testing, UAT (User Acceptance Testing), Documentation, etc. • Keep tasks small. Estimate all tasks in hours. Estimate each task as a team.
- 17. Page 17Classification: Restricted Burndown – Progress of a sprint A burn down chart is a graphical representation of work left to do versus time. The outstanding work (or backlog) is often on the vertical axis, with time along the horizontal. That is, it is a run chart of outstanding work. It is useful for predicting when all of the work will be completed.
- 18. Page 18Classification: Restricted Agile Methods – Scrum (3)
- 19. Page 19Classification: Restricted Agile Methods – Scrum (3) Commitment – Team takes responsibility to complete the Sprint. To avoid things that will stand in its way Focus – Team’s focus is maintained. Distractions, interruptions are fielded Openness – Overall and individual status and commitments kept open. Respect – Team responsibility rather than scapegoat. Courage – Management and team have the courage to take responsibility to do what is necessary
- 20. Page 20Classification: Restricted Advantage of Agile • Active User and Customer involvement • Changing Requirements • Agile requirements are barely sufficient • Frequent delivery • Intense for developers
- 21. Page 21Classification: Restricted Disadvantage of Agile • Customer satisfaction as product is viewed at each iteration • Close communication so less susceptible to fail OR deviate • Team reflects regularly on improvements through retrospective • Adaptable to changing requirements • Fully utilization of resources. • Product is not necessarily defined completely at the start hence giving the breathing space to the stakeholders and is flexible.