The document discusses Arun Kalesh Paniker's presentation on developing software using the Agile methodology. It begins with a disclaimer and outlines of content. It then discusses what Agile is, its advantages over traditional methods, and provides an overview. The core of the presentation is explaining the Agile Manifesto, which values individuals and interactions, working software, customer collaboration, and responding to change. It also details the 12 principles behind the manifesto, including early delivery, welcoming changing requirements, frequent delivery, collaboration between business and developers, motivated individuals, face-to-face conversation, using working software to measure progress, promoting sustainable development, technical excellence, simplicity, self-organizing teams, and retrospective meetings.
2. Arun Kalesh Paniker
Aartek One Global Services
Disclaimer
• The information contained in this slides are my own view gained
through various experiences.
•The images used in this slides were derived from various other online
resources.
•This is a technical session that contain non- technical content.
•Get relaxed to get ready for some detailed presentation.
3. Arun Kalesh Paniker
Aartek One Global Services
Content
• All about AGILE
• AGILE Manifesto
• AGILE Principles
• Queries
4. Arun Kalesh Paniker
Aartek One Global Services
What is AGILE?
Why AGILE?
Advantages over Traditional Methods
7. Arun Kalesh Paniker
Aartek One Global Services
Agile Manifesto
• Individuals and Interactions over Processes and Tools
• Working Software over Comprehensive Documentation
• Customer Collaboration over Contract Negotiation
• Responding To Change over Following a Plan
13. Arun Kalesh Paniker
Aartek One Global Services
1. Early and Continuous Delivery
• The highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
• Working software is the primary measure of progress.
14. Arun Kalesh Paniker
Aartek One Global Services
2. Welcome Changing Requirements
• Welcome changing requirements, even late in development.
• Agile processes harness change for the customer's competitive
advantage.
• This is nice customer expectation management also one of the
marketing / sales pitfalls of agile software development.
Coding Aspect : The development and architecture should be always
Open for Extension, but closed for modifications.
15. Arun Kalesh Paniker
Aartek One Global Services
3. Deliver Working Software Frequently
Coding Aspect : With Unit tests for each module in sprint
16. Arun Kalesh Paniker
Aartek One Global Services
4. Business People and Developers Work Together
The Product owner and Developers must work together daily throughout
the project which helps to
• Define the features of the product
• Decide a release date
• Prioritize feature according to change
• Adjust features and priority for iterations
• Accept or Reject work result for the sprint
Daily
Standup
19. Arun Kalesh Paniker
Aartek One Global Services
7. Working Software is the Measure of Progress
Coding Aspect : Modular and Expandable Codes
20. Arun Kalesh Paniker
Aartek One Global Services
8. Agile Processes Promote Sustainable Development.
The sponsors, developers, and
users should be able
to maintain a constant pace
indefinitely.
21. Arun Kalesh Paniker
Aartek One Global Services
9. Technical Excellence
• The code should always be Open for Extension, but Closed for
Modification
• Creating unit test along with Integration testing with each sprint
• Modular and Expandable
• Following SOLID principles may prove beneficial
• Self dependency
26. Arun Kalesh Paniker
Aartek One Global Services
Arun Kalesh Paniker
Software Engineer, Aartek One Global Services
arun-kalesh-1244153b
@arunkaleshp
arun.kalesh
Editor's Notes
If processes and tools are seen as the way to manage product development
Conformity makes it hard to accommodate new ideas, new requirements, and new thinking.