Agile Software Development - a Suvojyoti Presentation
Oct 29, 2014
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
AGILE SOFTWARE DEVELOPMENT
Requirements for good software solutions
EffectiveQuick Response To NeedsEasy to operateSimple to maintain Adoptive
Requirements for good software solutions
EffectiveQuick Response To NeedsEasy to operateSimple to maintain Adoptive
AGILE SOFTWARE DEVELOPMENT
General development processes
Slow Inconsistent Non-adoptive Time consuming Low interactive
General development processes
Slow Inconsistent Non-adoptive Time consuming Low interactive
AGILE SOFTWARE DEVELOPMENT
AGILE SOFTWARE DEVELOPMENT
Brief HistoryEdmonds introduced an adoptive software
development process in 1974Initially called “Light Wight methods”In 2001 developers made in Utah and formed
Agile MethodsLater Agile Alliance was formed Past methods include Extreme
Programming(XP),Adaptive Software Development, Feature Driven Development
Brief HistoryEdmonds introduced an adoptive software
development process in 1974Initially called “Light Wight methods”In 2001 developers made in Utah and formed
Agile MethodsLater Agile Alliance was formed Past methods include Extreme
Programming(XP),Adaptive Software Development, Feature Driven Development
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
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
AGILE SOFTWARE DEVELOPMENT
Agile PrincipalsEarly and continuous delivery of valuable
softwareWelcome changing requirementsWork in collaborationBuild projects around motivated individualsFace to face communication in a teamAttention to technical excellenceSimplicity
Agile PrincipalsEarly and continuous delivery of valuable
softwareWelcome changing requirementsWork in collaborationBuild projects around motivated individualsFace to face communication in a teamAttention to technical excellenceSimplicity
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
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
AGILE SOFTWARE DEVELOPMENT
Agile MethodsAgile 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………..
Agile MethodsAgile 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………..
AGILE LIFE CYCLE
ITERATION ZERO
Getting Initial Support and FundingModel The Scope Of The SystemStart Building A TeamInitial ArchitectureSet Up Environment
ITERATION ZERO
Getting Initial Support and FundingModel The Scope Of The SystemStart Building A TeamInitial ArchitectureSet Up Environment
AMDDLife Cycle
AGILE LIFE CYCLE(Contd.)
CONSTRUCTION ITERATIONS
Close Collaboration With Stakeholders & Developers
Implement Functionality In Priority OrderAnalysis & DesignEnsuring QualityRegularly Delivery of Working SoftwareTesting
CONSTRUCTION ITERATIONS
Close Collaboration With Stakeholders & Developers
Implement Functionality In Priority OrderAnalysis & DesignEnsuring QualityRegularly Delivery of Working SoftwareTesting
Construction Iteration
AGILE LIFE CYCLE(Contd.)
Release IterationFinal TestingReworkFinalize System & User DocumentationTrainingDeployment
Release IterationFinal TestingReworkFinalize System & User DocumentationTrainingDeployment
AUP Deployment Discipline
Testing, Testing And More Testing…..
Confirmatory Testing Developer Testing Agile Acceptance TestingIndependent Testing Acceptance Testing Function Testing Exploratory Testing Scenario Testing System Testing User TestingInvestigative Testing
Confirmatory Testing Developer Testing Agile Acceptance TestingIndependent Testing Acceptance Testing Function Testing Exploratory Testing Scenario Testing System Testing User TestingInvestigative Testing
Life CycleTesting
Test First Approach
Model Storming:
Screen Sketches
Model StormingFlowchart
ModelStorming:
Service Level Sequence Diagram
REFACTORING
Code RefactoringDatabase Refactoring A database refactoring is a
simple change to a database schema that improves its design while retaining both its behavioral and informational semantics
Code RefactoringDatabase Refactoring A database refactoring is a
simple change to a database schema that improves its design while retaining both its behavioral and informational semantics
Characteristics of Agile DBA
Work very closely with application developers Work in an evolutionary, if not agile, mannerNeed to communicate the constraints
imposed by legacy data sourcesWork with enterprise administratorsWork with enterprise architects
Work very closely with application developers Work in an evolutionary, if not agile, mannerNeed to communicate the constraints
imposed by legacy data sourcesWork with enterprise administratorsWork with enterprise architects
Percentage Of Success Under ASD Projects
44%
33%
12%
5% 6%
90%+ 75-90% 50-74% 25-49% >25%
PRODUCTIVITY UNDER ASD1% 4%
13%
60%
22%
Much LowerSomewhat LowerNo ChangeSomewhat HigherMuch Higher
QUALITY OF SERVICES UNDER ASD3%
6%
14%
48%
29%
Much Lower
Somewhat Lower
No Change
Somewhat Higher
Much Higher
COST CHANGES UNDER ASD SYSTEMS
5%
18%
40%
32%
5%
Much Higher
Somewhat Higher
No Change
Somewhat Lower
Much Lower
STAKEHOLDER SATISFACTION3% 4%
15%
47%
31%
Much Lower
Somewhat Lower
No Change
Somewhat Higher
Much Higher
WHEN WOULD YOU ADOPT ASD
3% 4%8%
7%
10%
21%
47%
<3 Months 3-6 Months 6-12 Months 12-24 Months
> 24 Months Never Don' Know
ADVANTAGES
Small team with high abilityActive stakeholder participationsEasy communicationLess DocumentationFrequent working softwareAdopt with changes easily
Small team with high abilityActive stakeholder participationsEasy communicationLess DocumentationFrequent working softwareAdopt with changes easily
ACKNOWLEDGMENTS AND REFERENCEShttp//www.wikipedia.comhttp//www.agilemanifesto.comhttp//www.ambisoft.comhttp//www.agilemodelling.comhttp//www.agiledata.com
http//www.wikipedia.comhttp//www.agilemanifesto.comhttp//www.ambisoft.comhttp//www.agilemodelling.comhttp//www.agiledata.com
THANK YOU
Related Documents
