Your SlideShare is downloading. ×
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Agile Software Development - a Suvojyoti Presentation
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile Software Development - a Suvojyoti Presentation

1,486

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,486
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
60
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1.  
  • 2. AGILE SOFTWARE DEVELOPMENT
    • Requirements for good software solutions
    • Effective
    • Quick Response To Needs
    • Easy to operate
    • Simple to maintain
    • Adoptive
  • 3. AGILE SOFTWARE DEVELOPMENT
    • General development processes
    • Slow
    • Inconsistent
    • Non-adoptive
    • Time consuming
    • Low interactive
  • 4. AGILE SOFTWARE DEVELOPMENT
  • 5. AGILE SOFTWARE DEVELOPMENT
    • Brief History
    • Edmonds introduced an adoptive software development process in 1974
    • Initially called “Light Wight methods”
    • In 2001 developers made in Utah and formed Agile Methods
    • Later Agile Alliance was formed
    • Past methods include Extreme Programming(XP),Adaptive Software Development, Feature Driven Development
  • 6. AGILE SOFTWARE DEVELOPMENT
    • 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
  • 7. AGILE SOFTWARE DEVELOPMENT
    • Agile Principals
    • Early and continuous delivery of valuable software
    • Welcome changing requirements
    • Work in collaboration
    • Build projects around motivated individuals
    • Face to face communication in a team
    • Attention to technical excellence
    • Simplicity
  • 8. AGILE SOFTWARE DEVELOPMENT
    • Characteristics
    • Team takes a Test Driven Development(TDD) approach
    • Stakeholders are active participants in development
    • Produce high quality software solutions in a regular basis
    • Team working in high collaboration
  • 9. AGILE SOFTWARE DEVELOPMENT
    • Agile Methods
    • Agile Modeling(AM)
    • Agile Unified Process(AUM)
    • Agile Data Method(ADM)
    • Test Driven Development(TDD)
    • Feature Driven Development(FDD)
    • Behavior Driven Development(BDD)
    • Essential Unified Process(EssUP)
    • Responsive Development(RD)
    • And many more………..
  • 10.  
  • 11. AGILE LIFE CYCLE
    • ITERATION ZERO
    • Getting Initial Support and Funding
    • Model The Scope Of The System
    • Start Building A Team
    • Initial Architecture
    • Set Up Environment
  • 12. AMDD Life Cycle
  • 13. AGILE LIFE CYCLE(Contd.)
    • CONSTRUCTION ITERATIONS
    • Close Collaboration With Stakeholders & Developers
    • Implement Functionality In Priority Order
    • Analysis & Design
    • Ensuring Quality
    • Regularly Delivery of Working Software
    • Testing
  • 14. Construction Iteration
  • 15. AGILE LIFE CYCLE(Contd.)
    • Release Iteration
    • Final Testing
    • Rework
    • Finalize System & User Documentation
    • Training
    • Deployment
  • 16. AUP Deployment Discipline
  • 17. Testing, Testing And More Testing…..
    • Confirmatory Testing
    • Developer Testing
    • Agile Acceptance Testing
    • Independent Testing
    • Acceptance Testing
    • Function Testing
    • Exploratory Testing
    • Scenario Testing
    • System Testing
    • User Testing
    • Investigative Testing
  • 18. Life Cycle Testing
  • 19. Test First Approach
  • 20. Model Storming:
    • Screen Sketches
  • 21. Model Storming
    • Flowchart
  • 22. Model Storming:
    • Service Level Sequence Diagram
  • 23. REFACTORING
    • Code Refactoring
    • Database Refactoring
    • A database refactoring is a simple change to a database schema that improves its design while retaining both its behavioral and informational semantics
  • 24. Characteristics of Agile DBA
    • Work very closely with application developers
    • Work in an evolutionary, if not agile, manner
    • Need to communicate the constraints imposed by legacy data sources
    • Work with enterprise administrators
    • Work with enterprise architects
  • 25. Percentage Of Success Under ASD Projects
  • 26. PRODUCTIVITY UNDER ASD
  • 27. QUALITY OF SERVICES UNDER ASD
  • 28. COST CHANGES UNDER ASD SYSTEMS
  • 29. STAKEHOLDER SATISFACTION
  • 30. WHEN WOULD YOU ADOPT ASD
  • 31. ADVANTAGES
    • Small team with high ability
    • Active stakeholder participations
    • Easy communication
    • Less Documentation
    • Frequent working software
    • Adopt with changes easily
  • 32. ACKNOWLEDGMENTS AND REFERENCES
    • http//www.wikipedia.com
    • http//www.agilemanifesto.com
    • http//www.ambisoft.com
    • http//www.agilemodelling.com
    • http//www.agiledata.com
  • 33. THANK YOU

×