This document discusses the symbiosis of agile software development and Web 2.0. It describes how Scrum, an agile framework, can be used to manage Web 2.0 projects. The key aspects of Scrum covered include sprints, daily stand-up meetings, product and sprint backlogs, and sprint reviews. An example is given of Salesforce.com, which saw over 500% sales growth in one year by combining Scrum and Web 2.0 principles like continuous feedback. The conclusion emphasizes getting early customer feedback in highly dynamic Web 2.0 markets and using hybrid models like Scrum plus extreme programming.

1. Birol Efe

2.  Web 2.0 – What it is
 Scrum
 Symbiosis of agile
software development & Web 2.0
 Example: Salesforce.com
 Future Perspectives
2

3. 3
• Buzzword
• Technologies
– Ajax, XML, GWT
– E. g. Blogs, Wikis, Mashups
• Perceptual Beta
• Enterprise 2.0

4. 4
• Orientation on the Agile Manifesto
• Framework for the management to create software
• Relatively young, light and agile process modell
• Roles:
• Product Owner,
• Scrum Master,
• The team.

5. 1. Sprint
Planning
2. Product
Backlog
3. Sprint
Backlog
4. Sprint
(Development
& Testing)
5. Sprint
Review
5
Web 2.0

6. 6

7.  Decision what
comes inside
the Sprint
Backlog
 Visualization
through
whiteboard or
flipchart
7

8.  Product Owner
takes care of the
perpetual
customer feedback
 Is a very organic
and lively process
 Flexible
requirements
through User
Generated Content
 All gathered
requirements for
the system
8
Product Backlog
Product
Backlog

9.  Aim: delieverable,
innovative Web 2.0
product increments
 Everything is beta
 Step by step
adaptation of the
software according to
the everychanging
customer wishes
 All functionality that
needs to be release in
the next sprints
9
Sprint Backlog
Sprint
Planung
Sprint
Backlog
Product Backlog

10.  Spring duration: 2
weeks
 Development of
the new product
increment
 Especially the test
driven
developtment is
beneficial for Web
2.0 projects
 Own seperate
sprint for the
prototype
◦ Concrete
knowledge in order
to generate a
project
10

11. 11
Daily
Scrum
Sprints
Sprint
Planung
Product Backlog
Sprint Backlog
Sprint
Planung Daily-SCRUM-Questions:
1. What has been done since the
last Daily Scrum?
2. What should be done until the
next Daily Scrum?
3. What impediments came up?
Status
Meeting
SCRUM
Master
notiert
Product
Owner hält
aktuell
Team
bespricht
15 Min

12.  Acceptance
criteria for the
finished Web
2.0 project
 Product Owner
decides if the
product gets
shipped or not
 Product
increment is
shown (e.g.
demo) to the
product owner
12

13.  Continuous
Development
of processes
and Web 2.0
software
◦ What did we
learn?
◦ What can be
improved?
13

14. 14
Improved the
sale in the
same year over
568% !
Quelle: Greene and Fry
2008.
• Salesforce.c
om is a
„software as
a service“
company

15. 15
• Important to ensure an early
feedback of the real
stakeholder or end
customer
• Hold the customer
• Be responsive to the highly
fluctuative market
• Chance to break up old modells
• Chance to get feedback early
enough
• Accomplishment of Web 2.0
projects with hybrid project
management models
• e. g. Scrum + XP

16. 16