Ch 2 : Agile Development

● Agile Processes : ▸ Process :

▸ People based Planning :
▸ Focus on software User story-cards ( new story cards for new changes )
▸ Iterative methods Release Planning
▸ Deliver working model quickly Small Releases of user stories
Iterative Process
● Agile Principles : Stand up meetings
▸ Satisfy customer with early and continuous delivery of software
▸ Changes must be accommodated even if late Designing :
▸ Deliver software quite often ( within shorter span ) Simple design - for less time
▸ Business people and dev must work together Spike Solution - for technical questions
▸ Motivate, support, trust people and provide proper env Refactoring - reducing redundancy
▸ Working software - primary measure of progress
▸ Maintain constant speed Coding :
▸ Continuous technical excellence and good design Customer availability - Customer is part of team
▸ Maintain simplicity Paired Programming
▸ Self organising teams Collective code ownership
▸ Team discussions and reviews regularly
Testing :
● Concepts of Agility : - Assumptions and characteristics Unit testing
Continuous integration
● Assumptions : No overtime
▸ Difficult to predict software requirements at beginning
▸ Difficult to predict how much design necessary
▸ SDE activities like analysis, design, construction, testing are unpredictable.

● Characteristics :
▸ Adaptable to technical and env changes.
▸ Incremental development
▸ Customer feedback must be used
▸ Short time delivery
▸ Iterative

● Extreme Programming :

▸ XP Values :
1. Communication,
2. Simplicity,
3. Feedback,
4. Courage,
5. Respect

Adaptive Software Development ( ASD )
▸ Jim Highsmith
▸ Iterative approach
▸ Collaboration and teamwork
▸ Speculation :
▸ Adaptive cycle planning
▸ Customer mission statement
▸ Project constraints
▸ Basic requirement
▸ Collaboration :
▸ Motivated people
▸ Assist, work hard, skills, criticize
▸ Learning :
▸ Focus groups ( feedback related )
▸ Formal technical review
▸ Postmortems
Ch 2 : Agile Development
Dynamic Sys Development Method ( DSDM )
▸ Incremental Prototyping
▸ Feasibility study :
▸ Analyze business req and constraints
▸ Business Study :
▸ Identify functional and infonal req
▸ Basic architecture decided
▸ Functional Model Iteration :
▸ Basic functions demo to customer
▸ Gather additional info
▸ Design and build iteration :
▸ Each prototype revisited
▸ Ensure all business req are satisfied
▸ Carried parallel sometimes
▸ Implementation :
▸ Software increment in working env
▸ Any end-user changes are noted
Feature Driven Development ( FDD ) Agile Modeling
▸ Peter Coad ▸ Scope and complexity can be understood
▸ Iterative + Incremental ▸ Pblms divided among gp of people
▸ Feature - client valued function ▸ Practice based for effective modelling
▸ Docmnttion for software based for systems
▸ Develop Overall model : Features suggested by Scott Ambler :
▸ Walkthrough of scope and domain ▸ Specify purpose for model
▸ Peer reviews and discussions ▸ Make use of multiple models
▸ Domain area model created ▸ Follow definite path
▸ Merge above model to overall model ▸ Give imp to contents and not presentation
▸ Adapt locally
▸ Build Features list :
▸ Domain decomposed to subject areas
▸ Sub areas contains business activities
▸ Feature repr :
<action><result><by|for|of|to><object>
▸ Plan by feature :
▸ Development plan created.
▸ Features assigned as classes
▸ 2 weeks only to develop
▸ Sequence diagram for each feature
▸ Build by feature :
▸ Client valued function for each feature
▸ Class owners dev actual code
▸ Code promoted to main build