Introduction To Agile

Introduction to Agile

Brenda Bao （鲍央舟）

Copyright © 2009 OutSofting. All Rights Reserved.

Agenda
• Challenges of waterfall
• Agile values
• Scrum framework
• Agile Survey results


Waterfall

Based on Hakan Herdogmus,
GUAM 2005


3 things we wish were true
The customer knows what he wants
The developers know how to build it
Nothing will change along the way

3 things we have to live with
The customer discovers what he wants
The developers discover how to build it
Most things change along the way


Software development is complex


Transparency


Handling deadlines


Design Dead Software


Can we capitalize earlier?


Do you want to…
• Focus on high business value features?
• Reduce Time to Market?
• Manage changes easily?
• Improve quality?
• Improve communication?
• ….


Introduction to Agile
• Agile software development refers to a group of
software development methodologies that are
based on similar principles. Agile methodologies
generally promote:
– A project management process that encourages
frequent inspection and adaptation
– A leadership philosophy that encourages team work,
self‐organization and accountability
– A set of engineering best practices that allow for
rapid delivery of high‐quality software
– And a business approach that aligns development
with customer needs and company goals

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

That is, while there is value in the items on
the right, we value the items on the left more.
http://agilemanifesto.org/

Agile Principles
1. Early and continuous delivery of valuable software
2. Welcome changing requirements
3. Deliver working software frequently
4. Business people and developers work together
5. Trust motivated individuals
6. Face‐to‐face conversation
7. Working software is the primary measure of
progress
8. Promote sustainable development
9. Technical excellence and good design
10. Simplicity is essential
11. Self‐organizing teams
12. Team reflection and adjustment

Myths
• No planning
• No document
• Loss of management control
• Undisciplined
•…


Agile Family
• Scrum
• Extreme Programming (XP)
• Adaptive Software Development
• Crystal
• Feature Driven Development
• DSDM
•…

•Time boxed
•3 Roles:
•Product owner
•ScrumMaster
•Team
•4 Ceremonies:
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
•4 Artifacts:
•Product backlog
•Sprint backlog
•Burndown charts
•Release burndown chart
Scrum flow

A Scrum Project


Strategy
Customer
requirements Estimation
Release
Vison

Iteration Retrospective
Goals Release
plan
Charter Daily
Backlog
Iteration
plan Acceptance
Funding testing
Continuous
Integration
Standup TDD
burndown
Build
Collaboration

Refactoring

tests
Delivery of
working
velocity software


Source:crisp Henrik Kniberg


Sequential vs. overlapping
development
Requirements Design Code Test

Rather than doing all of
one thing at a time...
...Scrum teams do a little
Source: “The New New Product Development
Game” by Takeuchi and Nonaka. Harvard Business of everything all the time
Review, January 1986.


FUNCTIONALITY RESOURCES TIME
FIXED
Customer Value
Driven

Plan Driven
VARIABLE
TIME RESOURCES FUNCTIONALITY

Traditional Agile


Scrum has been used by:
•Microsoft •Intuit
•Yahoo •Nielsen Media
•Google •First American Real Estate
•Electronic Arts •BMC Software
•High Moon Studios •Ipswitch
•Lockheed Martin •John Deere
•Philips •Lexis Nexis
•Siemens •Sabre
•Nokia •Salesforce.com
•Capital One •Time Warner
•BBC •Turner Broadcasting
•Oce

Results From Scrum ‐‐ at Yahoo!
• Productivity: 68% of respondents reported Scrum is
better or much better
• Team Morale: 52% of respondents reported Scrum is
better or much better;
• Adaptability: 63% of respondents reported Scrum is
• Accountability: 62% of respondents reported Scrum is
• Collaboration and Cooperation: 81% of respondents
reported Scrum is better or much better;
• Team productivity increased an average of 36%, based
on the estimates of the Product Owners.
• 85% of team‐members stated that they would continue
using Scrum if the decision were solely up to them


Case Study

France Telecom ‐ Orange


France Telecom case (1/3)
• Initial situation:
– Department of 40 persons.
– Analysis/Paralysis situation:
• Requirements coming from many different stakeholders
abroad.
• User Interface specification coming from abroad.
• Inability to refactor and change code easily.
– Long release cycles for usable features.
– Testing and development separated and not colocated which
caused communication overhead.


• Our contribution:
– ScrumMaster training in Chinese to all the department.
– Certified ScrumMaster training to the future ScrumMasters.
– ScrumMaster coaching for pilot Scrum team
• Guided the pilot team to use the Scrum process
• Coached the PO to manage the Product Backlog
• Made test problems visible (technical and organizational)
– As requested by the customers, provided Continuous
Integration, TDD, acceptance testing expertise for their specific
platform.
– Coached the ScrumMasters of the other teams to facilitate the
whole department’s adoption of Scrum.


• Results:
– 1 week iterations and delivery of usable software
functionalities:
• Faster feedback provided to all the stakeholders abroad.
• Ability to adapt to the changing requirements while keeping the code base
clean and safe.

– How?
• Cross‐functional Scrum teams (including testers) focus on delivering
defined features (using local UI specialist if abroad is too busy).
• Clarity of roles and responsibilities in Scrum enabled stronger spirit of
continuous improvement and initiatives within the teams.
• Continuous Integration and automated acceptance testing.
• Unit testing and refactoring practices thoroughly followed by developers.


OutSofting’s facilitation
Waterfall Scrum
process for Product‐wide process for
developing Preparation Pilot team Launch rollout developing
a product a product

Engineering practices training
Scrum training
and coaching

ScrumMaster for pilot team Agile coaching for teams and
coaching for organizational impediments

Agile coaching and consulting for management


Contact us

地址：北京市朝阳区日坛路6号新族大厦附楼
2层
电话：86‐10‐87748156
传真：86‐10‐51418072
邮箱： info@outsofting.com
www.outsofting.com


Introduction To Agile

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Introduction To Agile

Similar to Introduction To Agile (20)

More from Tony Deng

More from Tony Deng (20)

Recently uploaded

Recently uploaded (20)

Introduction To Agile