This document provides an overview of Agile methodologies like Scrum and Kanban. It discusses the Agile Manifesto principles of prioritizing individuals, interactions, working software, and customer collaboration over processes, tools, documentation, and contract negotiation. Core Kanban principles include visualizing work, limiting work in progress, focusing on flow, and continuous improvement. Scrum roles include the Product Owner, Scrum Master, and Scrum Team. The Product Owner represents stakeholders and users. The Scrum Master facilitates meetings and removes impediments while not having authority over the team. The Scrum Team works to deliver working software in short sprints through self-organization.

1. QUALITY ASSURANCE
www.sudreeshya.com
Aslam Ali

2. AGILE MANIFESTO

3. ● Individuals and interactions over processes and tools

4. Working software over comprehensive documentation

5. Customer collaboration over contract negotiation

6. Responding to change over following a plan

7. Principles of Agile

8. Customer Satisfaction with
Continuous Delivery

9. Accommodate Changes
throughout the development

10. Frequent delivery of working
Software

11. Collaboration of Stakeholder
with Developer throughout
Development

12. Support, Trust and Motivate
the Team

13. Enable Face to Face
Communications

14. Working Software is the
primary measure of Progress

15. Let's START….

16. Agile Process to support a
consistent development
Process

17. Attention to technical details
and design enhances agility

18. Simplicity

19. Self-organizing teams
encourage great
architecture,requirements
and design

20. Regular reflection on how to
become more effective

21. Agile Methodologies
● Kanban
● Scrum

22. What is Kanban?

23. ● Developed in 1940 In Japan by Toyota
Company.
● The core concept is to visualize the work.
● Toyota engineer used to use card to track
process and its management.

26. ● Visualize work
● Limit Work on Progress
● Focus on Flow
● Continuous Improvement
Core Principles of Kanban

27. SCRUM
● Developed in 1990’s by Hirotaka Takeuchi and ikujiro Nonaka defined scrum as
cross functional development like Rugby.

28. Role in SCRUM
● Product Owner
● SCRUM Master
● SCRUM Team

29. Product Owner
● Key Stakeholder, Which is the primary user of the developed Product.
OR
● Person who have deep knowledge of the software which is going to Developed
● Despite of Core Knowledge, He won't Decide the deadline of the Developing
Project in Scrum Team.
● He must be available to the team whenever team need him.
● The core role of the product owner is to communicate about the progress of the
developing software with Developer and Stakeholder

30. SCRUM Master
● The role of scrum master is to insure if Scrum team is following agile method or
not.
● Facilitates meeting, remove confusions and work with Product owner.
● SCRUM master plays as servant-Leader role who doesn't have authority over
team but does have authority over process.
● They can’t fire people, but they can alter how long particular sprint is going to
take to complete the project which makes more challenging to traditional role.

31. Scrum Team
● Collection of individual working together to deliver requested and committed
product in incremental order.
● Scrum Team follow common goal, adheres same norms and rules,show respect
to all.
● Scrum team has a team of 8 to 9, if we want to add more team, new team of
scrum will be formed which will work for the same goal.
● Scrum Team is responsible to break requirement, create task , estimate and
distribute them .In simple term responsible for creating sprint backlog.
● They have to organize short sprint meeting.
● They have to ensure at the end of the sprint potentially shippable functionality
is delivered.