Agile Talk at CSI Chapter, Mumbai

Introductions Over 17 years of corporate Software Development experience Owner, Agile Coach and Consultant @ PracticeAgile.com Active blogger on www.practiceagile.com Certifications - PMP, CSP, CSM, Lean Six Sigma Green Belt M.S Computer Science, UMASShirendoshi@practiceagile.comCell: +91 9619322001LinkedIn: http://in.linkedin.com/in/doshih © 2011 PracticeAgile

Traditional SDLC Commonly known as “Waterfall” Detailed requirement gathering, Designing, Implementing, Testing and Deploying. Follow a well defined documented process It’s supremely logical – think before you build, document everything, follow the plan. © 2011 PracticeAgile

Pros of traditional SDLC process Clear project objectives Stable project requirements Progress of system is measurable Strict sign-off at each stage Well Documented process, follows checkpoint model. PRD, SRS, High level design, Test Plan, Test cases, Documentation © 2011 PracticeAgile

Challenges with SDLC Late changing requirements are not welcome All requirement have to be generated upfront Difficult to keep up with the competition Integration errors which can result in unpredictable process. Growing defect backlog Manual and Regression testing © 2011 PracticeAgile

Agile Methodology Iterative way of development producing incremental delivery of working software in time-boxed interval of 2 to 4 weeks Iteration Iteration Iteration Iteration 1 2 3 n Is primarily a mechanism for continuous feedback from customers to successively refine and deliver a software system. © Hiren Doshi - PracticeAgile © 2011 PracticeAgile

The Agile Manifesto (Agile Values) Individuals and Interactions Over Processes and Tools Comprehensive Working Software Over Documentation Customer Over Contract negotiation Collaboration Responding to Over Following a plan change © 2011 PracticeAgile

12 Principles of the Agile Manifesto 1. Satisfy the customer through early and continuous delivery 2. Welcome changing requirements, even late in development 3. Deliver working software frequently 4. Business people and developers work together daily 5. Build projects around motivated individuals 6. Convey information via face-to-face conversation © 2011 PracticeAgile

12 Principles of the Agile Manifestocont..7. Working software is the primary measure of progress8. Maintain constant pace indefinitely9. Give continuous attention to technical excellence10. Simplify: maximizing the amount of work not done11. Teams self-organize12. Teams retrospect and tune behavior - Inspect & Adapt © 2011 PracticeAgile

Avoid miniature waterfalls Rather than doing all of one thing at a time... ...Scrum teams do a little of everything all the timeSource: “The New New Product Development Game” by Takeuchiand Nonaka. Harvard Business Review, January 1986. © 2011 PracticeAgile

The sprint should look like … Sprint 1 Analysis Analysis Analysis Analysis Analysis Analysis Analysis Design Design Design Design Design Design Design Dev Dev Dev Dev Dev Dev Dev Deploy Deploy Deploy Deploy Deploy Deploy Deploy Testing Testing Testing Testing Testing Testing Testing Rapid cycle – minimal testing lag © 2011 PracticeAgile

Case Study: Transitioning 150+ team toAgile Transformation• The reason to move to Agile• Approach• Cultural Changes• Recruiting Specialists• Investment in Hardware, Software, Tools• Training & Roll-out.• Scrum of Scrums © 2011 PracticeAgile

Agile Talk at CSI Chapter, Mumbai

by hdoshi73 on Dec 04, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

1 Embed 192

Statistics

Agile Talk at CSI Chapter, Mumbai — Presentation Transcript