Here is how the agile process works in Software industry.

1. AGILE METHODOLOGY

2. AGENDA:
• Frameworks of agile
• Scrum
1. Scrum roles
2. Scrum ceremonies
3. scrum artifacts
• Scrum Ceremonies
1. Sprint Planning
2. Daily Scrum
3. Sprint Review/ Retrospective
• Scrum Artifacts
• Advantages and Disvantages of scrum

3. Types of agile framework:
• Scrum
• Extreme Programming
• Lean
• Kanban
• Crystal
Note: Most of the companies follow the scrum framework

4. Scrum:
• Scrum is an agile process that allows us to focus on delivering the highest business
value in the shortest time.
• It allows us to rapidly and repeatedly inspect actual working software (every two
weeks to one month).
• The business sets the priorities. Our teams self-manage to determine the best way
to deliver the highest priority features.
• Every two weeks to a month anyone can see real working software and decide to
release it as is or continue to enhance for another iteration.
• This scrum consists consists of
1. Scrum’s roles
2. Artifacts
3. Ceremonies

6. Scrum roles:
 Product Owner:
• Define the features of the product
• Decide on release date and content
• Be responsible for the profitability of the product (ROI)
• Prioritize features according to market value
• Adjust features and priority every iteration, as needed
• Accept or reject work results.
 Scrum Master:
• Represents management to the project
• Responsible for enacting Scrum values and practices
• Removes impediments
• Ensure that the team is fully functional and productive
• Enable close cooperation across all roles and functions
• Shield the team from external interferences

7. Scrum roles:(cont...)
 Scrum team:
• Typically 5-10 people
– QA, Programmers, UI Designers
– Members should be full-time
• Teams are self-organizing
– Team should be self-organizes someone of the team.
• Membership can change only between sprints
• Has right to do everything within the boundaries of the project to meet the sprint
goal
• Actively participate in daily ceremonies

8. Scrum ceremonies:
 Sprint Planning:
A sprint begins with the team importing stories from the release backlog into the sprint
backlog; it is hosted by scrum master. The Testers estimate effort to test the various
stories in the Sprint Backlog.

9. Scrum ceremonies (cont..)
 Daily Scrum/Standup meeting:
It is hosted by scrum master, it last about 15 minutes. During Daily Scrum, the
members will discuss the work completed the previous day, the planned work for the
next day and issues faced during a sprint. During daily stand-up meeting team
progress is tracked.
 Sprint Review/ Retrospective:
It is also hosted by scrum master, it last about 2-4 hours and discuss what the team
has accomplished in the last sprint and what lessons were learned.

10. Scrum Artifacts:
• User stories: They are a short explanation of functionalities of the system under
test. Example for Insurance Provider is – "Premium can be paid using the online
system."
• Product Backlog: It is a collection of user stories captured for a scrum product. The
product owner prepares and maintains the product backlog. It is prioritized by the
product owner, and anyone can add to it with approval from the product owner.
• Release Backlog: A release is a time frame in which the number of iterations is
completed. The product owner co-ordinates with the scrum master to decide which
stories should be targeted for a release. Stories in the release backlog are targeted
to be completed in a release.
• Sprints: It is a set period of time to complete the user stories, decided by the
product owner and developer team, usually 2-4 weeks of time.

11. Scrum Artifacts(cont...)
• Sprint Backlog: It's a set of user stories to be completed in a sprint. During sprint
backlog, work is never assigned, and the team signs up for work on their own. It is
owned and managed by the team while the estimated work remaining is updated
daily. It is the list of task that has to be performed in Sprint
• Burndown chart: Burn-down chart represents overall progress of the work in
progress and work completed throughout the process. It represents in a graph
format the stories and features not completed

13. Process of scrum:

14. Process:
• Whenever the project comes to company there will be an kickoff (KT
seesion)meeting i.e they will explain about the project
• The whole project will be divided into iterations or sprints
• Every sprint contains some user stories
• Every sprint has ceremonies meetings

15. Advantages of Agile model:
• Customer satisfaction by rapid, continuous delivery of useful software.
• People and interactions are emphasized rather than process and tools. Customers,
developers and testers constantly interact with each other.
• Working software is delivered frequently (weeks rather than months).
• Face-to-face conversation is the best form of communication.
• Close, daily cooperation between business people and developers.
• Continuous attention to technical excellence and good design.
• Regular adaptation to changing circumstances.
• Even late changes in requirements are welcomed

16. Disadvantages of Agile model:
• In case of some software deliverables, especially the large ones, it is difficult to
assess the effort required at the beginning of the software development life cycle.
• There is lack of emphasis on necessary designing and documentation.
• The project can easily get taken off track if the customer representative is not clear
what final outcome that they want.
• Only senior programmers are capable of taking the kind of decisions required during
the development process. Hence it has no place for newbie programmers, unless
combined with experienced resources.

17. THANK YOU !