agile talk at csi chapter, mumbai

© 2011 PracticeAgile

Structured Agile Project Management Processes

Hiren R. Doshi

[email protected]


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, UMASS

[email protected]

Cell: +91 9619322001

LinkedIn: http://in.linkedin.com/in/doshih


Agenda

Traditional Software Development Methodology

Agile Manifesto & Principles

Scrum Framework

Case Study

Overlaying CMMI on Agile Practices

© Hiren Doshi - PracticeAgile


Traditional SDLC


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.


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


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


Agile Adoption

VersionOne -2010 State of Agile Development Survey Results


Agile Methodology

Iterative way of development producing incremental delivery

of working software in time-boxed interval of 2 to 4 weeks

Is primarily a mechanism for continuous feedback from

customers to successively refine and deliver a software

system.


Iteration 1

Iteration 2

Iteration 3

Iteration n


How is Agile different from Traditional approaches? The paradigm shift

© Hiren Doshi - PracticeAgile Source: www.dsdm.org


Traditional vs Agile Feedback



The Agile Manifesto (Agile Values)

Individuals and Interactions Over Processes and Tools

Working Software Over Comprehensive Documentation

Customer Collaboration

Over Contract negotiation

Responding to change

Over Following a plan


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


12 Principles of the Agile Manifesto cont.. 7. Working software is the primary measure of

progress

8. Maintain constant pace indefinitely

9. Give continuous attention to technical excellence

10. Simplify: maximizing the amount of work not done

11. Teams self-organize

12. Teams retrospect and tune behavior - Inspect & Adapt


Agile is Mainstream!


Scrum



Scrum

Product Owner

Product Backlog

The Team

Scrum Master

Sprint Demo

Sprint Retrospective

Login

Order

Inventory

Sprint Backlog

Sprint Goal

Daily Standup

2 to 4 Weeks

Reporting


Avoid miniature waterfalls

Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986.

...Scrum teams do a little of everything all the time

Rather than doing all of one thing at a time...


The sprint should look like …

Rapid cycle – minimal testing lag

Sprint 1

Analysis Design Dev Deploy Testing








Barriers to further Agile Adoption



Greatest concern about Adopting Agile



Agile techniques employed



Case Study: Transitioning 150+ team to Agile Transformation

• The reason to move to Agile

• Approach

• Cultural Changes

• Recruiting Specialists

• Investment in Hardware, Software, Tools

• Training & Roll-out.

• Scrum of Scrums


Structured Agile Project Management Processes

Hiren R Doshi Enterprise Agile / Scrum Coach [email protected]

Cell - +91 9619322001


agile talk at csi chapter, mumbai

Technology

working software

2011 practiceagile

practiceagile

www

2010 state

cell

time

follow