BIO
Senior SW Engineer
@RAI Radiotelevisione italiana
Rome, Italy

QUIT IT APP
@quititapp

GET IN TOUCH!
roberto.belardo@g...
?

WHY DO WE NEED
TO CHANGE SOMETHING
• “WE ARE USED TO work like this!”
• “Everybody works like this!”
• “We follow sw engineering standars!”
- and-

Change is...
What’s wrong with us?
• Big up front design
• Lengthy never-read documents
• Software is not a manufactured product
• Test...
THERE IS
A DIFFERENT WAY
{Possibly better}
Individuals and interactions
Working software

over

over

processes and tools

comprehensive documentation

Customer coll...
SCRUM

“Scrum is a simple and repeatable way of managing work” (Kelly Waters)
Scrum TEAM
self organized team
cross competence
colocated team

Scrum MASTER
protects the team
responsible for the process...
Done means… done!
PROs
• Incremental delivery means revenue
• Speed to market
• Constant feedback loop
• Quality
• Risk management
• Visibil...
Scrum hell
• Change is scary
• Change needs time (3-4 sprints at least)
• Scrum needs a lot of commitment
• scope creep da...
eXtreme
Programming
Where “extreme” is probably not what your are thinking about.
Pair programming
Test driven development
Refactoring
Continuous integration
user stories
agile
PRACTICES
COLOCATED TEAM
no junk on the trunk
30-days free reign
whiteboard
planning poker
retrospectives
bonus: pomodoro technique
Now what?
be the change
you wish to see in the world
M. Gandhi (so they say…)

better to start top-down
think big start small (pilot...
Resources
• 
• 
• 
• 

www.scrumalliance.org	
  	
  
“Agile	
  So?ware	
  Development	
  with	
  Scrum”	
  by	
  Ken	
  Sc...
Embrace the change
Embrace the change
Upcoming SlideShare
Loading in …5
×

Embrace the change

272 views

Published on

A very short introduction to Agile methodologies (in particular Scrum and Extreme programming)

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
272
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Questa è giusto unapiccolaintroduzioneallemetodologieagili per pochicuriosi. 
  • Perchèdovremmocambiarequalcosanelnostromodo di lavore?
  • Perchèdovremmocambiarequalcosanelnostromodo di lavor
  • Perchèdovremmocambiarequalcosanelnostromodo di lavor
  • Perchèdovremmocambiarequalcosanelnostromodo di lavore?
  • Agile!
  • Agile Manifesto: principi
  • Agile Manifesto: principi
  • Agile Manifesto: principi
  • Agile Manifesto: principi
  • Agile Manifesto: principi
  • Agile Manifesto: principi
  • Agile Manifesto: principi
  • Agile Manifesto: principi
  • Agile Manifesto: principi
  • Agile Manifesto: principi
  • Agile Manifesto: principi
  • Perchèdovremmocambiarequalcosanelnostromodo di lavore?
  • Agile Manifesto: principi
  • Embrace the change

    1. 1. BIO Senior SW Engineer @RAI Radiotelevisione italiana Rome, Italy QUIT IT APP @quititapp GET IN TOUCH! roberto.belardo@gmail.com     @robertobelardo     robertobelardo.wordpress.com     Skype:  backslash451  
    2. 2. ? WHY DO WE NEED TO CHANGE SOMETHING
    3. 3. • “WE ARE USED TO work like this!” • “Everybody works like this!” • “We follow sw engineering standars!” - and- Change is scary
    4. 4. What’s wrong with us? • Big up front design • Lengthy never-read documents • Software is not a manufactured product • Test when it’s too late • Client don’t know what they really want • 100% of the features are 80% complete
    5. 5. THERE IS A DIFFERENT WAY {Possibly better}
    6. 6. Individuals and interactions Working software over over processes and tools comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan agilemanifesto.org
    7. 7. SCRUM “Scrum is a simple and repeatable way of managing work” (Kelly Waters)
    8. 8. Scrum TEAM self organized team cross competence colocated team Scrum MASTER protects the team responsible for the process coach Product owner prioritize the work on the product he knows what is required for the product he is committed to the success of the product
    9. 9. Done means… done!
    10. 10. PROs • Incremental delivery means revenue • Speed to market • Constant feedback loop • Quality • Risk management • Visibility • Right product • Changes are welcomed
    11. 11. Scrum hell • Change is scary • Change needs time (3-4 sprints at least) • Scrum needs a lot of commitment • scope creep danger • agile testing is not for dummies • “Scrum-but” Scrum is not a silver bullet!
    12. 12. eXtreme Programming Where “extreme” is probably not what your are thinking about.
    13. 13. Pair programming Test driven development Refactoring Continuous integration user stories
    14. 14. agile PRACTICES
    15. 15. COLOCATED TEAM no junk on the trunk 30-days free reign whiteboard planning poker retrospectives bonus: pomodoro technique
    16. 16. Now what?
    17. 17. be the change you wish to see in the world M. Gandhi (so they say…) better to start top-down think big start small (pilot) adopt and share the philosophy but you need a change in organizational culture but… scrum is the new waterfall
    18. 18. Resources •  •  •  •  www.scrumalliance.org     “Agile  So?ware  Development  with  Scrum”  by  Ken  Schwaber   www.allaboutagile.com  by  Kelly  Waters   agilemanifesto.org  

    ×