Arun Kalesh Paniker Aartek One Global Services “Developing Software Based on AGILE methodology” 

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. 

Arun Kalesh Paniker Aartek One Global Services Content • All about AGILE • AGILE Manifesto • AGILE Principles • Queries 

Arun Kalesh Paniker Aartek One Global Services What is AGILE? Why AGILE? Advantages over Traditional Methods 

Arun Kalesh Paniker Aartek One Global Services AGILE at a Glance 

Arun Kalesh Paniker Aartek One Global Services AGILE Manifesto 

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 

Arun Kalesh Paniker Aartek One Global Services Individuals and Interactions over Processes and Tools 

Arun Kalesh Paniker Aartek One Global Services Working Software over Comprehensive Documentation 

Arun Kalesh Paniker Aartek One Global Services Customer Collaboration over Contract Negotiation 

Arun Kalesh Paniker Aartek One Global Services Responding To Change over Following a Plan 

Arun Kalesh Paniker Aartek One Global Services Principles Behind AGILE Manifesto 

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. 

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. 

Arun Kalesh Paniker Aartek One Global Services 3. Deliver Working Software Frequently Coding Aspect : With Unit tests for each module in sprint 

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 

Arun Kalesh Paniker Aartek One Global Services 5. Motivated Individuals 

Arun Kalesh Paniker Aartek One Global Services 6. Face To Face Conversation 

Arun Kalesh Paniker Aartek One Global Services 7. Working Software is the Measure of Progress Coding Aspect : Modular and Expandable Codes 

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. 

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 

Arun Kalesh Paniker Aartek One Global Services 10. Simplicity 

Arun Kalesh Paniker Aartek One Global Services 11. Self-Organizing Teams. 

Arun Kalesh Paniker Aartek One Global Services 12. Retrospective Meeting 

Arun Kalesh Paniker Aartek One Global Services Any Valuable Inputs? 

Arun Kalesh Paniker Aartek One Global Services Arun Kalesh Paniker Software Engineer, Aartek One Global Services arun-kalesh-1244153b @arunkaleshp arun.kalesh